> (1) UDDI Core Structures:
> ------------------------
> 
> businessEntity: Describes a business or other organization that
> typically provides Web services
> 
> [businessEntities contain businessServices]
> 
> businessService: Describes a collection of related Web services offered
> by an organization described by a businessEntity
> 
> [businessServices contain bindingTemplates]
> 
> bindingTemplate: Describes the technical information necessary to use a
> particular Web service
> 
> [bindingTemplates contain references to tModels]
> 
> tModel: Describes a "technical model" representing a reusable concept,
> such as a Web service type, a protocol used by Web services, or a
> category system
> 
> (2) ebXML Registry Web Services-Related Classes:
> -----------------------------------------------
> 
> Organization: A RegistryObject instance that provides information on
> organizations such as a Submitting Organization.
> 
> [An Organization may be associated with one or more Services]
> 
> Service: A RegistryEntry instance that provides information on services.
> 
> [A Service has a collection of ServiceBindings]
> 
> ServiceBinding: A RegistryObject instance that represents technical
> information on a specific way to access a specific interface offered by
> a Service instance.
> 
> [A ServiceBinding may have a SpecificationLink instance]
> 
> SpecificationLink: Provides the linkage between a ServiceBinding and one
> of its technical specifications that describes how to use the service
> with that ServiceBinding.
> 
> (3) Crosswalk*:
> -------------
> 
> UDDI "businessEntity"  ---> ebXML Registry "Organization"
> UDDI "businessService" ---> ebXML Registry "Service"
> UDDI "bindingTemplate" ---> ebXML Registry "ServiceBinding"
> UDDI "tModel"          ---> ebXML Registry "ExtrinsicObject"
> 
> *---> means "is roughly equivalent to in the Web Services context"