|
UDDI Spec TC Committee
Technical Notes
The UDDI Spec TC Technical Notes
Process is described below.
Documents
-
Providing a Taxonomy for Use in
UDDI Version 2 Taxonomies and identifier systems play an important role
within UDDI. It is through categorization and identification that businesses are
able to find each other and the services that meet their needs. Versions 1 and 2
of UDDI cite three common categorization schemes to encourage registrants to
categorize their businesses, services and service descriptions. There are dozens
of other taxonomies available that are newer, gaining in popularity, or targeted
at specific constituencies. While UDDI does not mandate use of these taxonomies,
it is imperative that they be made available to those who would benefit from
using them.
This paper guides the providers of taxonomies and identifier systems in the
registration of their taxonomies and through the process of providing a
validation service. Since taxonomies and identifier systems are handled in the
same way, for conciseness this paper refers to both as "taxonomies".
HTML /
PDF
(50 KB)
-
Providing A Value Set For Use In UDDI Version 3
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.
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.
HTML /
PDF
(50 KB)
Process
The UDDI Spec TC from time to time
publishes
Best Practices and Technical Notes. The contents of these documents are not
a part of the specifications.
A Technical Note is a non-normative document accompanying the UDDI Specification
that provides guidance on how to use UDDI registries. While Technical Notes
represent the UDDI Spec TC�s view on some UDDI-related topic, they may be
prospective in nature and need not document existing practice.
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.
Proposal
A technical note may be written about a real implementation or application of
UDDI to solve a business or technical problem, or it may be written to provide
recommendations regarding interaction between UDDI and other technologies and/or
standards where a widely adopted practice would benefit the Web services
community.
A Proposal is optional, but gives one the opportunity to present the idea for
the submission to the UDDI Spec TC without the need for investing the work
necessary to prepare a completed work. A proposal may take the form of a simple
abstract submitted to the TC mailing list, or may even be proposed as a topic of
discussion at a TC meeting. The individual making the proposal can then gauge
the support present in the TC for developing the work before proceeding to the
next stage.
Individuals intending to submit proposals should use the technical note template
available at the following location
http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-tn-template.doc.
Submission
To be considered by the TC, the technical note submission must be based on a
Committee Specification or OASIS Standard version of the UDDI specification. A
technical note based on a future release of the UDDI specification may be
created, but it will not be published until that version of the UDDI
specification is released.
OASIS IP rules and procedures apply for any submissions.
Technical notes must use the format of the documents available at the following
location
http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-tn-template.doc.
|
