The Cover PagesThe OASIS Cover Pages: The Online Resource for Markup Language Technologies
SEARCH | ABOUT | INDEX | NEWS | CORE STANDARDS | TECHNOLOGY REPORTS | EVENTS | LIBRARY
SEARCH
Advanced Search
ABOUT
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors
NEWS
Cover Stories
Articles & Papers
Press Releases
CORE STANDARDS
XML
SGML
Schemas
XSL/XSLT/XPath
XLink
XML Query
CSS
SVG
TECHNOLOGY REPORTS
XML Applications
General Apps
Government Apps
Academic Apps
EVENTS
LIBRARY
Introductions
FAQs
Bibliography
Technology and Society
Semantics
Tech Topics
Software
Related Standards
Historic
Last modified: March 13, 2008
Universal Description, Discovery, and Integration (UDDI)

Contents

"The Universal Description, Discovery and Integration (UDDI) specifications define a registry service for Web services and for other electronic and non-electronic services. A UDDI registry service is a Web service that manages information about service providers, service implementations, and service metadata. Service providers can use UDDI to advertise the services they offer. Service consumers can use UDDI to discover services that suit their requirements and to obtain the service metadata needed to consume those services. The UDDI V2.0 and 3.0 specifications have been approved as OASIS Standards and are maintained by the OASIS UDDI Specification technical committee. Numerous vendors and open source communities supply products that implement the UDDI standards..." [from the FAQ document]

Update 2005-02-02: Version 3 of the Universal Description, Discovery, and Integration (UDDI) specification, in development since mid-2002, has been ratified as an OASIS Standard. UDDI provides an interoperable, foundational infrastructure for a Web services-based software environment for publicly available services and services only exposed internally within an organization. A key objective in UDDI v3.0.2 is to support secure interaction of private and public UDDI implementations. See the news story "OASIS Consortium Members Approve UDDI Version 3 as an OASIS Standard."

The UDDI project takes advantage of WorldWide Web Consortium (W3C) and Internet Engineering Task Force (IETF) standards such as Extensible Markup Language (XML), and HTTP and Domain Name System (DNS) protocols. Additionally, cross platform programming features are addressed by adopting early versions of the proposed Simple Object Access Protocol (SOAP) known as XML Protocol messaging specifications found at the W3C Web site. The UDDI protocol is the building block that will enable businesses to quickly, easily and dynamically find and transact with one another using their preferred applications..." [UDDI Member Section, 'About']

UDDI4J is "a Java class library that provides an API to interact with a UDDI (Universal Description, Discovery and Integration) registry. The UDDI Project is a comprehensive, open industry initiative enabling businesses to (I) discover each other, and (II) define how they interact over the internet and share information in a global registry architecture. UDDI is the building block which will enable businesses to quickly, easily and dynamically find and transact with one another via their preferred applications..." See the UDDI4J Project description and the development web site.

In January 2005, the approved Committee Specification for UDDI version 3.0.2 was balloted for ratification as an OASIS Standard. The key objective in UDDI Version 3.0 is to support secure interaction of private and public implementations as major element of service-oriented infrastructure. "The UDDI Version 3.0.2 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry. The Universal Description, Discovery, and Integration (UDDI) protocol is a key member of the group of interrelated standards that comprise the Web services stack. It defines a standard method for publishing and discovering the network-based software components of a service-oriented architecture. The UDDI v3 specification builds on top of the OASIS UDDI v2 Standard. This version of the specification has been designed to be used in combination with other complementary Web services specifications. UDDI Version 3.0 builds on the vision of UDDI: a 'meta service' for locating web services by enabling robust queries against rich metadata. Expanding on the foundation of the OASIS UDDI v2 Standard, UDDI v3 offers the industry a specification for building flexible, interoperable XML Web services registries useful in private as well as public deployments..." [ballot text]

Principal References

Public UDDI websites and registries

UDDI Business Registry Shutdown. UDDI Business Registry Update 2005-12: "With the approval of UDDI v3.02 as an OASIS Standard in 2005, and the momentum UDDI has achieved in market adoption, IBM, Microsoft and SAP have evaluated the status of the UDDI Business Registry and determined that the goals for the project have been achieved. Given this, the UDDI Business Registry will be discontinued as of 12 January 2006." [from 'Registering for UDDI' 2005-12-17]

UBR Shutdown References:

UDDI Specifications

General: News, Articles, Reports, Papers, Press Releases

  • [March 13, 2008] "Crawling Multiple UDDI Business Registries." By Eyhab Al-Masri and Qusay H. Mahmoud (Department of Computing and Information Science, University of Guelph, Guelph, ON, Canada N1G 2W1). Poster Paper presented at the Sixteenth International World Wide Web Conference (WWW2007) [May 8-12, 2007, Banff, Canada]. Topic: Services. From the Abstract: "As Web services proliferate, size and magnitude of UDDI Business Registries (UBRs) are likely to increase. The ability to discover Web services of interest then across multiple UBRs becomes a major challenge specially when using primitive search methods provided by existing UDDI APIs. Clients do not have the time to endlessly search accessible UBRs for finding appropriate services particularly when operating via mobile devices. Finding services of interest should be time effective and highly productive. This paper addresses issues relating to the efficient access and discovery of Web services across multiple UBRs and introduces a novel exploration engine, the Web Service Crawler Engine (WSCE). WSCE is capable of crawling multiple UBRs, and enables for the establishment of a centralized Web services repository that can be used for discovering Web services much more efficiently. The paper presents experimental validation, results, and analysis of the proposed ideas...

    WSCE is part of the Web Service Repository Builder (WSRB) in which it actively crawls accessible UBRs, and collects information in a centralized repository called the Web Service Storage (WSS). A Query Engine (QE) within WSRB provides clients with an interface to perform advanced search and discovery operations. Our approach in implementing the conceptual discovery model is a process-per-service design in which WSRB runs each Web service crawl as a process that is managed and handled by the WSCE's Event and Load Manager (ELM). The crawling process starts with dispensing Web services into the WsToCrawl queue. The WSCE Ws Seed List contains hundreds or thousands of business keys, service keys, and corresponding UBR inquiry locations. WSCE begins with a collection of Web services and loops through taking a Web service from WsToCrawl queue. WSCE then starts analyzing Web service information located within the registry, tModels, and any associated WSDL information through the Analysis Module. WSCE stores this information in the Web Service Storage (WSS) after processing it through the Indexing Module. After completion, WSCE adds an entry of the Web service (using serviceKey) into VisitedWs queue. Conceptually, WSCE examines all Web services from accessible UBRs through businessKeys and serviceKeys and checks whether any new businessKeys or serviceKeys are extracted. If the businessKey or serviceKey has already been fetched, it is discarded; otherwise, it is added to the WsToCrawl queue. WSCE contains a queue of VisitedWS which includes a list of crawled Web services. In cases the crawler process fails or crashes, information is lost, and therefore, ELM handles such scenarios and updates the WsToCrawl through the Extract Ws component...

    Data used in this work are based on actual implementations of existing UBRs including: Microsoft, Microsoft Test, XMethods.net, and SAP... Our experiments demonstrate that building a crawler and a centralized repository for Web services is inevitable. For future work, we plan to extend our current framework to include a ranking mechanism that outputs desired services of interest within top results and therefore, rendering the discovery process to become more efficient."

  • [September 30, 2005] "Oracle-Systinet Deal a Win-Win." By Colleen Frye. From SearchWebServices.com (September 30, 2005). "Oracle Corp. and Systinet Corp. have entered into a strategic three-year agreement in which Oracle will embed Systinet's registry with the recently unveiled Oracle Application Server 10g Release 3, a component of Oracle Fusion Middleware. Also under the terms of the contract, Oracle will have the ability to prepopulate the registry with business services based on Oracle's family of application software. For Redwood Shores, Calif.-based Oracle, the deal will not only provide a UDDI v3 registry, it will also provide lifecycle management capabilities, which will become more important as organizations reach a critical mass with Web services and service-oriented architecture. 'One of the main reasons Oracle was interested in working with Systinet was [its] support for the UDDI v3 standard, ratified at the beginning of this year,' said Ian Bruce, director of marketing for Systinet, Burlington, Mass. 'But the standard is simply a protocol; we've added a lot of functionality that is very attractive to BEA Systems Inc. and Oracle, like lifecycle management.' According to Mike Lehmann, director of product management for Oracle Application Server, early adopters of Web services who are increasing their portfolio of services are beginning to be concerned about having a system of record and a taxonomy. 'Customers wanted more than just the basic vanilla UDDI v2 registry we provided; they obviously wanted UDDI v3, and Systinet has built a pretty rich functional interface on top of the UDDI v3 spec'..."

  • [September 22, 2005] "UDDI Registry Helps NASA Create an Earth Science 'Marketplace'." By Colleen Frye. From SearchWebServices.com (September 22, 2005). "Businesses looking to build more agile architectures that enable them to discover and reuse their IT assets in new ways can take a page from NASA's playbook. Long before acronyms like SOA, SOAP and UDDI were part of the vernacular, the earth science community, under the auspices of the NASA, began building an SOA for the Earth Observing System Clearinghouse (ECHO), which allows scientists to access, search and share earth science meta data. Now NASA has rolled out an extended services registry for ECHO, based on a UDDI registry from Systinet Corp., Burlington, Mass., which allows third parties to publish and access data. ECHO, initiated in 1998, was built from the get-go, utilizing XML and Web service technologies. The ECHO system acts as middleware between data partners and client partners; client partners develop software to access the information... The ECHO environment comprises an Oracle 9i back-end database from Oracle Corp., and the plan is to move to Oracle 10g. The WebLogic application server from BEA Systems Inc. hosts most of the core business logic. Apache Axis and Tomcat are also utilized. The Systinet UDDI server is used to expose the service registry through the industry standard UDDI protocol. And developers use Eclipse and a variety of other tools... Wichmann said the team is in the process of upgrading ECHO to be compliant with the Web Services Interoperability (WS-I) Basic Profile. In version 8 of the system (the current version is 6), he said, 'ECHO itself will be available as a Web service'..."

  • [February 22, 2005] "UDDI v3: The Registry Standard for SOA." A Webinar hosted by OASIS UDDI Specification Technical Committee. February 22, 2005. "UDDI v3.0.2 OASIS Standard: was approved by OASIS membership at-large in February 2005. Widely regarded as a cornerstone of Web services; it defines a standard method for publishing and discovering network-based software components in an SOA; the spec was developed within an open process... Ongoing work of the OASIS UDDI TC: [1] Technical Notes (TN) published to date: Using WSDL in a UDDI Registry; Using BPEL4WS in a UDDI Registry; Generating a JAX-RPC Client for UDDI 3.0.2; UDDI as the registry for ebXML Components; Providing a Value Set For Use in UDDI; Versioning Value Sets in a UDDI Registry; Value Set Overview Documents; Handling of anyURI datatypes [2] TNs in progress and under consideration in 2005 'WSRP - UDDI' Technical Note: publication and discovery of WSRP Producer and Portlet services Using WS-Policy and WS-PolicyAttachment with UDDI 'WSDM - UDDI' TN: mapping of WSDM metrics and management endpoints to UDDI WS-Security Related work ('HTTP Basic and Digest Authentication' TN, 'WS-Security TN for Modeling WS-Security in UDDI' TN).." [source]

  • [February 08, 2005] "Core Web Service Standard UDDI Evolves With Version 3.0.2." By Charles Abrams, Ray Valdes, and David Mitchell Smith. A Gartner Research Note, ID Number: G00126170. (February 08, 2005). ['The new version of the Universal Description, Discovery and Integration (UDDI) standard, used for building registries of service-oriented business applications (SOBAs), shows progress but still faces adoption challenges.'] "New features in UDDI v. 3.0.2 include: (1) Support for digital signatures, which will allow UDDI to deliver a higher degree of data integrity and authenticity; (2) Extended discovery features, which combine multistep queries used in prior versions into a single-step complex query. Subqueries can also be nested within a single query, allowing client machines to narrow their searches more efficiently; (3) A change in the underlying mechanism for pointers to actual services, from Globally Unique Identifiers to the more Web-centric Universal Resource Identifier... UDDI offers a standardized mechanism for discovering Web services, and is supported by major Web services platform vendors. Although UDDI is foundational, its adoption by enterprises has lagged behind that of the other cornerstones of Web services — SOAP (Simple Object Access Protocol) and WSDL (Web Services Description Language). Gartner surveys show that fewer than 10 percent of businesses use UDDI for their service-oriented architecture (SOA) registries. UDDI v. 3.0.2 serves enterprise needs better than prior implementations, through increased trust mechanisms and more robust categorization and security capabilities. Gartner clients have not stated that a lack of the features now provided by v. 3.0.2 has stopped them from adopting UDDI. Nonetheless, we believe that the use of UDDI will grow as businesses recognize that it provides benefits for internal uses and can be used as the basis for a development-time repository. We also believe that UDDI may eventually merge with alternative technologies, such as XMethods and ebXML Registry, which are used as much as UDDI..." [source PDF, cache]

  • [February 03, 2005] "OASIS Approves UDDI Upgrade. Web Services Directory Spec Gains SOA, Digital Signature Boosts." By Paul Krill. From InfoWorld (February 03, 2005). "OASIS on Thursday announced that the organization has approved Version 3.0.2 of the UDDI Web services directory specification as an OASIS standard, the highest level of ratification. Featured in Version 3.0.2 is the ability to affiliate registries. This is in keeping with the emphasis of SOAs (service-oriented architectures) on supporting a variety of infrastructural variations and providing a means to define relationships among UDDI registries, according to OASIS. The new version offers a standardized approach to ensure interoperable communication between server peers. To make it easier for developers and architects to communicate, Version 3.0.2 allows for well-known identifiers for service descriptions to facilitate reuse of service descriptions among registries. Other features supported include digital signatures and extended discovery to combine multi-step queries into a single query. Also highlighted is the ability to nest sub-queries within a single query, for narrowing of searches. Companies such as IBM, SAP, and Computer Associates are expressing support for the new specification..." See the news story "OASIS Consortium Members Approve UDDI Version 3 as an OASIS Standard."

  • [February 03, 2005] "More Open UDDI Web Services Directory Standard Ratified by OASIS." By ADT Staff. In Application Development Trends (February 03, 2005). "A new version of Universal Description, Discovery and Integration (UDDI), the often forgotten XML-based standard for Web services, won approval from OASIS. IBM announced it will support the new version in its J2EE WebSphere Application Server. Big Blue continues to believe the directory services provided by UDDI will be helpful in the discovery of Web services within an IT infrastructure, according to Karla Norsworthy, vice president of software standards for IBM. The next version of SAP NetWeaver, the open integration and application platform for mySAP Business Suite and SAP xApp composite applications, will support UDDI V3, according to a spokesperson for the German software vendor..."

  • [January 27, 2005] "W3C, OASIS Recommend New Web Services Standards." By Darryl Taft. In eWEEK (January 27, 2005). "OASIS initiated final voting this month on the latest version of the UDDI (Universal Description, Discovery and Integration) specification, version 3.0. The actual version sent out to vote on is version 3.0.2, said Luc Clément, senior program manager at Systinet Inc., of Cambridge, Mass., and co-chair of the OASIS UDDI technical committee. UDDI is a Web-based distributed directory that enables businesses to list themselves on the Internet and discover each other, similar to a traditional phone book's yellow and white pages. The UDDI registry is both a white pages business directory and a technical specifications library. Version 3 of the specification was initially released in July 2002, Clément said, 'with the guiding principal of making the spec enterprise ready. Now it's been two years and we have gone through two sets of errata and we can see that our assumptions were right on.' Clément, who said he has been involved with UDDI since 2001, said UDDI 3.0 went out for final vote on Jan. 15 and he expects to see the specification completed by Jan. 31, 2005... One of the features in UDDI 3.0 that help make the specification enterprise ready is the 'ability to define your own keys. You need to have well-known interfaces and identities, and version 3 allows you generate your own keys,' Clément said. Version 3.0 also includes the ability to support change management, and also includes the ability to support data integrity and nonrepudiation of data. 'We provided the ability to support digital signatures to ensure the integrity of the data,' Clément said. Meanwhile, Tony Rogers, a senior architect at Computer Associates International Inc. of Islandia, N.Y., and cochair of the OASIS UDDI technical committee, said he finds it noteworthy that other standards groups have adopted the UDDI specification in their work, such as the WS-I (Web Services Interoperability Organization), which maps policy to the UDDI registry. 'Version 3 has been out in the real world for a long time,' Rogers said. 'It's out there and being beaten on in real life.' Clément said Systinet has been among the first to implement UDDI 3.0 and to put a product on the market. Clément said, 'We've had support for version 3 for about eight months.' And this month the company began shipping the latest release of its Web services infrastructure platform, which adds a business services registry on top of UDDI, he said..."

  • [January 26, 2005] Generating a JAX-RPC Client for UDDI 3.0.2. UDDU Spec TC Technical Note. Author: John Colgrave (IBM). Edited by Matthew Dovey (Oxford) and Mirek Novotny (Systinet). Revision 0.3. Document identifier: 'uddi-spec-tc-tn-jax-rpc'. URLs: this version (HTML) and latest version. "There are several incompatible Java clients for UDDI V2 which prevents portability of UDDI applications and tools written in Java. This Technical Note aims to avoid a repetition of this for UDDI V3 by encouraging the use of a single JAX-RPC programming model for UDDI V3. This document describes the additions and changes to the UDDI 3.0.2 WSDL and schemas to enable a Java client to be generated according to the requirements of the JAX-RPC 1.1 Specification... This Technical Note is intended for anyone who intends to produce a Java client for UDDI 3.0.2." [source .DOC, cache]

  • [January 20, 2005] "DISA Cancels RFP for Enterprise Services Project." By Dawn S. Onley. In Government Computer News (January 20, 2005) "The Defense Information Systems Agency (DISA) this week abruptly cancelled a request for proposals on a universal discovery tool for its Net-Centric Enterprise Services initiative. The cancellation of the RFP has some pondering the future of the NCES program. 'I think they're moving it along at the Office of the Secretary of Defense level as a concept, but they wanted to move it from an idea to something that was buildable,' an industry source said. Late last month, DISA posted a notice seeking to procure a Universal Description, Discovery and Integration Registry commercial product with unlimited licenses for NCES usage. The purchase would have supported the establishment of a UDDI registry for use within NCES — a key move to bring the NCES concept over to Web services. The agency cancelled that notice on January 18, 2005. NCES is considered one of the major components of the Global Information Grid, the Defense Department's global network for classified and nonclassified data. NCES is comprised of nine core services: applications, collaboration, discovery, enterprise service management, mediation, messaging, security, storage and user assistance..." Note: The Request for Proposal (RFP) HC1047-05-R-4011 requested a price for (e.g.,) "Universal Description, Discovery and Integration (UDDI) Registry COTS Product with Unlimited Licenses for NCES Usage... The registry must be based upon the UDDI standard to support the Discovery of services on an enterprise scale in order to comply with the OSD Net-Centric checklist and to integrate with the NCES Core Discovery service. The Universal Description, Discovery and Integration (UDDI) protocol is an industry standard governed by the OASIS consortium. UDDI specifies a standard interoperable protocol that enables Web Service consumers to discover and use Web Services, providing the key publication and discovery capabilities of Service-Oriented Architectures (SOA). UDDI is a cross industry effort driven by major platform and software providers. This purchase will support the establishment of a UDDI registry for use within the NCES..."

  • [December 02, 2004] "Was the Universal Service Registry a Dream? Features in UDDI and RDF May Just Make the Dream Come True." By Fred Hartman and Harris Reynolds. From Web Services Journal (December 02, 2004). "For all the limitations of UDDI, there is currently no alternative registry standard that can match its maturity or features. RDF has much interesting potential, but is still far from being a viable ISR. A combination RDF and UDDI implementation needs mature implementations of a number of components and interfaces that are currently in their infancy. UDDI implementations are solving real-world business problems today and UDDI is not standing still. There are proposals to add RDF features to UDDI. Some UDDI vendors have extended their implementations with more granular security controls, merged service namespace across multiple registries, and identification of equivalent services to allow on-the-fly service failover without requiring hardware clustering. There are solutions for the limitations of UDDI, but it remains to be seen if these and future proposals will be accepted, and if the timeline toward workable implementations will stay ahead of the progress in the RDF world..."

  • [December 01, 2004] "Insurance That SOA Works." By Michael S. Mimoso. From SearchWebServices.com (December 01, 2004). "Insurance and security may be what The Hartford Financial Services Group Inc. offers its customers worldwide. But it's also what the investment and insurance provider's application delivery group was looking for when it created an SOA-based reference architecture using a UDDI registry so that the company's four lines of business could leverage the same applications. "We wanted to move away from siloed applications to an enterprise approach," said Ben Moreland, director of the property and casualty division's application delivery group. In 2003, Moreland's group tackled scalability issues with its single-entry multiple-carrier interface (SEMCI) application that exchanges documents in Accord XML. Accord XML is an insurance industry standard the enables agents to obtain client information and broadcast it to other carriers and receive quotes in return. The introduction of a UDDI registry enabled the application to do dynamic binding checks with the registry as the application evolves, Moreland said. UDDI is a Web services protocol that discovers and stores services. Used in conjunction with Accord XML version 2.0, The Hartford created new services, published them to the UDDI registry without any changes to the orchestration..."

  • [November 17, 2004] "Users and Vendors Demonstrate Support for UDDI OASIS Standard at Gartner Web Services Summit. Charles Schwab and The Hartford Present UDDI Implementations IBM, Oracle, SAP, Systinet, and Prove UDDI Interoperability." - "Implementations and interoperability of the Universal Description, Discovery, and Integration (UDDI) OASIS Standard were featured at today's Gartner Application Integration and Web Services Summit. Representatives from The Hartford and Charles Schwab each presented details on their company's implementation of UDDI registries as core foundation components of their Service Oriented Architectures (SOA). Then, members of the OASIS UDDI Specification Technical Committee staged a live demo incorporating UDDI product offerings from IBM, Oracle, SAP, Systinet, and others in a business scenario. 'Enterprise business analysts, architects, and developers fully understand that a business services registry is the foundation of the SOA infrastructure,' noted Tony Rogers of Computer Associates, co-chair of the OASIS UDDI Specification Technical Committee. 'The UDDI OASIS Standard has established itself as an important enabler of visibility, manageability, adaptability, and reusability of the service-oriented enterprise.' The OASIS UDDI InterOp at Gartner featured an inventory management scenario for a chain of book stores. Varying in size from mall kiosks to large retail outlets, each store maintained its own inventory management processes, which were not centrally controlled. By using UDDI to integrate suppliers and inventory management systems, corporate purchasers were able to monitor inventory levels, replenish stock, respond quickly to demand fluctuations, streamline procurement, and deliver useful information on product demand to publishers. 'Today we provided concrete, real-world examples of UDDI registries as the foundation of SOA,' said Luc Clément of Systinet, co-chair of the OASIS UDDI Specification Technical Committee. 'We demonstrated how enterprises can exploit a UDDI registry to deploy adaptive business services dealing with the realities of change within the enterprise by showing the benefits of location-independence. In the process, we showed how you can add new services without the need to do any configuration other than the act of publishing the new service. And finally, we demonstrated how UDDI brings an increase in visibility and reuse that dramatically reduces the cost of an SOA integration.' Participation in the OASIS UDDI Specification Technical Committee remains open to all organizations and individuals. End-users and system integrators are invited to join OASIS to advance the adoption of this international standardization effort. OASIS hosts an open mail list for public comment and the uddi-dev mailing list for exchanging information on implementing the standard..."

  • [November 15, 2004] "Data Management, Tools Wrap: Systinet Hails UDDI." By Paul Krill. From InfoWorld (November 15, 2004). "Systinet is releasing an upgrade of its UDDI-based business services registry that adds a configurable services console, advanced classification management, and publishing wizards for mapping and publishing of service data. Version 5.5 of Systinet Business Services Registry is intended to provide for SOA 'governance' and application life cycle management, serving as a hub. With the business services console, users gain an easy way to navigate and search for services based on specific categorizations, such as business processes like order entry or credit authorization. An advanced classification management function enables users to set up the business service model and change relationships of services. Typically, services are customer- defined into classifications such as service views or security policy compliance. Previously, classifications in the product were based on standard UDDI taxonomies. SOA information publishing wizards in Version 5.5 allow for automatic mapping and publishing of business service data while providing standard SOA information, including XML Schema, WSDL, BPEL (Business Process Execution Language), and versioning, according to Systinet. Specific XML documents can be related to a Web service. A policy document, for example, could be based on a Web services policy and describe a rule such as a security rule..."

  • [November 15, 2004] "Systinet Unveils First Business Services Registry for SOA Latest Version of Proven Systinet Registry Provides the Standards-Based Foundation for SOA Governance and Lifecycle Management." - "Systinet, the provider of the leading foundation for SOA governance and lifecycle management, today announced the release of Systinet Registry 5.5, the industry's most complete and proven Business Services Registry. The Business Services Registry is the centerpiece of Systinet's foundation for governance and lifecycle management within a service-oriented architecture (SOA). The Business Services Registry provides Systinet's customers a simpler, faster, and easier way to establish control of an SOA. This is especially crucial during the transition from point-to-point Web services to re-usable business services. Systinet Registry creates the system of record for all information about business services in the SOA; provides lifecycle functions to enable, publish, discover, and manage business services; allows for on-demand re-use of business services; and acts as the guide in mapping business processes to SOA. 'There's tremendous power for SOA governance if you store process, policy, SLAs, and related information about services in a registry,' said Frank Kenney, research analyst at Gartner. 'Gartner believes that registries will be essential to minimally discover and document services and preferably to enable the governance function.' Systinet Registry 5.5 extends beyond full v3 UDDI compliance to include federation, security, data validation and lifecycle services for change management and notification and quality of service management. It supports any Web services enablement or management platform and works with traditional message oriented middleware (MOM), enterprise application integration (EAI) or enterprise service bus (ESB). With Systinet Registry, businesses are able to manage complete SOA business service lifecycles across disparate, heterogeneous environments. The new Business Service Registry builds on the company's already proven versions currently in use at Motorola, Level 3, and the U.S. Department of Defense..."

  • [November 02, 2004] "A New Approach to UDDI and WSDL, Part 5: Query from a Java Application Using the New OASIS UDDI WSDL Technical Note." By John Colgrave. From IBM developerWorks (November 02, 2004). "This article is the fifth in a series outlining a new approach to using WSDL and UDDI as described in the Technical Note. It shows how to implement the approach to query from a Java application as defined in the Technical Note using UDDI4J. Earlier installments in the serialized article (1) explain the new approach to constructing a UDDI model of a WSDL description; (2) describe the types of UDDI query this new approach enables, with examples of several queries given in the form of UDDI V2 API requests; (3) present a more complex example than the one in the Technical Note, including screen shots showing you how to publish the UDDI entities and how to construct the types of query described in the Technical Note and in Part 2; (4) present some example Java code showing you how to publish WSDL descriptions to UDDI programatically. See also the references for Parts 1-4 of this serial article.

  • [September 30, 2004] "WSRP-UDDI Technical Note." Edited by Richard Jacob (IBM) and Andre Kramer (Citrix Systems Inc). Version: draft-10. September 30, 2004. Produced by members of the OASIS WSRP TC, Publish Find Bind SC. Document Identifier: 'wsrp-pfb-uddi-tn-1.0-draft-10.doc'. The goals for this technical note are to: (1) enable the automatic publishing of WSRP Producers and Portlets to UDDI registries using tooling support and (2) enable manual publishing of WSRP Producers and optionally Portlets to UDDI registries. The WSRP Publish Find Bind Abstract Model provides guidelines for publishing WSRP Producers and Portlets as services in registries. This technical note adheres to the guidelines and maps the abstract model to UDDI specific schemes and data structures. Compared to many Web Services scenarios, WSRP services prove more complex. Firstly, the WSRP Producer can be considered as a Web Service on its own, exposing multiple Bindings and PortTypes. One can view the WSRP Producer as the actual Web Service described through the WSRP WSDLs. Secondly, Portlets can also be understood to be services. In contrast to Producers, Portlets are not full services in a Web Service sense. In addition to the WSDL interface specification, WSRP services carry metadata which describes both the Producer and its Portlets. Prior to using a Producer or its Portlets this metadata has to be obtained..." See also WSRP references. [source PDF]

  • [August 23, 2004] "UDDI URI Scheme Registration with IANA." By Andrew Hately (IBM Software Group, Emerging Technologies). For the OASIS UDDI Specification TC. IETF Internet Draft, 'draft-hately-uddi-uri-scheme-00.txt'. July 2004, expires January 2005. "This IETF document reproduces the UDDI keying scheme definition found in the OASIS UDDI Version 3 Specification and is published as an RFC for ease of access and IANA registration. Change control is retained within OASIS..." See the announcement. From IETF: http://www.ietf.org/internet-drafts/draft-hately-uddi-uri-scheme-00.txt.

  • [July 29, 2004] "Auto Industry Seeks to Improve Web Services." By Laurie Sullivan. From InformationWeek (July 29, 2004). "A project being undertaken by leading members of the auto industry next month could facilitate the convergence of much-needed capabilities found in the ebXML transaction standard into the three most widely accepted Web-services specifications. As part of the Automotive Industry Action Group's project to improve visibility within the supply chain, Ford Motor Co., General Motors Corp., and most recently DaimlerChrysler have agreed to work to bring ebXML's encryption, reliability, and security capabilities to the UDDI registry of available services, the Web Services Description Language, XML-based code that carries out Web services requests, and the Simple Object Access Protocol used to transfer the data. EbXML is more advanced than these Web-services protocols, according to research firm Gartner, providing for reliable business collaboration and interenterprise process automation. 'The automotive industry is trying to bring authentication and nonrepudiation to messaging of Web services based on ebXML,' says Gartner Research analyst Frank Kenney. The auto industry's Inventory Visibility and Interoperability project is based on ebXML standards, but the car makers say suppliers already supporting UDDI, WSDL, and Soap would rather see ebXML's benefits brought to those platforms than have to support another standard..."

  • [July 25, 2004] Using BPEL4WS in a UDDI Registry. By Claus von Riegen (SAP) and Ivana Trickovic (SAP). Edited by Luc Clément (Systinet) and Andrew Hately (IBM). July 19, 2004. 23 pages. "BPEL4WS abstract processes describe the observable behavior of Web services. They complement abstract WSDL interfaces (port types and operations) and the UDDI model by defining dependencies between service operations in the context of a message exchange. This technical note describes the relationships between the three models and suggests how BPEL4WS abstract processes can be used in a UDDI Registry." [source PDF]

  • [July 01, 2004] "WebMethods, for One, Believes in UDDI. New Platform Built to Publish Services to a Directory." By Edward J. Correia. From Software Development Times (July 01, 2004). "In the future, all Web services will be published through UDDI. That perhaps unlikely scenario is the outlook for customers of WebMethods Inc., which in June released Enterprise Services Platform, a combination of the company's Fabric, Glue and Integration Platform that it says not only turns any application, service or legacy system into a Web service, but automatically publishes them to a UDDI directory for easier inclusion in future apps. Graham Glass, WebMethods' chief technology officer, said that for developers looking for cohesion as they piece together applications, UDDI is the only game in town. "Web services is the only standard that everybody is supporting. Now, if third-party software comes along and does a UDDI lookup, it will be able to automatically find other services exposed through the platform." Though Fabric has supported the Universal Description, Discovery and Integration spec since version 1.0, Glass said all of Enterprise Services Platform (ESP) is now integrated with the specification..."

  • [June 21, 2004] "Creating Your Own Private UDDI Registry." By Jeff Hanson. From DevX.com (June 21, 2004). "Universal Description, Discovery and Integration (UDDI) specification and protocol work together to form define messages, application programming interfaces (APIs), and data structures for building distributed registries of Web services and storing the business and technical information associated with these services. UDDI is an OASIS standard. There are fundamentally two types of UDDI registries: public registries and private registries. This article shows you how to implement a private registry. The Universal Description, Discovery and Integration (UDDI) specification and protocol work together to form one of the primary components of a complete Web services infrastructure. jUDDI is an open source Java implementation of the UDDI specification for Web services. By following the steps shown in this article, you can use jUDDI to create a private UDDI registry that handles publication, authentication, and inquiry requests... You can use the information provided in a UDDI registry to perform three types of searches: (1) A white pages search returns basic information such as address, contact, and identifiers about a company and its services; (2) A yellow pages topical search retrieves information according to industrial categorizations and taxonomies, such as the NAICS, ISO3166, and UNSPSC classification systems; (3) A green pages service search retrieves technical information about Web services, as well as information describing how to execute these services..."

  • [June 04, 2004] "UDDI as an Extended Web Services Registry. Versioning, Quality of Service, and More." By Adam Blum. From Web Services Journal (June 04, 2004). "This article discusses how UDDI can be used as this more robust registry of extensive information on each Web service. It describes UDDI tModels for categorization and shows how they are used in the 'Using WSDL in a UDDI Registry, Version 2.0' Technical Note to represent all of the information present in WSDL in UDDI. It then describes how the techniques used by the WSDL mapping technical note can be used to represent new classes and attributes of information generally. As enterprises build a critical mass of Web services, they need some way of keeping track of those services. UDDI is an ideal store for such information. Using UDDI's built-in abstractions of business services, binding templates, and tModels referring to interface specifications, UDDI can be used to manage all of the addresses and protocols and formats of those services. Incremental standards in the form of UDDI Technical Notes are emerging for these attributes of Web services and others to allow tracking of this information..."

  • [May 11, 2004] "Infravio Spiffs Up Web Services Registry Idea." By Martin LaMonica. ZDNet News (May 11, 2004). "Start-up Infravio is reviving the notion of a Web services application marketplace to set itself apart in the market for Web services management tools. With its X-registry, Infravio is trying to cash into a long-held idea that never fully got off the ground. Universal Description, Discovery and Integration (UDDI) — one of the first XML-related protocols called Web services — was first developed as a sort of yellow pages to locate available services. The idea was to provide a large repository of available services on the Internet to which anyone could connect. That vision never really took hold, in part because of business reasons. Integrating complex systems between companies proved to be very challenging technically, and corporations tend to work within a network of known partners rather than rent software from a little-known intermediary. Infravio executives said that its X-Registry improves on UDDI to achieve a similar vision of a Web services marketplace. Calling it an 'Amazon.com for Web services,' Infravio president and CEO Jeff Tonkel said X-Registry will give companies a central point for viewing available services and a structured process for keeping track of Web services in use..."

  • [April 21, 2004] "WASP UDDI 5.0 Beta: Support for OASIS UDDI V3 Specification." - "Systinet has announced the Beta availability of WASP UDDI, 5.0, with full support for the OASIS UDDI V3 Specification. Systinet WASP UDDI is the first and only commercial registry to fully support the latest V3 specification, which provides new functionality specifically for private, enterprise deployments. A major advancement in the Version 3 specification is the support for digital signatures. By allowing UDDI entities to be digitally signed, a new level of data integrity and authenticity is delivered by UDDI. Inquirers of a registry can now filter their queries, only requesting data that has in fact been signed. When an inquirer then retrieves and verifies data from a registry, the inquirer can be confident that the data is exactly as the publisher intended it. Using the policy guide that is now part of the Version 3 specification, different UDDI implementations can mold a particular registry given its context. Some UDDI aspects that have been identified as policy decisions include the following: authorization models, data custody and confidentiality, key generation, value set validation, subscription, user publication limits, and audit policy. V3 makes is much easier to search and discover a relevant services. Now it is possible to conduct multi-step queries, use new qualifiers, wildcards and also to sort and handle large result flows. The subscription API set also provides for tracking registry activity and has been updated to support multi-registry environments. In such a way, users can establish a subscription based on a specific query or set of entities that the user is interested in. In the case of a query-based subscription, if the result set changes within a given time span, the user is notified. In the case of entity-based subscription, if the contents of one of those entities were to change, the user is notified. UDDI Version 3 introduces the notions of root and affiliate registries. The existence of a root registry enables its affiliates to share data with the root registry and among themselves with the knowledge that keys remain unique. The notion of registry topologies is thus enabled..."

  • [April 15, 2004] "Using BPEL4WS in a UDDI Registry." By Claus von Riegen and Ivana Trickovic (SAP). OASIS UDDI Spec Technical Committee. Draft Technical Note. Document identifier: 'uddi-spec-tc-tn-bpel-20040415.doc'. April 15, 2004. 24 pages. "BPEL4WS abstract processes complement abstract WSDL interfaces describing behavioral aspects of Web services and providing data needed for integration with business partners. Abstract processes are used to specify the order in which business partners may invoke operations. Therefore it may be also of interest to exchange abstract processes between business partners. Software companies and standards bodies may use a UDDI registry to publish different types of services and business users may populate the registry with descriptions of services they support. BPEL4WS and WSDL may be used to describe service types, protocols that are supported and other deployment details. While it is certainly possible to publish BPEL4WS process definitions in a UDDI registry, no guidelines are available as of today, which specify a common approach for doing that. Without such a common approach, the certainty that users find BPEL4WS process definitions or Web services that implement a given part of such a definition is limited. This technical note provides guidelines for publishing BPEL4WS abstract processes in UDDI. The primary goals of mapping BPEL4WS artifacts to the UDDI model are to: (1) enable the automatic registration of BPEL4WS definitions in UDDI; (2) enable optimized and flexible UDDI queries based on specific BPEL4WS artifacts and metadata; (3) provide composability with the mapping described in the Using WSDL in a UDDI Registry, Version 2 Technical Note document..." See also "Business Process Execution Language for Web Services (BPEL4WS)." [source .DOC]

  • [January 05, 2004] "WASP UDDI 4.6: Extra Features Add to a Solid Product." Reviewed by Brian R. Barbash (Computer Sciences Corporation, Consulting Group). In Web Services Journal Volume 4, Issue 1 (January 2004). If you're looking to deploy a UDDI registry that provides strong standards support, a capable API, and security and management capabilities, look no further than Systinet's WASP UDDI version 4.6. WASP UDDI is a UDDI server that supports UDDI specification versions 1 and 2 as well as the version 3 subscription API. Systinet has also added extensions to the core UDDI specification to provide additional functionality around management, security, inquiries, and other operations. The server can run on top of a number of databases, including Oracle, SQL Server, DB2, PostgreSQL, Sybase, Cloudscape, PointBase, and Hypersonic SQL (included)... Along with a full-featured Web interface, Systinet's WASP UDDI provides a rich, open-source client API written in Java that developers may leverage to create applications that interact with the UDDI repository. For this review, I will be focusing on the supplied Java API and exploring various pieces of the UDDI server's functionality... Both the Web interface and the Java API for the UDDI registry allow elements to be published to the registry. Out of the box, the UDDI registry is populated with sample data and a set of common taxonomies to support the tutorials and exercises in the documentation and allow services to be classified with existing industry standards... Systinet's WASP UDDI server is an easy-to-use, full-featured UDDI registry. In addition to providing support for versions 1 and 2, as well as parts of the version 3 UDDI specification, several enhancements have been provided. The Java API is full featured and does an excellent job of hiding the communications details of interacting with the registry. The additional security and administrative functions provide unique management capabilities for the product. Overall, Systinet's WASP UDDI server is a very solid product..." [print view]

  • [August 25, 2003]   UBR Operators Council Announces Beta Release of UDDI Business Registry for UDDI Version 3.0.    The UDDI Business Registry (UBR) Operators Council has announced the availability of beta nodes for Version 3 of the Universal Description, Discovery, and Integration specification. Composed of members from IBM, Microsoft, NTT Communications, and SAP, the UDDI Operators Council operates the UDDI Business Registry, collecting information from UDDI web services implementations and providing feedback to members of the OASIS UDDI Specification Technical Committee. The UDDI specification "enables businesses to quickly, easily, and dynamically find and transact with one another. UDDI enables a business to describe its business and its services, discover other businesses that offer desired services, and integrate with these other businesses." The UBR announcement highlights four key enhancements in the UDDI Business Registry based upon the UDDI Version 3.0 Committee Specification. (1) Support for User-Defined Keys allows users to create human readable values for keys based on the known concept of domain names. Version 3 recommends the usage of a key scheme based on DNS names rather than formatted Universally Unique Identifier (UUID) notation; this allows publishers to establish a key partition from a DNS record and then generate keys based on that partition. (2) In V3 the UDDI Business Registry (UBR) becomes a Root Registry: the UBR will serve as the recognized root registry for globally unique keys, where affiliate registries will be able to reserve UDDI keys. (3) Version 3 also introduces Portable Keys -- the ability to copy keys between registries without being altered, enabling public and private registries to import information from others. (4) Digital Signatures based upon the W3C/IETF Recommendation are now used. The addition of digital signature support for entities in UDDI enables clients to establish the veracity of data registered in the UBR. By allowing UDDI entities to be digitally signed, a new level of data integrity and authenticity is delivered by UDDI; inquirers of a registry can now filter their queries, only requesting data that has in fact been signed."

  • [August 21, 2003] "UDDI Operators Council Releases Version 3 of the UDDI Business Registry. Beta Version to Include Enhanced Functionality for Companies to Build Secure Web Services Registries. UDDI Operators SAP, IBM and Microsoft to Provide Beta APIs for Public Usage of UDDI Version 3 Free of Charge." - "The Universal Description, Discovery, and Integration (UDDI) Business Registry (UBR) Operators Council announced today the availability of UDDI Version 3 (V.3) beta nodes. The Universal Description, Discovery and Integration protocol is one of the major building blocks that enable successful Web service deployments. UDDI creates a standard interoperable platform that enables companies and applications to quickly, easily and dynamically find and use Web services. 'The beta release of UBR V.3 takes a further step in bringing this important specification closer to successful real-world implementations,' said Charles Abrams, research director, Gartner Research. 'The UDDI Operators Council is providing companies with an early opportunity to explore new functionality when considering extended Web service implementations.' The UDDI V.3 Specification brings the following important capabilities to the UBR: (1) User-Defined Keys: This allows users to create human readable values for keys based on the known concept of domain names. (2) UDDI Business Registry (UBR) as a Root Registry: Once the UBR migrates to V.3, the UBR will serve as the recognized root registry for globally unique keys, where affiliate registries will be able to reserve UDDI keys. (3) Portable Keys: V.3 introduces the ability to copy keys between registries without being altered, enabling public and private registries to import information from others. (4) Digital Signatures: The addition of digital signature support for entities in UDDI enables clients to establish the veracity of data registered in the UBR. UDDI is a cross-industry effort driven by major platform and software providers, as well as marketplace operators and e-business leaders within the OASIS standards consortium. IBM, Microsoft and SAP will provide UDDI V.3 beta nodes. With this beta, the UBR operators continue to provide validation of the UDDI specification through early reference implementations. Early availability of new V.3 features affords tool providers and early adopters publicly available access to this technology. The UDDI Operators Council, which consists of IBM, Microsoft, NTT Communications and SAP, continues to provide support for the momentum in the developer community to harness real-world implementations of the advanced specification. The Operators Council documents and submits their experience with the beta implementation to the OASIS UDDI Specification Technical Committee to help refine and improve the UDDI V.3 Specification..."

  • [July 14, 2003] "Using WSDL in a UDDI Registry, Version 2.0." By John Colgrave (IBM) and Karsten Januszewski (Microsoft). Edited by Anne Thomas Manes and Tony Rogers (Computer Associates). Technical Note produced by the OASIS UDDI Specification Technical Committee. Document Identifier: uddi-spec-tc-tn-wsdl-v2. 42 pages. According to a posting from Tom Bellwood Tom Bellwood (Co-Chair, OASIS UDDI Specification TC), this document was approved as a Committee Technical Note. Send comments to uddi-spec-comment@lists.oasis-open.org. Summary: "This document is an OASIS UDDI Technical Note that defines a new approach to using WSDL in a UDDI Registry." From the Introduction: " The Universal Description, Discovery & Integration (UDDI) specification provides a platform-independent way of describing and discovering Web services and Web service providers. The UDDI data structures provide a framework for the description of basic service information, and an extensible mechanism to specify detailed service access information using any standard description language. Many such languages exist in specific industry domains and at different levels of the protocol stack. The Web Services Description Language (WSDL) is a general purpose XML language for describing the interface, protocol bindings, and the deployment details of network services. WSDL complements the UDDI standard by providing a uniform way of describing the abstract interface and protocol bindings of arbitrary network services. The purpose of this document is to clarify the relationship between the two and to describe a recommended approach to mapping WSDL descriptions to the UDDI data structures. Consistent and thorough WSDL mappings are critical to the utility of UDDI... The primary goals of this mapping are: (1) To enable the automatic registration of WSDL definitions in UDDI; (2) To enable precise and flexible UDDI queries based on specific WSDL artifacts and metadata; (3) To maintain compatibility with the mapping described in the Using WSDL in a UDDI Registry, Version 1.08 Best Practice document; (4) To provide a consistent mapping for UDDI Version 2 and UDDI Version 3; (5) To support any logical and physical structure of WSDL description. This mapping prescribes a consistent methodology to map WSDL 1.1 artifacts to UDDI structures. It describes an approach that represents reusable, abstract Web service artifacts, (WSDL portTypes and WSDL bindings) and Web service implementations (WSDL services and ports). Tools can use this mapping to generate UDDI registrations automatically from WSDL descriptions. This mapping captures sufficient information from the WSDL documents to allow precise queries for Web services information without further recourse to the source WSDL documents, and to allow the appropriate WSDL documents to be retrieved once a match has been found. Given that the source WSDL documents can be distributed among the publishers using a UDDI registry, a UDDI registry provides a convenient central point where such queries can be executed... This document builds on Using WSDL in a UDDI Registry, Version 1.08, providing an expanded modeling practice that encompasses the flexibility of WSDL. The primary difference between this mapping and the one described in the existing Best Practice is that this mapping provides a methodology to represent individual Web services artifacts."

  • [April 15, 2003] "Using Categorization To Distinguish Entries And Create Communities in UDDI. Developing and Using a Validation Service for Checked Categories in UDDI." By Matt Rutkowski, Andrew Hately, and Robert Chumbley (UDDI Development, Emerging Technologies, IBM). From IBM developerWorks, Web services. April 2, 2003. ['This article describes the power of categorization in UDDI to differentiate data according to standard taxonomies and how to use categorization to create a subset of the registry that has been screened by an external party. The use of the UDDI validation service to create the Speed-start Web services community within the IBM UDDI Test registry is described in this article. This Speed-start community is an example of a set of public data that can be distinguished from all of the remaining public data within the same UDDI registry using a simple category based query. UDDI entries that are returned as part of the response to that query have been evaluated at publication time by the Speed-start validation service to ensure that they are Internet accessible Web services.'] "UDDI provides a mechanism to include standard taxonomies that can be used to describe each entry using as many industry standard search terms as needed. Each business, service, or technical model can contain a 'Category Bag' which holds keyed references (that is, categorization codes, locators, or keywords) that can specifically describe its type of business, physical location, and even the exact products and services it offers. These keyed references contain a reference to the classification system or taxonomy, a text field containing the value within that taxonomy and a text field for a human readable description. Using this method of categorization, the UDDI Inquiry API can quickly and efficiently connect businesses and services to exactly the customers that need them... Three of the UDDI taxonomies [NAICS, UNSPSC, GCS] are standards for categorizing entries. The fourth taxonomy, UDDI classifications, is a taxonomy that was developed as part of the UDDI specification to provide useful values for categorizing the technical information of Web services. The last taxonomy is useful for associating keywords with an entry, especially those that are not part of the name of the entry. Each of these category systems is uniquely identified by a UDDI entry called a tModel (Technical Model) and can be referenced using its tModelKey... The article provides a general overview of categorization and how it can be used in conjunction with validation services called by UDDI registries to provide a community or screened set of results according to category system specific criteria. The example of the Speed-start community is a simple example of the power of contextual validation services that can greatly enhance the quality of results corresponding to queries for data referencing a particular category or identifier system. Using the information in this article, it should be possible to develop services that greatly enhance the results from UDDI registries such as service quality or reference services..."

  • [April 09, 2003] "This Could Be the Year for UDDI. IBM Exec Touts Upcoming Upgrade." By Paul Krill. In InfoWorld (April 09, 2003). "An upcoming version of UDDI could give the Web services directory technology the boost it needs to spur adoption, according to an IBM official at a conference on Wednesday. Version 3 of UDDI, which actually was formulated last summer, is likely to be voted on by OASIS (Organization for the Advancement of Structured Information Standards) later this year, said Tom Bellwood, senior technology staff member in IBM's emerging technologies group and co-chairman of an OASIS technical committee on UDDI. Bellwood gave a presentation on UDDI Version 3 at the IBM developerWorksLive conference... Version 3 will help UDDI be adopted more in publicly available applications rather than the private, behind the firewall where it has primarily been used, said Bellwood during an interview following his presentation. 'In a public environment, I think that it needs a lot of the features in Version 3,' he said, citing features such as security and a multi-registry model. The security model in Version 3 allows for use of digital signatures and for querying based on data that has been signed. Digital signatures bring trust, integrity, and reliability to UDDI, Bellwood said. Users also can find out who published a specific directory item and data can be moved between registries. 'I think Version 3 is probably the basis for which really all UDDI work will be done' in the future, Bellwood said. The multi-registry feature enables private and public registries that can interact with each other. There will be root and affiliate registries, with root registry acting as authority for key spaces, which are analogous to DNS names. The root registry delegates key partitions. Affiliate registries follow rules of a particular root registry and are important for sharing of information but not replication... Additionally, Version 3 is schema-driven, in which schemas have been separated for improved interoperability, Bellwood said. Version 3 also enables development of industry-specific taxonomies, has peer-based replication for improved scaling, and has improved internationalization..." See the UDDI Version 3 Features List.

  • [March 21, 2003] "Using WSDL in a UDDI Registry, Version 2.0." Edited by Anne Thomas Manes and Tony Rogers. Technical Note produced for the OASIS UDDI Specifications TC. Document identifier: uddi-spec-tc-tn-wsdl-20030319-wd. Announced in a posting by John Colgrave; comments are welcome for the next thirty days. The TN defines a new approach to using WSDL in a UDDI Registry. "The Universal Description, Discovery and Integration (UDDI) specification provides a platform-independent way of describing and discovering Web services and Web service providers. The UDDI data structures provide a framework for the description of basic service information, and an extensible mechanism to specify detailed service access information using any standard description language. Many such languages exist in specific industry domains and at different levels of the protocol stack. The Web Services Description Language (WSDL) is a general purpose XML language for describing the interface, protocol bindings, and the deployment details of network services. WSDL complements the UDDI standard by providing a uniform way of describing the abstract interface and protocol bindings of arbitrary network services. The purpose of this document is to clarify the relationship between the two and to describe a recommended approach to mapping WSDL descriptions to the UDDI data structures. Consistent and thorough WSDL mappings are critical to the utility of UDDI. The primary goals of this mapping are: (1) To enable the automatic registration of WSDL definitions in UDDI; (2) To enable precise and flexible UDDI queries based on specific WSDL artifacts and metadata (3) To maintain compatibility with the mapping described in the Using WSDL in a UDDI Registry, Version 1.08 Best Practice document; (4) To provide a consistent mapping for UDDI Version 2 and UDDI Version 3; (5) To support any logical and physical structure of WSDL description. This mapping prescribes a consistent methodology to map WSDL 1.1 artifacts to UDDI structures. It describes an approach that represents reusable, abstract Web service artifacts, (WSDL portTypes and WSDL bindings) and Web service implementations (WSDL services and ports). Tools can use this mapping to generate UDDI registrations automatically from WSDL descriptions. This mapping captures sufficient information from the WSDL documents to allow precise queries for Web services information without further recourse to the source WSDL documents, and to allow the appropriate WSDL documents to be retrieved once a match has been found. Given that the source WSDL documents can be distributed among the publishers using a UDDI registry, a UDDI registry provides a convenient central point where such queries can be executed..." Also in PDF format. [cache]

  • [March 04, 2003]   UDDI Version 2 Specification Submitted for Approval as an OASIS Open Standard.    On behalf of the OASIS UDDI Specifications Technical Committee, TC Co-Chairs Tom Bellwood and Luc Clément have submitted the UDDI v2 Committee Specifications for consideration as an OASIS Open Standard. UDDI v2 components include the UDDI Version 2 API Specification, Data Structure, XML Schema, Replication Specification, XML Replication Schema, XML Custody Schema, Operator's Specification, WSDL Service Interface Descriptions, and UDDI tModels. "Universal Description, Discovery and Integration, or UDDI, is the name of a group of web-based registries that expose information about a business or other entity and its technical interfaces (or APIs). These registries are run by multiple Operator Sites, and can be used by anyone who wants to make information available about one or more businesses or entities, as well as anyone that wants to find that information. There is no charge for using the basic services of these operator sites." Updated announcement 2003-05-20: "UDDI v2 Ratified as OASIS Open Standard. Building Block for Web Services Advances Within Open Process."

  • [February 26, 2003] "Providing a Value Set For Use in UDDI Version 3." Edited by Claus von Riegen (SAP). With contributions from Tom Bellwood (IBM). TC Technical Note produced by the UDDI Specification Technical Committee. Document identifier: uddi-spec-tc-tn-valuesetprovider-20030212. Abstract: "Through the use of value sets in UDDI registries, businesses are able to find each other and the services that meet their needs. This document provides guidelines for providers of value sets on how to model, register, and validate their value sets for use in UDDI Version 3." Topic: "In UDDI, a value set represents a set of values that can be used to provide meaning or context to a UDDI entity. Category, identifier, and relationship type systems are all value sets. Value sets play an important role within UDDI, because it is through their use that businesses are able to find each other and the services that meet their needs.... This paper guides the providers of value sets in the creation of value set services and in the registration of the value sets and these external value set services, following the recommended policies outlined in Chapter 9 of the UDDI Version 3 Specification..." Note: A 2003-02-24 posting from Tom Bellwood and Luc Clément (Co-chairs, OASIS UDDI Specification TC) reported that this document had been approved as a UDDI Spec TC Technical Note.

  • [February 25, 2003] "UDDI Finds a Role After All." By Keith Rodgers. From LooselyCoupled.com. (February 20, 2003). "Two years after the fanfare of its introduction, UDDI adoption levels remain low. But users are beginning to see UDDI directories filling a practical role: adoption of UDDI is growing among web services pioneers; directory capabilities become more critical as the volume of services increases; but UDDI's origins have left design challenges; most users will acquire UDDI as a component of their web services platform... The latest specification of UDDI, version 3, has moved on from its B2B origins, adding features designed to meet users' needs for private registries. These include, for example, procedures for putting security keys into requests, or for enabling information transfer from one private registry to another. That said, the twists and turns in UDDI's evolution have also influenced its design and left some technical oddities. UDDI defines three registry components, which in layman's terms are akin to the Yellow Pages phone book -- or more precisely, to the trio of white, yellow and green pages. The white pages list companies' contact details and the key services they provide; the yellow pages categorize businesses using agreed taxonomies, including where they operate; and the green pages provide the technical data other companies need in order to take advantage of the services on offer. These three components will become useful to various individuals when organizations start to run between 20 to 50 services, suggests Mukund Balasubramanian, founder and chief technology officer of Infravio. Developers, for example, will require information about services as they're built -- what resources went in, what configurations were used and so forth. System administrators will want to look at the services from the perspective of how they were deployed -- which servers they're running on, for example, and what the loads are. The business user taxonomy, meanwhile, will help end users find the services they need... Increasingly, the question of how and when to adopt UDDI will be taken by the vendors rather than their customers. A private UDDI registry is already built into the latest release of IBM's WebSphere web service platform, and other vendors are not far behind. This may save organizations the trouble of getting their heads round what UDDI is or why it's important, but it will leave questions such as managing service quality and the degree of interoperability with other platforms unresolved. Ironically, those were the very same problems that stopped enterprises from eagerly adopting the B2B hubs of the dot-com boom. UDDI may have secured its place in the web services firmament by sidestepping such issues, but customers won't find it so easy to avoid facing up to them..."

  • [February 04, 2003] "What's New in UDDI 3.0 - Part 2." By Frank Sommers. From WebServices.Org. February 03, 2003. ['The second in a series of articles that provide an in-depth review of the most recent UDDI (Universal Description, Discovery, and Integration) Web service registry standard.'] "While the description of data structures takes up about half of Version 1 and 2 of the UDDI specifications, the other half defines the manner in which you can interact with those data structures. That interaction occurs via UDDI's public, or programmer's, API. That API is grouped into API sets according to functionality. The UDDI specifications define those API sets via the XML messages that must exchange between a UDDI registry and a registry client. Those XML messages are transmitted via the SOAP protocol... The most important API sets define the publishing and querying operations for a UDDI registry... Versions 3's most significant API changes concern the addition of four new API sets, and modifications to the semantics of existing API functions. The latest changes result from feedback during UDDI's two years of history, and aim to ease the development of business-to-business e-commerce applications... The UDDI 3 subscription API allows WidgetsRUs to be automatically notified when a new supplier publishes its Web service, or when an existing supplier's Web service registration changes. That eliminates the need for periodic administrative querying of UDDI, and makes incorporating new suppliers in the internal MIS system more timely... Note that the UDDI 3 subscription API is an optional API set: A UDDI registry is not required to support it. While it is a very useful feature in support of business-to-business e-commerce, it remains to be seen how many UDDI 3-compliant registries will offer it..." See also: (1) "What's New in UDDI 3.0 - Part 1"; (2) "UDDI Version 3 Features List".

  • [December 11, 2002] "Novell Adds Secure Identity Management to Key Web Services Standard." - "On December 11, 2002 Novell announced the availability to developers of a new Universal Description, Discovery and Integration (UDDI) server that adds secure identity management to the UDDI standard. Novell Nsure UDDI Server is based on Novell's market-leading eDirectory software and is the first deliverable of the company's Destiny roadmap for eDirectory. Novell has extended its secure identity management expertise to a key Web services standard to help businesses more easily and confidently deploy Web services. The company today announced the availability to developers of a new Universal Description, Discovery and Integration (UDDI) server that adds secure identity management to the UDDI standard, bolstering the security and simplifying the management of Web services registries. Novell Nsure UDDI Server is based on Novell's market-leading eDirectory software and is the first deliverable of the company's Destiny roadmap for eDirectory. Since its inception in 2000, adoption of the UDDI standard has been limited, partly because initial Web services deployments have been relatively small, but also because the standard lacks adequate provisions to ensure the security and management of registered services. With the delivery of a UDDI server based on eDirectory, Novell is attacking those limitations head on... Novell Nsure UDDI Server allows businesses to register Web services and make them available to internal or external users, while leveraging the security and management inherent in eDirectory. Users, whether publishing or consuming services, can be required to first authenticate to the directory and verify their identity. Equally important, those users, their access rights, and the registered Web services can be easily managed with eDirectory tools like Novell iManager, which are familiar to most network administrators... Novell Nsure UDDI Server will be available December 17, 2002 for free download..."

  • [December 02, 2002] "Traversing the Tree: Using the 'get_relatedCategories' API in UDDI Services." By Karsten Januszewski (Microsoft Corporation; UDDI Blog). From Microsoft MSDN Library. November 2002. ['Karsten Januszewski explains how and why to use the get_relatedCategories API, an extension API for accessing and retrieving a list of values within a given categorization scheme in a Microsoft UDDI node. '] "The ability to use categorization schemes to classify data in Universal Description Discovery and Integration (UDDI) is key to the UDDI mission of description and discovery. While the ability to categorize UDDI entries is a core part of the UDDI specification, the specification provides no API facility for querying to retrieve a list of values within a given categorization scheme. In order to address this need, Microsoft UDDI nodes (both the publicly available UDDI Business Registry node as well as private UDDI Services nodes available in Microsoft Windows .NET Server 2003) provide an extension API for accessing this information called the get_relatedCategories API. This paper explains how and why to use this API. There are several reasons why one might want to gain access to the set of values of a categorization scheme in UDDI: (1) Writing custom user interfaces to UDDI; (2) Providing categorization metadata when installing applications that register themselves in UDDI; (3) Using UDDI to dynamically configure applications; one scenario for using UDDI is as an abstract layer between Web services and their clients. In particular, clients might query UDDI at run time to determine the best service to bind to. Because those queries may be based on categorization information, the client may need to dynamically navigate a categorization scheme to discover services... The get_relatedCategories API is a powerful enhancement to UDDI provided with the Microsoft UDDI Services shipping with Windows .NET Server 2003. It allows developers to access and traverse the hierarchy of a taxonomy that has been imported into a UDDI Services instance, giving developers the freedom to create applications that take advantage of the UDDI metadata strategy..." Note in this connection the posting by Luc Clément in response to the question "Do we have a schema to describe a taxonomy with all parent-child relationships, possible values and all?" -- [Luc:] "Unfortunately, there is nothing that has been published by the UDDI.org Working Group or this TC to date. This is clearly an area that deserves some attention. To support the needs of Microsoft's UDDI customers, Microsoft has created a schema and an API to navigate and retrieve valued from a given value set. The API is entitled the get_relatedCategories. The schema used to support these value sets is available at http://uddi.microsoft.com/extensions.xsd..." See also "The Importance of Metadata: Reification, Categorization and UDDI." [cache .XSD]

  • [December 02, 2002] "Using WSDL in a UDDI Registry." UDDI Spec TC Best Practice document. Reference: Version 1.08, uddi-spec-tc-bp-using-wsdl-v108-20021110. 12 pages. Edited by John Colgrave (IBM) and Karsten Januszewski (Microsoft). Contributors: Francisco Curbera (IBM), David Ehnebuske (IBM), and Dan Rogers (Microsoft). A posting from Luc Clément (Co-chair, OASIS UDDI Spec TC) announced the results of a TC vote which approved version 1.08 of Using WSDL in a UDDI Registry as a Best Practice document. A Best Practice "is a non-normative document accompanying a UDDI Specification that provides guidance on how to use UDDI registries. Best Practices not only represent the UDDI Spec TC's view on some UDDI-related topic, but also represent well-established practice." Using WSDL in a UDDI Registry "describes the current Best Practice for constructing UDDI entities from, or relating to, WSDL descriptions of web services." From the Introduction: "The Universal Description Discovery and Integration (UDDI) specification provides a platformindependent way of describing services, discovering businesses, and integrating business services using the Internet. The UDDI data structures provide a framework for the description of basic business and service information, and architects an extensible mechanism to provide detailed service access information using any standard description language. Many such languages exist in specific industry domains and at different levels of the protocol stack. The Web Services Description Language (WSDL) is a general purpose XML language for describing the interface, protocol bindings and the deployment details of network services. WSDL complements the UDDI standard by providing a uniform way of describing the abstract interface and protocol bindings of arbitrary network services. The purpose of this document is to clarify the relationship between the two, describe how WSDL can be used to help create UDDI business service descriptions."

  • [October 14, 2002] "UDDI and WSIL for e-Science." By Rob Allan, Dharmesh Chohan, Xiao Dong Wang, Mark McKeown, John Colgrave, and Matthew Dovey. From the CLRC e-Science Centre and Distributed Computing Programme. ['A UK e-Science UDDI registry is being developed to integrate e-Science projects and Virtual Organisations into a Web and Grid services framework. This paper provides the technical background to this project, which complements other sources of information such as the NeSC project database.'] "In this paper we describe how an private UK e-Science UDDI registry or Web Services Inspection document hosted by the Grid Support Centre might be used to register information about e-Science Virtual Organisations and to enable inter-working between them by exposing their contacts and service points. We propose using UDDI and WSIL to provide APIs for information about UK e-Science projects and also show how individual projects might use the same technology. Examples of the latter are the CLRC Integrated e-Science Environment project (IeSE) and EPSRC's MyGrid. These show how UDDI could be used within a single e-Science project for discovery of its own businessEntities and services by high-level components such as applications and portals. We believe that by providing interfaces to e-Science projects using (proposed) Web services standards, such as UDDI and WSIL, it will facilitate commercial uptake. A partly moderated top-level service will build confidence, allow for testing but still provide the capability to register with the worldwide Universal Business Registry via the publisherAssertion capability as projects become more mature and wish to expose their services to international partners. It nevertheless remains to be seen how the proposed services could be used to enable electronic contract negotiation via the so-called 'tModels'. Finally, appendices describe UDDI and WSIL implementations and a proposed architecture for accessing Web services through a firewall using a proxy service. Implementations of this architecture will show if the performance is acceptable for a variety of purposes... We outline how UDDI might be used as a programmatic Web services information directory for e-Science projects and for services within a single project providing its community with multiple 'views' of sub-projects. UDDI will probably need to be supplemented with a 'top-level' WSIL document accessible from the UK Grid Support Centre Web site. The UDDI and WS-Inspection sources can be cross referenced. A private UDDI for the projects of the UK e-Science Programme offers the chance to test the publication of Web services and provide some degree of assurance that the published services will be acceptable to the wider community. Services may also be published to the Universal Business Registry and the publisherAssertion mechanism of UDDI v3.0 can be used to guarantee that they do belong to the programme..." [PDF format, cache]

  • [October 09, 2002] "A Global Universal Description, Discovery, and Integration Repository Is Unlikely Part of Web Services in Short Term, Says IDC." By [IDC Staff]. Summary from IDC Bulletin #27838 "UDDI in the eMarketplace: The Right Role for the Repository?," by Rob Hailstone. August 20002. "The concept of a global universal, description, discovery, and integration (UDDI) repository has received much criticism as a standard component of Web services architecture due to the lack of business demand for such an implementation. According to IDC, the need for a UDDI repository is apparent at the corporate level, but on a global scale it is difficult to envision how a repository could be policed such that it serves as a benefit, rather than hazard, to business. 'The secret lies in the repository being operated by a trusted third party, and the most likely type of organization to fill this role will be the emarketplace,' said Rob Hailstone, director of IDC's Systems Infrastructure Software research. 'IDC believes that repositioning emarketplaces around Web services and featuring the UDDI repository would be viable within the next two to three years. However, initial adoption rates are likely to be low until demand is driven by leading user organizations.' According to IDC, the second phase of Web services deployment, where usage is predominantly between organizations, has to be successful if the more visionary later phases are to have any chance of becoming reality. UDDI will play an important role enabling this second phase, but implementation must be in a controlled manner if the expected benefits are to be achieved. IDC believes that UDDI deployment within the infrastructure of emarketplaces provides the level of control required within a format that creates business benefits for service providers and consumers as well as the operators of emarketplaces..."

  • [October 08, 2002]   NTT Communications Launches Asia's First UDDI Registry.    NTT Communications Corporation has announced the October 9, 2002 launch of "Asia's first UDDI Business Registry based on the Universal Description, Discovery and Integration (UDDI) specifications, joining IBM, Microsoft and SAP in providing a completely open public registry with a standard access method for companies to register their services and search for business partners' services online." In July 2002 NTT Com and IBM announced a collaborative arrangement for building NTT Com's UDDI Business Registry using IBM's WebSphere and DB2 products and technologies. "The UDDI Business Registry is an online directory that enables companies to register, search and dynamically share information completely free of charge. NTT Com joined the UDDI Operators Council in December 2001 to become Asia's first UDDI Business Registry node operator. Information is registered in a unified format as defined by the UDDI specifications. Information registered in the database of each registry node operator is regularly copied to the other operators' databases, assuring a consistent, worldwide network of registered information. As part of registering its own services in the registry, NTT Com plans to develop new business-to-business (B2B) Web Services and thereby establish the company as a new leader in this field. Like the registries currently operated by IBM, Microsoft and SAP, NTT Com's registry will be based on the UDDI Version 2 specifications." [Full context]

  • [September 30, 2002]   IBM alphaWorks Releases UDDI Registry Extensions.    An IBM alphaWorks development team has released a package of extensions that enhance IBM WebSphere UDDI product with advanced search capabilities. These UDDI Registry Extensions support Version 1.1.1 of the IBM WebSphere UDDI Registry. The new UDDI Registry Extensions provide "advanced search capabilities that enable the formation of complex queries comprising search criteria from two standard UDDI 'find' APIs, find_business and find_service, all in one query. With these advanced search capabilities, requesters can find businesses with services of specific names or in a specific category and vice versa to find services owned by businesses that match specified criteria. Such capabilities are not available with current UDDI search technology and these searches cannot be done without much effort. To make equivalent queries with the current UDDI search technology, the client search requester must perform two steps: (1) Issue two queries: a find_business query and a find_service query, and (2) Process the two sets of results returned by the queries and perform the appropriate intersection of the results, which is complex and error-prone." [Full context]

  • [September 19, 2002] "The Importance of Metadata: Reification, Categorization and UDDI." By Karsten Januszewski (Microsoft Corporation). From the Microsoft XML Web Services Developer Center (September 2002). ['Look behind the UDDI metadata structure to see how to best employ it within a UDDI registry, both in the UDDI Business Registry (UBR) and in UDDI Services of Microsoft Windows .NET Server; see how to create custom categorization schemes that allow users to solve particular problems in description and discovery.'] "Categorization is arguably the most important feature of Universal Description, Discovery and Integration (UDDI), yet it is the least understood. The ability to attribute metadata to services registered in UDDI, and then run queries based on that metadata is absolutely central to the purpose of UDDI at both design time and run time. This article will explain the thinking behind the UDDI metadata structure and then demonstrate how to best employ that metadata structure within a UDDI registry, both in the UDDI Business Registry (UBR) and in UDDI Services of Windows .NET Server. It explains how to create custom categorization schemes that allow users to solve particular problems in description and discovery... UDDI provides typed metadata through several means: First, three of the four central entities in UDDI (providers, services and tModels) can be adorned with what might be thought of as property bags: collections of typed name/value pairs that describe that given entity. Each of the properties in the bag comes from a known classification system... Adorning UDDI entities with these property bags provides entities with the critical metadata and context that can be used to discover and consume them. The corollary to adorning an entity with properties is the ability to search for that entity based on those properties. The UDDI API was designed to support a complex range of queries based on metadata ascribed to these bags. Queries are written that look for properties based on the classification scheme they are associated with. In other words, in writing a query "to find services in the United States", one must provide not only the appropriate value that represents the United States but also the classification scheme from which that value originates. In this way, queries can be written that have contextual intelligence about the properties being searched for. Other features make the UDDI query engine able to handle a range of scenarios. For example, queries can do an exact match of all the properties in a bag or can match just one property in a bag. Or, a query can search across bags contained in both providers and services. The querying capacity in the UDDI API provides a great deal of flexibility in terms of writing focused, precise queries. Through these two parallel facilities -- adorning properties to entities and searching for entities based on well-known properties -- UDDI entities are reified. Below, the article will delve into exactly how to accomplish this... Classification and typed metadata is key to the ability of UDDI to solve the problems of reification of data both in the enterprise and in the public sphere. Well-architected Web service software applications will employ UDDI as an infrastructure, taking advantage of the many possibilities of employing this complex categorization system to different entities for both design-time and run-time usage..."

  • [September 10, 2002] "Finding the Right Formula For UDDI. Web-services Specification to Play Key Role." By Jeffrey Schwartz. In VARBusiness (September 06, 2002). "As customers start using Web services to link disparate applications, they will need a way to efficiently organize and keep track of all those Web services. Most experts believe they will do that through repositories based on a specification called universal description and discovery interface (UDDI). Some believe UDDI will be as pervasive in directories and repositories as XML is in defining metadata and SOAP is in encapsulating software components. Simply put, UDDI makes it possible to search any registry for specific Web services, such as business rules and SOAP-based components. In addition to helping users and applications find specific Web services, UDDI will allow them to query data that describes how those services are used. 'UDDI is really a registry of Web services, wherever they're deployed, and descriptions of how to interact with them,' says Chris Kurt, program manager for UDDI.org at Microsoft and a member of Microsoft's XML standards team. UDDI also specifies a set of APIs to interact with the registry and provides references on how to interface with applications. UDDI registries have basic white and yellow pages models for finding services. Solution providers will increasingly find UDDI implemented in various forms of repositories, including application servers, middleware, databases and directories. IBM is already shipping a UDDI registry based on its WebSphere application server suite; Novell recently announced plans to release a UDDI server by year's end that will run atop its eDirectory software; and Microsoft's forthcoming .Net servers will support UDDI through microcode in the new server platforms and via its SQL Server database. While UDDI will be key to tying together Web services, the market is still nascent. 'Everyone's trying to get mind share,' says Michael Neuenschwander, an analyst at the Burton Group. In July, work on UDDI was turned over to Oasis, a standards body that governs e-business and Web-services standards, including XML. The move coincided with the release of version 3 of the UDDI spec, which gives the standard key enterprise capabilities, such as support for XML-based security and policy management, internationalization and a subscription API that generates messages when changes are made to a UDDI repository. And late last month, Oasis announced the formation of a technical committee that will develop the technical standards and best practices. Members of the technical committee include BEA Systems, Hewlett-Packard, IBM, Microsoft, Novell, Oracle, Sun and Verisign, among others... In order for Web services to proliferate, customers and solution providers should be looking at UDDI as a key component of that infrastructure. Sutor describes it as a catch-22. 'You need to have a registry to get the growth of Web services, but you need a whole bunch of Web services to put in the registry to make it useful,' Sutor says. So, what will make UDDI useful? It's likely to proliferate within organizations for sharing business logic among applications. For example, Microsoft's Kurt says, if an enterprise wants to make a change-of-address service originally built for an HR application for other apps, a UDDI registry can help internal developers, or even end users, find the software components and business rules for using those programs..."

  • [August 30, 2002] "UDDI Takes Step Forward but Isn't Ready for Deployment." By Ray Wagner and John Pescatore (Gartner Research). Gartner FirstTake. Reference: FT-18-0859. 30 August 2002. ['Most major IT vendors support OASIS's new committee to develop the UDDI protocol. However, UDDI will achieve widespread use only at a late stage in the deployment of Web services.'] "On 28 August 2002, the Organization for Structured Information Standards (OASIS) announced the UDDI Specification Technical Committee to oversee the development of Universal Description, Discovery, and Integration (UDDI), a Web service protocol. More than 20 major IT companies have said they will participate, including most major software infrastructure providers... The unprecedented cooperation by industry participants will do much to secure widespread acceptance of UDDI, which provides a common format for enterprises to identify and link to new Web services... However, this specification may not prove as important as other Web service protocols with which it is normally associated, such as Simple Object Access Protocol (SOAP) and the Security Assertion Markup Language (SAML), because UDDI will achieve widespread use only at a late stage in the deployment of Web services. In general, enterprises will not need UDDI initially, either behind the firewall or when they deal with trusted business partners. Supporters will have to resolve many security issues related to UDDI before enterprises can safely expose service information via UDDI. Standard mechanisms need to be defined for such functions as supporting granular access, denial-of-service protection and nonrepudiation. Gartner recommends that enterprises evaluate the output of the UDDI committee for in-depth treatment of UDDI security issues before planning externally exposed use of UDDI. Gartner also believes that secure use of Web services will greatly accelerate if the vendors participating in the UDDI committee also participate aggressively in the SAML, Web Services Security (WS-Security), Liberty Alliance and other Web service initiatives related to security..." Also in PDF format [cache]

  • [August 29, 2002]   OASIS UDDI Specification Technical Committee Continues Work on Web Services Registry Foundations.    A UDDI Specification Technical Committee has been formed within the OASIS UDDI Member Section to "continue work on the Web services registry foundations developed and published by UDDI.org." The new technical committee has been chartered to support: "specifications for Web services registries and Web service interfaces to the registries; replication or synchronization mechanisms across multiple implementations; and security facilities for access or manipulation of the registry and maintaining data integrity." Specifically, the OASIS UDDI Specification TC will: "(1) Accept as input the UDDI version 2.0 and 3.0 specifications published by the members of UDDI.org; (2) Produce as output a specification for Web Services Description, Discovery and Integration; this specification will reflect refinements and changes made to the submitted version of UDDI that are identified by the UDDI Specification TC members, and for additional functionality within the scope of the TC charter; (3) Liaise and/or forge relationships with other Web services efforts to assist in leveraging UDDI as a part of their specifications or solutions; (4) Coordinate with the chairs of the other related OASIS Technical Committees via Joint Committees as appropriate; (5) Coordinate with the UDDI Business Registry operators in order to get early feedback from their implementation experiences; (6) Oversee ongoing maintenance and errata of the UDDI specifications." Members of the OASIS UDDI Specification Technical Committee include BEA Systems, Cincom, Computer Associates, E2open, Entrust, Fujitsu, Hewlett-Packard, IBM, Intel, IONA, Microsoft, MSI Business Solutions, NerveWire, Novell, Oracle, Perficient, SAP, SeeBeyond, Sun Microsystems, TIBCO, Verisign, webMethods, XML Global, and others. [Full context]

  • [August 29, 2002] "XML Web Services: Is the End Near?" By Darryl K. Taft. In