Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
UDDI Data Schema
The following list shows the hierarchy of services within the Microsoft implementation of UDDI, including (in parentheses) the label each level maps to in the broader UDDI specification:
Provider (businessEntity). A provider is typically a business but can be any entity—business, organization, department, person, computer, application—that offers one or more XML web services. In the UDDI schema, the provider is the entity under which all other data is organized and stored. A provider can have one or more services.
Contact. A human or computer resource that can be contacted for information about the provider. A provider can have multiple contacts.
Service (businessService). This entity describes and provides access to the services to be shared across the network via UDDI services. Services can have one or more bindings.
Binding (bindingTemplate). The physical point at which a specific implementation of a service can be accessed, such as a URL. To provide fault tolerance, a service can have one or more bindings to reduce the impact of a single point of failure. Bindings contain references to tModels, which declare the interface specification for a service. Bindings cannot be directly queried; to locate a binding, you must know which service is the binding's parent.
Instance info. Contains technical information about a binding. For example, the instance info may be a Web Services Description Language (WSDL) file or an interface specification document.
tModel (tModel). Typically, tModel entities represent files such as WSDL files or interface specification documents. tModel entities can also represent a unit of descriptive data, such as an identification or categorization scheme. tModels are implemented in different ways in organizations, depending on the organization of the web services publishing service model. tModel entities don't contain files but instead point to WSDL, XML Schema datatypes (XSD), XML, or other network files.
Each entity in the schema can be defined by one or more attributes, including categorization scheme, overview document URL, discovery URL, identifier, relationships, and instance parameters.