Before a Committee Specification or Committee Note Draft can be approved as a Committee Specification or a Committee Note, you must first conduct one or more public reviews of the Draft (TC Process section 3.2, Public Review of a Committee Draft). A public review provides other OASIS members and interested parties outside of OASIS with an opportunity to provide feedback on the Draft to the members of the Technical Committee.

Public review comments from members of the TC must be sent directly to the TC's mailing list. If TC Administration has any public review comments, they will likewise be sent to the TC mailing list. All other comments must be sent to the TC's comment mailing list. Comments received by any other channel may not be accepted by the TC. TC members must avoid forwarding or otherwise copying comments from other parties to the TC mailing list or comment list to avoid any possible IP conflicts or confusion.

The first public review for a committee draft must be for a minimum of 30 days. Subsequent reviews must be for a minimum of 15 days. The TC may request longer review periods.

Prerequisites for a public review 

In order to start a public review, the TC must have:

  • A Committee Specification Draft or Committee Note Draft created using the starter template provided by TC Administration, and;
  • The Draft and all other component files that together make up the Specification or Note must be packaged in a ZIP file and loaded to the TC's document repository in Kavi.

Work on the Draft must be complete and any changes tracked under change control during editing accepted and removed from the document. No changes can be made to the Draft after the TC approves it for public review and the Draft may not be approved for public review contingent on editorial changes or other corrections being made. The Draft itself must conform to the following requirements identified in TC Process section 2.18, Work Product Quality:

  • Filenames must meet the requirements of the OASIS Naming Directives including a Working Draft number (e.g. WD03) that applies to the entire Specification or Note; 

  • If the work contains references, then a References section must be included and must identify references as Normative or Non-Normative;

  • If the work contains normative computer language content, such as a copy of a schema, then the content must also be included as a separate plain text file and the file must be referenced from the Draft;

  • An Acknowledgements section must be included listing all the people who participated in the development of the Draft (generally included as Appendix A); 

  • For Committee Specification Drafts, a Conformance Clauses section must be included listing numbered conformance clauses to which an implementation of the specification must adhere;

  • The Draft must contain the OASIS copyright and must be labelled as a Standards-track or Non-Standards track document on every page.

Steps for initiating a public review 

When you are ready to start a public review, follow these steps:

  1. Vote to approve releasing the Draft for public review. You can make and approve the vote to release the Draft for public review at the same time that you vote to approve the Working Draft as a Committee Specification or Note Draft as explained in Approving a Committee Specification or Note Draft.

    1. You can either approve the public review by making and passing a motion in a meeting or by starting and voting on a ballot by email or by the OASIS TC ballot facility in Kavi.

    2. If the approval is by motion in a meeting, include the text of the motion and the results of the vote in your meeting minutes.

    3. For either method, include the name and working draft number and the link to the ZIP file in Kavi in your text. For example:

      Do members of the TAG TC approve releasing Test Assertions Model Version 1.0 WD03 (contained in for 15-day
      public review?

      Including the ZIP file URI as well as the title and Working Draft number allows OASIS to connect the dots between the Draft the TC approves and the Draft TC Administration releases for public review.

  2. Submit the Draft to TC Administration by completing the proper Public Review Request ticket on the TC Administration Requests page. You will need the link to the ZIP file in Kavi and the link to the meeting minutes or ballot where the approval was documented for the ticket. You must submit your request using the forms on the requests page. TC Administration will not act on requests sent by email. 

  3. In addition to the Draft, please submit a list of interested external parties who should be notifed of the public review. TCs that publicize their public reviews to a targeted audience generally get more and better feedback on their work.

Template for motion or ballot language

The motion or ballot language used to approve the Draft for public review must include the name of the Committee Draft being approved and the link to the ZIP file in the TC's document repository. Language such as the following satisfies this requirement.

[I move that the TC / Do you ] approve submitting [Committee Draft title, version number and revision number]and all associated artifacts contained in [URL to the ZIP file on the TC document repository OR URL to the CSD on ] for [number of days] public review.

What happens next

Once you have submitted your request, TC Administration takes the following steps:

  • Review the approval and the submitted documents to ensure that they comply with all OASIS requirements;
  • Create the official OASIS Committee Specification or Note Public Review Drafts by copying the body of the document into the appropriate cover pages and adding all necessary metadata such as Chairs, Editors, Associated artifacts, etc.
  • Make any needed modifications to associated artifacts such as adding the OASIS copyright to schemas and WSDLS
  • Create an OASIS Namespace document for the Draft if needed
  • Load the Draft and related artifacts to the TC's folders on the OASIS Library (
  • Add an entry to the TC's Approved Work Product folder in Kavi
  • Announce the public review to OASIS members and the public. If the TC has provided a list of emails for external stakeholders and interested parties, those contacts will be bcc'ed on the OASIS announcements to avoid any risk of their being spammed with unwanted email traffic.


The TC may continue developing their Working Draft while the public review is underway.

The TC must maintain a log of all comments received and their disposition. This is covered in the next section.