Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 321

</overviewDoc>
….
</tModel>
As you can see, this model is uniquely identified by UUID, used as a reference to this
model. For the service's invocation, the most important element is overviewURL , con-
taining the pointer to the service WSDL/Endpoint descriptor. All other elements are self-
descriptive.
Rather minimalistic, isn't it? Generally, what we can get is the reference to WSDL and in-
formation about its structure (remember the discussions about abstract and concrete in
Chapter 1 , SOA Ecosystem - Interconnected Principles, Patterns, and Frameworks ). We
can figure out what a server does and what effects to expect. So, is UDDI just a list of
WSDL? What if we need some more information about a service and, more importantly,
not just as a consumer where just the Endpoint is enough, but as an Agnostic Composition
Controller and/or Agnostic Adapter Factory? By the way, what if our service provider is
not SOAP/WSDL-based at all?
Well, generally, we can put any type of Endpoint in the overviewURL element. All oth-
er service particulars can be packed in a bag. Literally, there is an element named cat-
egoryBag ; please see its schema in the following code:
<complexType name="categoryBag">
<complexContent>
<restriction base="{http://www.w3.org/2001/
XMLSchema}anyType">
<choice>
<sequence>
<element
ref="{urn:uddi-org:api_v3} keyedReference "
maxOccurs="unbounded"/>
<element
ref="{urn:uddi-org:api_v3} keyedReferenceGroup "
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<element
ref="{urn:uddi-org:api_v3} keyedReferenceGroup "
maxOccurs="unbounded"/>
</choice>