OASIS UDDI Specification TC

FAQ

  1. What is UDDI?
  2. What is the current status of UDDI?
  3. What requirements are currently under consideration?
  4. How do people use UDDI?
  5. How does UDDI relate to other Web services-related standards projects at OASIS, W3C, and WS-I?
  6. Where can I find information on available UDDI product and development tools?

Details

  1. What is UDDI?

    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 specifications define:

    1. SOAP APIs that applications use to query and to publish information to a UDDI registry

    2. XML Schema schemata of the registry data model and the SOAP message formats

    3. WSDL definitions of the SOAP APIs

    4. UDDI registry definitions (technical models - tModels) of various identifier and category systems that may be used to identify and categorize UDDI registrations

    The OASIS UDDI Spec TC also develops technical notes and best practice documents that aid users in deploying and using UDDI registries effectively.

  2. What is the current status of UDDI?

    The UDDI V2.0 specifications have been approved as an OASIS Standard. Numerous vendors and open source communities supply products that implement the UDDI V2.0 standard.

    The UDDI V3.0 specification has been approved as an OASIS Committee Draft. Once referred to as a "Committee Specification" the specification will be referred to as "Committee Draft" henceforth. Many vendors are developing products that implement the UDDI V3.0 specifications.

    The OASIS UDDI Spec TC is currently gathering requirements for the next revision of the specification.

  3. What requirements are currently under consideration?

    Currently the OASIS UDDI Spec TC is working on improving security, trustworthiness, semantics, and alignment with the Web Service Architecture and other standards.

  4. How do people use UDDI?

    A business may deploy one or more private and/or public UDDI registries. A private registry permits access to only authorized users. A public registry does not restrict access to the registry. A business may choose to deploy multiple registries in order to segregate internal and external service information. An internal registry supports intranet applications, while an external registry supports extranet applications. Industry groups may deploy a UDDI registry to support public or private exchanges.

  5. How does UDDI relate to other Web services-related standards projects at OASIS, W3C, and WS-I?

    UDDI is complementary to other Web services-related projects at OASIS and W3C, such as SOAP, WSDL, WSBPEL, WSRP, and WS-Security. WS-I adopts and further profiles the UDDI V2.0 standard in the WS-I Basic Profile.

  6. Where can I find information on available UDDI products and development tools?

    UDDI XML.org provides a directory of resources containing product listings, case studies, presentations, white papers, and other useful materials.

 

TOP OF PAGE