" rel="home"><?php print " id="logo-image" />
" rel="home">

" rel="home">

'main-menu', 'class' => 'links clearfix')); ?>

To UDDI Spec TC page
 
 OASIS UDDI Specifications TC - Change Requests

The Change Request Process is described below.

 

Specification Change Requests

UDDI V2 Related Change Requests

There are no UDDI v2 Change Requests at this time.

UDDI V3 Related Change Requests

There is an ongoing review, discussion and approval of the UDDI V3 Committee Specification. The TC tracks CRs in the "status.htm" document of the http://www.oasis-open.org/committees/documents.php?wg_abbrev=uddi-spec document folder.

Process

 

From time to time, errors, inconsistencies or ambiguities will be discovered in an OASIS UDDI TC Specification or OASIS UDDI Specification Standard based upon ongoing experience with the specification by those implementing it. Such feedback is essential to improving the quality of these documents.

The specification change request and errata process is intended to address defects found in a specification. It may NOT be used to add new functionality or substantively change existing functionality except as minimally required to effect a fix.

When an error is discovered in one of the UDDI specifications or related documents, the issue must be documented using a standard change request template and submitted to the OASIS UDDI TC. If the submitter is a member of the UDDI Specification TC, then this submission should be made to the uddi-spec mailing list. If not, then it should be submitted via the "Send a comment" link at http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=uddi-spec. An evaluation of the item by the TC will be provided back to the list where the submission is performed.

The Change Request (CR) form submitted will be used as input to the Editor(s) of affected documents to make any needed corrections. Note that point versions of updated specification documents may be provided in such a way as to group multiple CRs into a single document update and version.

 

Specification Change Request Process

Upon submission of a CR, the TC Chairs will assign it a tracking number and the CR will be assigned to an Editor(s) for consideration as errata. This information will be tracked by the TC Chairs. The Editor(s) of the affected document takes responsibility for the change and adds it to a list of candidate erratum for making up an errata package. In the course of preparing the revised text, further dialog and a number of drafts may be required between editors and the TC. This business will be carried out on the TC’s uddi-spec mailing list. Once the TC agrees to produce an erratum for the item, this information is communicated back via the "Send a comment" link if the person who submitted it was not a member of the TC.

 

The Specification Change Request template located at http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-cr-template.doc will be used to make submissions.

 

Upon submission and agreement by the TC that the error is indeed valid and should be corrected, the completed form is provided to the Editor(s) of the appropriate specifications for consideration. If the Editor(s) determine that further work is required to integrate the proposed correction, they inform the TC and the Chair will call for a subcommittee to develop a workable solution. Otherwise, the editors will include the work as errata using the Specification Errata Process described in the following section.

Specification Errata Process

The process for integrating a set of errata into a specification is as follows:

  • In consultation with the TC Chairs, once the Editor(s) determine they have integrated a sufficient number of erratum to justify the release of an errata document / or revised spec is released to the TC for review.

  • The errata is posted together with a marked up version of the specification document for a 15 day review period by the TC members, during which time no changes should be made to either the errata or the marked up document. These will be posted on the uddi-spec. Note that an errata set will be tied to an update of the version numbers associated with each of the specifications which make up the version of UDDI being amended. All version numbers of all such documents will be updated to a matching level for such releases of errata sets.

  • Any revision necessary as a result of feedback should be made and resubmitted for review; an additional 15 day review period should be allowed but may be waived depending on the nature of the changes.

  • At the end of the review period, the TC Chairs will submit the errata and amended specification document for vote. Voting rules for this vote are the same as for approval of a TC Committee Specification, as documented in the OASIS TC Process.

  • Approved errata documents and the corresponding updated specifications will be posted on the TC’s web site.

 

TOP OF PAGE

Gear Image