UDDI 2.0 takes important steps forward, while 3.0, now in early development, should really hit its stride.
With one versions worth of experience under its belt, the UDDI design team has gained valuable insight into the things it missed in UDDI 1.0. UDDI 2.0 takes important steps forward, while 3.0, now in early development, should really hit its stride.
"Many larger corporations and virtual businesses such as marketplaces and trade blocks had commented that [Universal Description, Discovery and Integration] Version 1.0 was not adequate for registration of complex business information," states the UDDI Version 2.0 Programmers API Specification (available at www.uddi.org/pubs/ProgrammersAPI-V2.00-Open-20010608.pdf).
The UDDI 2.0 specification, which was released last June, makes two major changes over UDDI 1.0.
First, Version 2.0 provides a way for multiple entities (multiple UDDI BusinessEntity objects) in a UDDI directory to link themselves in a hierarchy or in a horizontal, point-to-point chain. This is especially important for large organizations with many divisions or subsidiaries that will register themselves in a UDDI directory.
Using these links (called PublisherAssertions), separate divisions can group themselves under a master corporate registration to show corporate affiliation and avoid duplicating shared information.
These PublisherAssertions could also be used to create horizontal links (in a chain or star topology) to indicate business partnership relationships or membership in a trade association.
To prevent false claims, all links have to be verified by parties on both sides of the link before the link becomes visible in the directory. The exception is if the same agent creates both registrations.
Second, UDDI 2.0 adds a mechanism for those querying a UDDI directory to verify that the statements an organization makes about itself are true. Claims about categorization (the type of industry a business is in, using standardized industry taxonomies) or identity (any unique identifiers, such as a Dun & Bradstreet D-U-N-S number) can now be defined as checked taxonomies.
UDDI 2.0 directories pass information in checked taxonomies through a verification process (left unspecified by the standard) before allowing the entries to be registered.
Four organizationsHewlett-Packard Co., IBM, Microsoft Corp. and SAP AGare hosting beta implementations of public UDDI directories based on UDDI 2.0. As the uddi.org site warns, these registries are for testing and prototyping UDDI 2.0 only, and data stored in them may be lost at any time. IBM and Microsoft continue to maintain production-status UDDI 1.0 registries.
Links to other stories in this package
Timothy Dyck is a Senior Analyst with eWEEK Labs. He has been testing and reviewing application server, database and middleware products and technologies for eWEEK since 1996. Prior to joining eWEEK, he worked at the LAN and WAN network operations center for a large telecommunications firm, in operating systems and development tools technical marketing for a large software company and in the IT department at a government agency. He has an honors bachelors degree of mathematics in computer science from the University of Waterloo in Waterloo, Ontario, Canada, and a masters of arts degree in journalism from the University of Western Ontario in London, Ontario, Canada.