OASIS Motion & Ballot Language Template    
Version 1.0 
Published 05 August 2014
Num Task Motion Template Ballot Template Example Required elements Common Mistakes Notes
Approve Committee Specification Documents          
1) Approve a Working Draft as a Committee Specification Draft I move that the TC approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as a Committee Specification Draft and designate  the <format> version of the specification as authoritative. - Ballot title: Approve <Working Draft title and version number> as a CSD
- Ballot question: Do you approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as a Committee Specification Draft and designate the <format> version of the specification as authoritative?
- Description: <any additional information you wish to add.>

I move that the OASIS Energy Interoperation TC issue OASIS Energy Interoperation Transport Protocol Bindings for OASIS Energy Interoperation 1.0 Version 1.0 Working Draft 03 and its associated XML artifacts packaged together in the Energy Interoperation archive at http://www.oasis-open.org/committees/document.php?document_id=45683&wg_abbrev=energyinterop as Energy Interoperation Transport Bindings 1.0 Committee Specification Draft and further direct the Chairs to perform any actions required by the TC Administrator to accomplish that issuance as soon as practicable. We further direct that the PDF version of the specification is authoritative. - The title of the working draft and its version number;
- A URL to the ZIP file containing all the component parts of the specification
- Not combining all components of the spec in the ZIP file and loading them to Kavi;
- Not including the URL to the ZIP file in the motion;
- Approving the draft contingent upon editors making additional changes.
- Submitting a URL to TC Admin that is different from the URL approved in the motion or ballot.
- Passing requires a Full Majority Vote of the TC
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
2) Approve a Committee Specification Draft for Public Review I move that the TC approve submitting <Working Draft OR Committee Specification Draft title, version number and revision number> contained in <URL to CSD on docs.oasis-open.org OR ZIP file in TC's Kavi document repository> for <number of days> public review. - Ballot title: Approve submitting <Working Draft title and version number> for public review
- Ballot question: Do you approve submitting <Working Draft OR Committee Specification Draft title, version number and revision number> contained in <URL to CSD on docs.oasis-open.org OR ZIP file in TC's Kavi document repository> for <number of days> public review?
- Description: <any additional information you wish to add.>
Do the members approve submitting OASIS WS-Calendar 1.0 Committee Specification Draft 04 contained in http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csd04/ for a fifteen-day Public Review? - The title of the Committee Specification Draft and its version number;
- If the CSD already exists, its URL otherwise a URL to the ZIP file containing all the component parts of the specification
- Not including a URL to the CSD or the Work Product - Passing requires a Full Majority Vote of the TC
- For a first public review, the minimum period is 30 days. For a subsequent public review, the minimum period is 15 days. The TC is free to specify a longer period.
 - A Committee Specification Draft must be approved before the TC can vote to approve it for public review.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
3) Request a Special Majority Vote to approve a Committee Specification Draft as a Committee Specification I move to approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve <Committee Specification Draft title and version number> contained in <URL to Committee Specification Draft> as a Committee Specification. - Ballot title: Approve requesting Special Majority Vote on <Committee Spec Draft title and version number>
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve <Committee Specification Draft title and version number> contained in <URL to Committee Specification Draft> as a Committee Specification?
- Description: <any additional information you wish to add.> 
I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve CAMP Version 1.1 CSD03 contained in https://docs.oasis-open.org/camp/camp-spec/v1.1/csd03 as a Committee Specification. - The title of the Committee Specification Draft and its version number.
- A URL to the Committee Specification Draft. 
- Voting in the TC to directly approve the Committee Specification rather than to approve requesting that the Special Majority Vote be set up.  - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- A Committee Spec Draft must have been through at least one public review before it can be approved as a Committee Specification.
- A vote to approve a Committee Specification requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
4) Request a Special Majority Vote to approve a Committee Specification Draft with Non-Material Changes as a Committee Specification I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve  <Working Draft title, version number and working draft number> contained in <URL for the revised draft in Kavi> as a Committee Specification. I further move that the TC affirm that changes have been made since the last public review, that the changes made are documented in <URL for the summary of changes> and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange). - Ballot title: Approve requesting Special Majority Vote on <Committee Spec Draft title and version number>
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Vote to approve  <Working Draft title, version number and working draft number> contained in <URL for the revised draft in Kavi> as a Committee Specification, affirming that changes have been made since the last public review, that the changes made are documented in <URL for the summary of changes> and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange)?
- Description: <any additional information you wish to add.> 
I move that the Chair request TC Administration hold a Special Majority Vote to approve Topology and Orchestration Specification for Cloud Applications V1.0 Working Draft 06 contained in https://www.oasis-open.org/committees/document.php?document_id=48397 as a Committee Specification. The TC affirms that changes have been made since the last public review. The changes made are documented in https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/48475. The TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange). - The title, version number and stage of the Committee Specification Draft.
- A URL to a ZIP file loaded in the TC's document repository containing all the component parts of the revised Working Draft.
- A link to the record of changes made to the Working Draft since the last public review in the TC's document repository.
- A statement that the TC judges the changes to be Non-Material in keeping with the definition of the term in the TC Process. 
- Not making a log of the changes made since the last public review.
- Not including the URL of the log of changes.
- Not including the assertion that the TC judges the changes to be Non-Material. 
- Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- A Committee Spec Draft must have been through at least one public review before it can be approved as a Committee Specification.
- If a TC wishes to make changes to a Committee Specification Draft after its last public reivew, a log of the changes made must be kept, loaded into the TCs Kavi document repository and made available in the motion. The log of changes can be in the form of a red-lined file displaying the differences between the last publicly reviewed version of the specification and the revised version.
- A vote to approve a Committee Specification requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (b) the vote tally. 
5) Request a Special Majority Vote to approve a Committee Specification Draft as a Committee Specification and update cross-references  I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve <Committee Specification Draft title and version number> contained in <URL to Committee Specification Draft> as a Committee Specification, and to approve the Chair requesting that TC Administration update the following Designated Cross-References during publication of the Committee Specification:

- Current reference to be updated: <text of OASIS work product cross-reference to be updated?  Expected approval status and date: <expected approval stage>, <expected month/year of approval>

- <repeat references as needed>

The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.
- Ballot title: Approve requesting Special Majority Vote on <Committee Spec Draft title and version number>
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Vote to approve <Committee Specification Draft title and version number> contained in <URL to Committee Specification Draft> as a Committee Specification, and to approve the Chair requesting that TC Administration update the following Designated Cross-References during publication of the Committee Specification? 

- Current reference to be updated: <text of OASIS work product cross-reference to be updated?  Expected approval status and date: <expected approval stage>, <expected month/year of approval>

- <repeat references as needed>

- Description: <any additional information you wish to add.>
Do the members approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve Service Component Architecture Web Service Binding Specification Version 1.1 contained in http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-spec.html as a Committee Specification. Do the members also approve requesting TC Administration update the following Designated Cross-References during publication of the Committee Specification:

- Current reference to be updated: [SCA-Assembly]  OASIS Committee Specification Draft 07, Service Component Architecture Assembly Model Specification Version 1.1, January 2011. http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-spec-csd07.pdf
  Expected approval status and date: Committee Specification, May, 2013

The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes. 
- The title, version number and stage of the Committee Specification Draft.
- A URL to the Committee Specification Draft.
- One or more citations from the draft's References section along with the status they are expected to reach and approximate timeframe.
- A statement that the TC acknowledges that publication of the final CS may be delayed while the cross-referenced documents are updated. 
- Not copying citations from the body of Committee Specification Draft making it unclear what cross-reference is to be updated.
- Requesting changes to references in sections of the draft other than the References section or in documents other than the specification draft.  
- Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- A Committee Spec Draft must have been through at least one public review before it can be approved as a Committee Specification.
- A vote to approve a Committee Specification requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
Approve OASIS Standard Documents            
6) Request a Special Majority Vote to approve submitting a Committee Specification as a Candidate OASIS Standard. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting <Committee Specification title and version number> Committee Specification ## at <URL to Committee Specification> as a Candidate OASIS Standard.  - Ballot title: Approve requesting Special Majority Vote on <Committee Specification title and version number>
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting <Committee Specification title and version number> Committee Specification ## at <URL to Committee Specification> as a Candidate OASIS Standard?
- Description: <any additional information you wish to add.> 
I move that the OASIS Energy Interoperation TC submit OASIS Energy Interoperation 1.0 CS02 at http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/energyinterop-v1.0-cs02.html as a Candidate OASIS Standard and direct the Chairs to take any necessary steps to carry out that submission pursuant to the OASIS TC Process 3.4.1, with a public review not exceeding the process requirements (presently 60 days). - The title, version number and Committee Specification number.
- Voting to directly approve the move to Candidate OASIS Standard rather than voting to request a Special Majority Vote.  - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The Committee Specification must have its 3 or more Statements of Use received and approved by the TC before starting the process to advance it as a Candidate OASIS Standard.
- A vote to approve a Candidate OASIS Standard requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
7) After a COS public review, request a Special Majority Vote to approve continuing to submit a Candidate OASIS Standard for a membership vote If comments were received but no changes were made. I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve continuing with an OASIS Standard ballot for <COS title and version number> Candidate OASIS Standard ##. - Ballot title: Approve requesting Special Majority Vote to continue with OASIS Standard
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Vote to approve continuing with an OASIS Standard ballot for <COS title and version number> Candidate OASIS Standard ##?
- Description: <any additional information you wish to add.> 
Do the members approve the Chair requesting that TC Administration hold a Special Majority Vote to approve continuing with an OASIS Standard ballot for Test Assertions Model Version 1.0 Candidate OASIS Standard 01?

- The title, version number and Candidate OASIS Standard number - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- A vote to approve continuing to present a Candidate OASIS Standard to the membership for a vote requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
8) After a COS public review, request a Special Majority Vote to approve a new Candidate OASIS Standard with Non-Material Changes and submit it to OASIS members for a membership vote if comments were received and only Non-Material Changes were made.  I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve <working draft ##> of <COS title and version #> and all related artifacts contained in <URL to the working draft> as Candidate OASIS Standard 02 and present this Candidate OASIS Standard to the membership for an OASIS Standard vote in accordance with the procedures documented in 3.4.2, “Public Review of a Candidate OASIS Standard” in the OASIS TC Process. By passing this motion, the TC affirms that (a) Working Draft ## contains changes from Candidate OASIS Standard 01; (b) that the changes made are documented in <URL to the comment resolution log>; (c) that these changes are Non-Material; and (d) that these changes are made ONLY to address the comments received during the public review period.  - Ballot title: Approve requesting Special Majority Vote to approve revised COS 02
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Vote to approve a new <COS title and version #> COS02 and submit it to the OASIS members for a vote?
- Description: By passing this motion, the TC affirms that (a) Working Draft ## contains changes from Candidate OASIS Standard 01; (b) that the changes made are documented in <URL to the comment resolution log>; (c) that these changes are Non-Material; and (d) that these changes are made ONLY to address the comments received during the public review period. <any additional information you wish to add.> 
I move that the TC instruct the Officers to request that OASIS TC Admin hold a Special Majority Vote to approve Working Draft 05 of XLIFF Version 2.0 and all related artifacts contained in http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/xliff-20.zip?op=dl&rev=536&isdir=0 as Candidate OASIS Standard 02 and present this Candidate OASIS Standard to the membership for an OASIS Standard vote in accordance with the procedures
documented in 3.4.2 Public Review of a Candidate OASIS Standard in the OASIS TC Process. By passing this motion, the TC affirms that (a) Working Draft 05 contains changes from Candidate OASIS Standard 01 (http://docs.oasis-open.org/xliff/xliff-core/v2.0/cos01/xliff-core-v2.0-cos01.html); (b) that the changes made are documented in https://wiki.oasis-open.org/xliff/XLIFF%202.0%20Public%20Review%20submitted%20comments%20tracker; (c) that these changes are Non-Material; and (d) that these changes are made ONLY to address the comments received during the public review period as documented in https://wiki.oasis-open.org/xliff/XLIFF%202.0%20Public%20Review%20submitted%20comments%20tracker.
- The title, version number and working draft number for the revised COS and the URL to the working draft.
- The affirmation that the working draft contains changes, the URL to the comment resolution log, that the TC judges the changes Non-Material, and that the changes were made only to address the comment received.
- The comment resolution log
- Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
9) After an OASIS Standard membership vote, if negative votes were received but the ballot did not fail, request a Special Majority Vote to request TC Administration approve the COS as OS.  I move to acknowledge negative votes received during the vote for OASIS Standard, reaffirm the TC's support for <Candidate OASIS Standard title and version #> Candidate OASIS Standard ## and to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve the COS as submitted as an OASIS Standard.  - Ballot title: Approve requesting Special Majority Vote to continue with OASIS Standard
- Ballot question: Do the members acknowledge negative votes received during the vote for OASIS Standard, reaffirm the TC's support for <Candidate OASIS Standard title and version #> Candidate OASIS Standard ## and approve the Chair requesting that TC Administration hold a Special Majority Vote to approve the COS as submitted as an OASIS Standard?
- Description: <any additional information you wish to add.> 
I move that the TGF TC note the result of the recent ballot to approve the “TGF Pattern Language – Core Patterns” as an OASIS Standard and the existence of negative votes in that ballot, reaffirm its support for the Candidate OASIS Standard and instruct the chair  request a Special Majority Vote to request that TC Administration approve the Candidate OASIS Standard as OASIS Standard.

“The TGF TC notes the result of the recent ballot to approve the “TGF Pattern Language – Core Patterns” as an OASIS Standard and the existence of negative votes in that ballot. In line with the TC Process, the TGF TC reaffirms its support for the Candidate OASIS Standard and instructs the chair to request the TC Administrator to conduct the necessary Special Majority vote required to formally reaffirm this support."

- The title, version number and Candidate OASIS Standard number.
- TC acknowledgement of negative votes cast.
- Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The vote to request TC Admin approve an OASIS Standard despite negative votes case requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
10) After an OASIS Standard membership vote, if negative votes were received but the ballot did not fail, request a Special Majority Vote to request TC Administration withdraw the submission. I move to acknowledge negative votes received during the vote for OASIS Standard and to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve withdrawing <Candidate OASIS Standard title and version #> Candidate OASIS Standard ## from further consideration at this time.   - Ballot title: Approve requesting Special Majority Vote to withdraw Candidate OASIS Standard
- Ballot question: Do the members acknowledge negative votes received during the vote for OASIS Standard and approve the Chair requesting that TC Administration hold a Special Majority Vote to approve withdrawing <Candidate OASIS Standard title and version #> Candidate OASIS Standard ## from further consideration at this time? 
- Description: <any additional information you wish to add.> 
Do the members acknowledge negative votes received during the vote for OASIS Standard and approve the Chair requesting that TC Administration hold a Special Majority Vote to approve withdrawing SomeSpec Version 1.0 Candidate OASIS Standard 01 from future consideration at this time.  - The title, version number and Candidate OASIS Standard number.  - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The vote to request TC Admin withdraw the submission requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
11) After an OASIS Standard membership vote, if negative votes were received but the ballot did not fail, request a Special Majority Vote to request TC Administration accept an amended specification. I move that the members acknowledge negative votes received during the vote for OASIS Standard and approve the Chair requesting a Special Majority Vote to request TC Administration accept an amended submission  of <Candidate OASIS Standard title and version #> as a Candidate OASIS Standard. 
- Ballot title: Approve requesting Special Majority Vote to amend Candidate OASIS Standard
- Ballot question: Do the members acknowledge negative votes received during the vote for OASIS Standard and approve the Chair requesting a Special Majority Vote to request TC Administration accept an amended submission  of <Candidate OASIS Standard title and version #> as a Candidate OASIS Standard?
- Description: <any additional information you wish to add.> 
I move that the members acknowledge negative votes received during the vote for OASIS Standard and approve the Chair requesting a Special Majority Vote to request TC Administration accept an amended submission  of SomeSpec Version 1.0 as a Candidate OASIS Standard. The TC intends to present the amended submission on or about the last week of July, 2013.
- The title, version number and Candidate OASIS Standard number.
- An approximate timeframe for submitting the amended submission.
- Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The vote to request TC Admin accept an amended submission requries a Special Majority Vote run by TC Administration.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
Approve Errata Documents            
12) Approve a working draft as an Errata Draft and confirm that the corrections do not constitute Substantive Changes. I move that the TC approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as an Errata Draft to <title, version number> OASIS Standard approved on <date> and confirm that the errata corrections do not constitute Substantive Changes to the Standard. - Ballot title: Approve <Working Draft title, version number> as an Errata CSD
- Ballot question: Do you approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as an Errata Draft to <title, version number> OASIS Standard approved on <date> and confirm that the errata corrections do not constitute Substantive Changes to the Standard?
- Description: <any additional information you wish to add.> 
Does the ODF TC approve ODF 1.1 Errata 01 WD08 contained in https://www.oasis-open.org/committees/document.php?document_id=49151 and ODF 1.1 with Errata 01 Changes Applied contained in https://www.oasis-open.org/committees/document.php?document_id=49143 as an Errata Draft to the Open Document Format for Office Applications (OpenDocument) v1.1 OASIS Standard approved on 01 February 2007 AND does the TC confirm that the proposed corrections do not constitute a Substantive Change?
- The title of the working draft(s) and its version number;
- A URL to the ZIP file(s) containing all the component parts of the errata draft
- The title, version number and approval date of the OASIS Standard to which the errata applies.
- Confirmation that the changes are not Substantive.
- Fail to include the statement that the changes are not Substantive.
- Submitting a URL to TC Admin that is different from the URL approved in the motion or ballot.
- Passing requires a Full Majority Vote of the TC
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally. 
13) Approve an Errata Draft for Public Review. I move that the TC approve submitting <errata title, version number and revision number> contained in <URL to ZIP file in TC's Kavi document repository> for 15 day public review. - Ballot title: Approve submitting <Working Draft title, version number> for public review
- Ballot question: Do you approve submitting< Working Draft title, version number and revision number> contained in <URL to ZIP file in TC's Kavi document repository> for 15 day public review?
- Description: <any additional information you wish to add.> 
AND does the ODF TC further approve submitting ODF 1.1 Errata 01 and ODF 1.1 with Errata 01 Changes Applied for 15 day public review?  - The title of the working draft(s) and its version number;
- A URL to the ZIP file(s) containing all the component parts of the errata draft if not already supplied in the preceding motion.
- Passing requires a Full Majority Vote of the TC
- Public review for an Errata Draft is 15 days as specified in the TC Process.
 - A Committee Specification Draft must be approved before the TC can vote to approve it for public review.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
14) Approve an Errata Draft as an Approved Errata. I move that the TC approve <errata title, version number and revision number> contained in <url to the publicly reviewed Errata Draft document> as an Approved Errata and make it available with <title and version number> OASIS Standard.  - Ballot title: Approve <Working Draft title, version number> as Approved Errata
- Ballot question: Do you <Working Draft title, version number and revision number> contained in <url to the publicly reviewed Errata Draft document> as an Approved Errata and make it available with <title and version number> OASIS Standard?
- Description: <any additional information you wish to add.> 
Does the ODF TC approve ODF 1.1 Errata 01 Committee Specification Draft 01 contained in http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-csprd01.html and ODF 1.1 with Errata 01 Changes Applied contained in http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-csprd01-complete.html as an Approved Errata and make it available with Open Document Format for Office Applications (OpenDocument) v1.1 OASIS Standard? - The title of the Errata, its version number and Committee Specification number;
- A URL to the publicly reviewed Errata Draft.
- Passing requires a Full Majority Vote of the TC
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
Approve Committee Note Documents            
15) Approve a Working Draft as a Committee Note.  I move to approve <Working Draft title and version number> and all associated artifacts packaged together at <URL to ZIP file in TC's Kavi document repository> as a Committee Note and designate the <format> version of the note as authoritative.  - Ballot title: Approve <Working Draft title, version number> as Committee Note
- Ballot question: Do you approve <Working Draft title and version number> and all associated artifacts packaged together at <URL to ZIP file in TC's Kavi document repository> as a Committee Note and designate the <format> version of the note as authoritative?
- Description: <any additional information you wish to add.>
I move to approve "Using XLIFF to Translate DITA Articles" Version 1.0 packaged in https://www.oasis-open.org/committees/download.php/48340/ as a Committee Note and designate the PDF version as authoritative.  - The title of the working draft and its version number;
- A URL to the ZIP file containing all the component parts of the draft.
- Not including a URL to the Working Draft.
- Submitting a URL to TC Admin that is different from the URL approved in the motion or ballot.
- Passing requires a Full Majority Vote of the TC
- A TC can vote to approve a working draft directly as a Committee Note without having to go through a public review draft stage.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
16) Approve a Working Draft as a Committee Note Draft.  I move that the TC approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as a Committee Note Draft and designate  the <format> version of the note as authoritative? - Ballot title: Approve <Working Draft title, version number> as Committee Note Draft
- Ballot question: Do you approve approve <Working Draft title, version number and revision number> and all associated artifacts packaged together in <URL to ZIP file in TC's Kavi document repository> as a Committee Note Draft and designate  the <format> version of the note as authoritative?
- Description: <any additional information you wish to add.>  
Do the members approve "EMIX 1.0 and the OASIS Smart Grid Suite of Standards Version 1.0" working draft 02 contained in https://www.oasis-open.org/apps/org/workgroup/emix/download.php/43891/emix-oasis-v1%200-wd02.zip as a Committee Note Draft and designate the PDF version as authoritative?  - The title of the working draft and its version number;
- A URL to the ZIP file containing all the component parts of the draft.
- Not including a URL to the Working Draft.
- Submitting a URL to TC Admin that is different from the URL approved in the motion or ballot.
- Passing requires a Full Majority Vote of the TC
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
17) Approve a Committee Note Draft for Public Review I move that the TC approve submitting <Working Draft OR Committee Note Draft title, version number and revision number> contained in <URL to CND on docs.oasis-open.org OR ZIP file in TC's Kavi document repository> for <number of days> public review. - Ballot title: Approve submitting <Working Draft title, version number> for public review
- Ballot question: Do you approve submitting <Working Draft OR Committee Note Draft title, version number and revision number> contained in <URL to CND on docs.oasis-open.org OR ZIP file in TC's Kavi document repository> for <number of days> public review?
- Description: <any additional information you wish to add.>  
Do the members further approve submitting "EMIX 1.0 and the OASIS Smart Grid Suite of Standards Version 1.0" working draft 02 contained in https://www.oasis-open.org/apps/org/workgroup/emix/download.php/43891/emix-oasis-v1%200-wd02.zip for 30-day public review? - The title of the Committee Note Draft and its version number;
- If the CND already exists, its URL otherwise a URL to the ZIP file containing all the component parts of the note.
- Not including a URL to the CND or the Work Product - Passing requires a Full Majority Vote of the TC
- For a first public review, the minimum period is 30 days. For a subsequent public review, the minimum period is 15 days. The TC is free to specify a longer period.
 - A Committee Note Draft must be approved before the TC can vote to approve it for public review.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
Miscellaneous motions            
18) Approve Statements of Use submitted to the TC  I move to accept the Statements of Use for <Committee Specification title and version #> approved on <date> provided by <list of SoU providers and links to SoU emails>.   - Ballot title: Accept Statements of Use
- Ballot question: Do you approve accepting the Statements of Use for <Committee Specification title and version #> approved on <date> provided by <list of SoU providers and links to SoU emails>?
- Description: <any additional information you wish to add.>  
Do the TC members approve and accept the Statements of Use received and posted to the TC mailing list on behalf of Huawei on May 14th (https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201305/msg00026.html), Axway on May 17th (https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201305/msg00041.html) and IBM on May 17th (https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201305/msg00040.html) as acceptable Statements of Use with respect to the TOSCA Committee Specification 02, which was approved on May 10, 2013.

Motion was seconded by Gerd Breiter and accepted with unanimous consent.
- The title of the Committee Specification, its version number and approval date;
- The name of each entity providing the Statement of Use;
- A link to each email submitting a Statement of Use. 
- Not fully specifying the Committee Specification so that it isn't clear which CS the Statements go with;
- Not including links to the Statements of Use. 
- Passing requires a Simple Majority Vote of the TC
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
19) Request a Special Majority Vote to approve a charter clarification I move to approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve the charter clarification contained in <URL to charter clarification document>.  - Ballot title: Request Special Majority Vote for charter clarification
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve the charter clarification contained in <URL to charter clarification document>?
- Description: <any additional information you wish to add.>  
Do the TC members approve the Chair requesting the TC Administration hold a Special Majority Ballot to approve the charter clarification contained in http://www.oasis-open.org/apps/org/workgroup/bias/download.php/49466? - A link to the document containing the clarified charter.  - Not including the link to the document containing the clarified charter. - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The charter clarification should contain a red-line of the differences between the current charter and the clarified charter.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
20) Request a Special Majority Vote to approve a charter revision I move to approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve the revised charter contained in <URL to charter revision document>.  - Ballot title: Request Special Majority Vote for charter revision
- Ballot question: Do you approve the Chair requesting that TC Administration hold a Special Majority Ballot to approve the revised charter contained in <URL to charter revision document>?
- Description: <any additional information you wish to add.>  
Do the TC members approve the Chair requesting the TC Administration hold a Special Majority Ballot to approve the charter revision contained in http://www.oasis-open.org/apps/org/workgroup/kmip/download.php/49466? - A link to the document containing the revised charter.  - Not including the link to the document containing the revised charter. - Passing requires a Simple Majority Vote for the Resolution. The Special Majority Vote requires a minimum of 2/3 of the Voting Members of the TC and no more than 1/4 may vote no. 
- The charter revision should contain a red-line of the differences between the current charter and the clarified charter.
- TCs are free to add additional information or instructions to their motion so long as (a) all required elements are provided and (b) additional instructions do not conflict with OASIS rules.
- TCs are free to record their votes in the minutes how they wish but should clearly document (a) that quorum was present, (b) the motion that was voted and (c) the vote tally.
21) Adopt standing rules  I move that the TC adopt the following standing rule as part of its operating procedures and communicate it to TC Administration for approval.

<text of the standing rule> 
- Ballot title: Adopt standing rule
- Ballot question: Do you approve adopting the following standing rule as part of the TC's operating procedures and communicating it to TC Administration for approval?

<text of the standing rule> 
- Ballot title: Adopt standing rule #1
- Ballot question: Do you approve adopting the following standing rule as part of the TC's operating procedures and communicating it to TC Administration for approval:

Rule 1: the TC will follow the issues lifecycle defined in CAMP TC Proposed Issues Process v6.ppt
- The language of the proposed standing rule. - Passing requires Full Majority Vote.
- The standing rule  may not relate to IPR, quorum requirements, membership, voting, participation, or that otherwise conflict with or supersede any OASIS Board-approved policy.
- The standing rule must be communicated to TC Administration for review. TC Administration may rescind the rule if it is in conflict with OASIS policies.
- Standing rules must be posted on the TC's public web page in order to be enforceable. 
22) Submit an OASIS Standard to another standards body   I move that the TC submit <OASIS Standard title and version number> to <name of the target standards organization> for International Standard and request the Chair to present this request to the OASIS President as required by the OASIS Liaison Policy (https://www.oasis-open.org/policies-guidelines/liaison)?
- Ballot title: Approve submitting <OASIS Standard title and version number> to <name of target standards organization>
- Ballot question: Do you approve submitting <OASIS Standard title and version number> to <name of the target standards organization> for International Standard and presenting this request to the OASIS President as required by the OASIS Liaison Policy (https://www.oasis-open.org/policies-guidelines/liaison)?
- Description: <any additional information you wish to add.>
- Ballot title: Approve submitting AMQP to ISO/IEC JTC1
- Ballot Question: Do you approve advancing AMQP 1.0 OS to an International Standard via the ISO/IEC JTC 1 PAS Process and submitting this request to the OASIS President via the AMQP Member Section Steering Committee?
- Description:  Since the approval of AMQP 1.0 as an OASIS Standard (October 2012), the AMQP Technical Committee has been evaluating various international standards organizations, in an effort to advance AMQP 1.0 to an International Standard status. Please see the references below for details.

Reference 1: AMQP 1.0 International Standardization.pdf (https://www.oasis-open.org/apps/org/workgroup/amqp/email/archives/201304/msg00002/AMQP_1.0_International_Standardization.pdf)
Description: This describes the various international standards organizations, recommendation, timeline, etc.

Reference 2: Submission for international standardization.pdf (https://www.oasis-open.org/apps/org/workgroup/amqp/email/archives/201304/msg00002/Submission_for_international_standardization.pdf)
Description: This contains the request package intended for submission to OASIS upon successful completion of this ballot.

Of the many pathways to international standardization that have been identified, ISO/IEC Joint Technical Committee 1 PAS (Publicly Available Specification)Transposition Process has emerged as the best option, considering various factors including taking advantage of OASIS as a recognized ISO/IEC JTC 1 PAS Submitter organization.
- The title and version number of the OASIS Standard
- The name of the standards organization and any other information relevant to the request. 
- The Work Product to be submitted must be an OASIS Standard.
- The receiving organization must be a de jure standards authority.
- An OASIS-sponsored public demonstration of interoperability involving at least three implementations must be carried out.
- A written request to submit the OS must be sent to the OASIS President and include the information listed in the OASIS Liaison Policy (https://www.oasis-open.org/policies-guidelines/liaison).