OASIS Preps Developers for UDDI v2 Standard
Next week, OASIS begins formal consideration of proposals
for UDDI v2 as an Open Standard for web services registries, including its committee work on specifications, APIs, model requirements and implementations. See IDN's quick overview along with links to proposed standards and even sample code.
Looking even further out, OASIS has also made available the proposed feature list for UDDI v3
, which in a sign of multi-vendor co-operation, is being edited by representatives from Microsoft and Sun Microsystems.
To bring developers and architects up-to-speed on this next step of defining a directory for web services, IDN has provided a quick overview of UDDIv2 features, along with links (where appropriate) to OASIS committee documents that define terms, propose standards or supply sample code.
What following are short descriptions of improvements in UDDI v2 (from earlier versions), and suggestions, links and other assistance for implementing these key UDDI v2 areas. UDDIv2 Data Structure and XML Schema. These documents outline the details of each of the XML structures associated with these messages. The UDDI Programmers API Specification defines approximately 30 SOAP messages that are used to perform inquiry and publishing functions against any UDDI compliant service registry. This key document (last updated July 2002) is available at http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.htm
UDDIv2 API Specification. This document describes the programming interface that is exposed by all instances of the Universal Description, Discovery & Integration (UDDI) registry. This document (last updated July 2002) is available here.
UDDIv2 WSDL Service Interface Descriptions. The WSDL service interface description for a UDDI registry is defined in two WSDL documents. One document contains the UDDI inquiry interface description, and the other document contains the UDDI publish interface description. Both of these service interface descriptions are based the UDDI V2 specification. They also adhere to the WSDL service interface definition described in the Using WSDL in a UDDI Registry, version 1.08 document.
UDDI Registry tModel. To be compliant with UDDI v2, registries must have at least one of its registry nodes provide a web service that implements the UDDI Registry tModel, the latest spec for which was just released in December 2002. The goal is to make it easier for developers to build services that can find one another by using easier-to-implement APIs and identifiers. Code sets for building UDDI v2-compliant tModels are here. http://uddi.org/taxonomies/UDDI_CoreOther_tModels.htm
UDDI v2 Taxonomies. Through taxonomies and identifier systems define the categorization and identification that businesses are able to find each other and the services that meet their needs. UDDI (v1 and v2) cites three (3) common categorization schemes to encourage registrants to categorize their (1) businesses, (2) services and (3) service descriptions. There are dozens of others that are gaining in popularity, or targeted at specific constituencies. Find for your installations.