|
The current UDDI Spec TC
Best Practices Process is described below.
Documents
Using
WSDL in a UDDI Registry, Version 1.08.
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 describe how WSDL can be used to help create UDDI
business service descriptions.
This Best Practice is supplemented by the
Using WSDL in a UDDI Registry, Version 2.0 Technical Note providing an
expanded modeling practice that encompasses the flexibility of WSDL. The
primary difference between the Version 2.0 Technical Note mapping and the
one described by this Best Practice is that the TN mapping provides a
methodology to represent individual Web services artifacts.
The
Using WSDL in a UDDI Registry, Version 2.0 Technical Note does not
replace the Version 1 Best Practice. If the additional flexibility is not
required, the existing Best Practice can still be used, particularly when
the UDDI artifacts are published manually.
HTML /
PDF
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 best practice 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 best practice template
available at the following location
http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-bp-template.doc.
Submission
To be considered by the TC, the best practice submission must be based on a
Committee Specification or OASIS Standard version of the UDDI specification. A
best practice 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.
Best practices 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-bp-template.doc.
|
