Voting Rules

OOXML passes if 66% of the voting P-Members vote Approve, and no more than 25% of the total vote (P-Members plus ISO plus IEC) vote Disapprove.

Deadline for the ballot is Sept 2nd. All who are eligible to vote (JTC1 P-Members as well as general ISO and IEC members) have that same deadline. Only those who vote Approve or Disapprove are counted. Those who Abstain or do not return the ballot are ignored.

For more details, see the JTC1 directives, p48-49:

9.8 Votes on Fast-track DISs

The period for fast-track DIS (or DAM) voting shall be six months, consisting of a 30-day JTC 1 National Body review period followed by a five-month ballot period. NBs may reply in one of the following ways:

  1. Approval of the technical content of the DIS as presented (editorial or other comments may be appended);
  2. Disapproval of the DIS (or DAM) for technical reasons to be stated, with proposals for changes that would make the document acceptable (acceptance of these proposals shall be referred to the NB concerned for confirmation that the vote can be changed to approval);
  3. Abstention (see 9.1.2).

[Note: Conditional approval should be submitted as a disapproval vote.]

The criteria for approval are given in 9.6. If these criteria are not met initially, but are subsequently met at the
conclusion of ballot resolution in accordance with 13.9, the DIS (or DAM) is approved.

Our interpretation of the JTC1 directives is that, if the delegation has technical comments (te), their vote should be only a "NO". In the "Yes with comments", only editorial (ed) and other general comments (ge) are allowed.

You can also have a look at the voting forms which confirms the options of conditional approval and the no with technical comments.

An ODF Alliance paper has also more informations.

Furthermore the voting form G18 contains the following:

If a national body votes affirmatively, it shall not submit comments. If a national body finds the DIS unacceptable, it shall vote negatively and state the technical reasons.

Abstentions and failure conditions

http://www.geniisoft.com/showcase.nsf/archive/20070925-1217