Approving a Committee Specification or Committee Note
After a Committee Specification Draft or a Committee Note Draft has been through a public review that did not result in comments or, if comments were received, that did not result in any material changes to the draft, the TC can vote to approve the draft as a Commitee Specification or a Committee Note. For Committee Specifications, this is a Special Majority Vote, set up and run for the TC by TC Administration. A TC may approve a Committee Note by a Full Majority Vote rather than a Special Majority Vote. A Committee Specification is the first stage for an OASIS Standards Final Deliverable
You may also request that references to other OASIS Committeee Specifications or Committee Notes in the Normative and Non-Normative reference section of the draft be updated during the publication of the
Committee Specification or Committee Note. See Requesting Cross-Reference Changes for instructions.
You may also approve a Committee Specification or Committee Note that includes changes made since the last public review if the TC judges those changes to be Non-Material. See Approving a Committee Specification or Committee Note with Non-Material Changes for instructions.
As documented in the OASIS Naming Directives, a Committee Specification or Committee Note is identified on the front page of the document with the name of the stage and a revision number and its approval date. (The date is the date that the approval ballot or vote closed.) For example:
WS-Calendar Version 1.0
Committee Specification 01
30 July 2011
Transformational Government Framework Primer
Committee Note 01
11 January 2012
Likewise, the filename will include the stage abbreviation and revision number to uniquely identify the draft. For example:
Steps to approve a Committee Specification or Committee Note
The first step in approving a draft as a Committee Specification (or optionally a Committee Note) is to approve a Resolution requesting TC Administration hold the Special Majority Vote. The Resolution can be passed by a Simple Majority Vote. To
vote on the Resolution, follow these steps:
- Make the motion or start a ballot to request the Special Majority Vote. Include the title, version number and stage name and number in the language and include the link to the Committee Draft that went through the last public review. If approving a subsequent Working Draft with Non-Material Changes, include a link to a ZIP file with all the component files that together will make up the approved Draft.
- Make a motion or start a ballot to requesting the Special Majority Vote. You can use the template below to cut and paste suitable language.
- After the motion or ballot has passed, enter a TC Admin support request ticket, either the Committee Specification Ballot Request or the Committee Note Ballot Request. You will need to include the link to the meeting minutes that record the approval or to the ballot and you will need to include the same link as was in the motion or ballot.
After you enter the ticket, TC Admin will prepare the Special Majority Vote and announce it to the TC, including the number of yea votes necessary for it to pass. The ballot will remain open for 7 days. If the ballot passes, TC Administration will publish the Committee Specification or Committee Note and announce it to the OASIS membership.
Template for motion or ballot language
The motion or ballot language used to request the Special Majority Vote must include the identification information for the draft being approved. Language such as the following will meet the requirement:
[I move that the TC / Do you] approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve [Committee Draft title and version number] contained in [URL to the Committee Draft] as a Committee [Specification | Note].
Multiple drafts can be approved for Special Majority Votes in a single Resolution. Simply ensure that each is clearly identified.
Note that a Committee Specification Draft cannot be approved as a Committee Note or vice versa. To switch a document between a Non-Standards Track and Standards Track, it must be restarted through the OASIS Process as a draft of the appropriate type.