OASIS recognizes three general classes of documents that can be produced by a Technical Committee:

  1. Administrative documents
  2. StandardsTrack Work Products
  3. Non-Standards Track Work Products

Administrative documents are those that support internal operations of the TC such as minutes, agendas, etc. A TC is generally free to create and manage these documents using whatever tools and methods they choose. Only a few requirements apply to them:

Standards Track Work Products are documents and associated files such as schemas, WSDLs or examples, that are intended to become formal OASIS Committee Specifications and OASIS Standards. The specific stages in the development of a Standards Track Work Product are:

In addition, once a specification has become an OASIS Standard, the TC may produce Approved Errata to make non-substantive corrections to the content.

Non-Standards Track Work Products are documents such as white papers, how-to guides, or promotional sheets that support the promotion and adoption of the specification and the work of the TC. They are by definition non-normative and not subject to the requirements of the OASIS IPR Policy.

A Non-Standards Track Working Draft can be approved as a Committee Note by the TC at any time. Approval requires a Full Majority Vote. A TC always has the option to submit Committee Note Drafts for public review before approving them as Committee Notes. If they choose to do so, the same procedures and approvals apply to them as apply to Standards Track Work Products save that the Committee Note does not need to go through a Special Majority Vote for approval.

The specific stages in the development of a Non-Standards Track Work Product are:

The following sections explain how to create, manage and advance your TC work products through these stages.