OASIS UDDI Specification TC

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200208/msg00002.html

The charter for this TC is as follows.


OASIS UDDI Specification Technical Committee (UDDI)

Statement of Purpose

The purpose of the Universal Description, Discovery, and Integration (UDDI) Specification TC is to continue work on the Web services registry foundations developed and published by UDDI.org [1]. The UDDI specifications form the necessary technical foundation for publication and discovery of Web services implementations both within and between enterprises.

The Technical Committee will take advantage of the OASIS provided services for such things as e-mail lists and archives, and also web pages for tracking progress. E-mail archives will be visible to the public.

Relationship to Existing Activities:

Where appropriate, the UDDI Specification TC will foster collaborative relationships and liaisons with other activities.

List of Deliverables

The scope of the UDDI Specification Technical Committee is the support of Web services discovery mechanisms in the following areas:

  1. Specifications for Web services registries and Web service interfaces to the registries.
  2. Replication or synchronization mechanisms across multiple implementations.
  3. Security facilities for access or manipulation of the registry and maintaining data integrity.

The UDDI specifications will use implementation and language neutral XML formats defined in XML Schema where appropriate.

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; see http://www.uddi.org/specification.html
  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.