Home > Standards Blog

Advanced Search 

Welcome to ConsortiumInfo.org
Wednesday, June 28 2017 @ 02:38 PM CDT

Email Article To a Friend View Printable Version

If this were any other JTC1 Proposal, the OOXML Vote Would be Over Now

OpenDocument and OOXML

Updated:  I am now predicting that the OOXML vote has failed to pass.
Public announcements of how P members of ISO have voted on OOXML are now rolling in one at a time, and the trend thus far is meaningfully weighted towards "No with comments." 
By my count, there are now four announced Yes votes, with comments (Germany, Poland, Switzerland and the United States), two abstentions (Australia and Sweden, the former due to a failure to achieve consensus, and the latter due to voting irregularities), and seven eight public No with comments votes: Brazil, China, Denmark, France, India, Ireland, and New Zealand. Updated: and Norway; tracking changes made below.
There is also a blog posting of a No with comments vote by Korea here. In addition, I expect at least Canada, Japan and the United Kingdom to announce "No with comments" today or tomorrow (that would take us up to 12), and that a number of additional countries will be revealed to have voted in a similar fashion when the official vote tally is announced by ISO in the next day or so. 

The reason I say that in any other case the vote would be over now is because of the 11 countries that upgraded their status from Observer to Participating member status in the last few weeks. Without those extra 11 P countries, it would only require 10 votes to make an overall vote to approve impossible under the ISO rules (i.e., one more than 1/3 of the former 30 P members, minus the two that have abstained).

But with those eleven new P countries, and assuming no further abstentions, it could now conceivably take a total of 14 no votes, calculated as follows: there are 41 total P members. If all vote, as they are supposed to do, then you would subtract the two abstentions, yielding 39, and two-thirds of 39 is 26. Hence, more than 13 no votes would be needed to block a yes vote. And only by blocking a yes vote can there be assured to be a meaningful effort to address the many comments that appear to be accompanying the votes – including the yes votes. (You can read more on how the results will be calculated here).

Interestingly, while 13 countries have publicly announced their votes, not one of the new 11 P members has thus far revealed how it has cast its vote. As I have pointed out in several recent blog entries, (the latest is here), it will be very interesting to see how these last-minute additions to the P membership cast their votes. Those new P members, once again, are Cote d'Ivoire, Cyprus, Ecuador, Jamaica, Lebanon, Malta, Pakistan, Trinidad and Tobago, Turkey, Uruguay and Venezuela.

Updated:  You can follow a visual estimate by the folks at <no>ooxml.org site here that I assume they are updating in real time.  As I write this, they're guessing 18 no votes, which would be sufficient to block an outright approval.  A spreadsheet I received over the weekend from another group that has been following things closely was forecasting 16 No votes (on receipt also sufficient), and since then, one vote they expected to be a Yes turned to a No, and another to an Abstain.

For further blog entries on ODF and OOXML, click here

subscribe to the free Consortium Standards Bulletin

If this were any other JTC1 Proposal, the OOXML Vote Would be Over Now | 11 comments | Create New Account
The following comments are owned by whomever posted them. This site is not responsible for what they say.
If this were any other JTC1 Proposal, the OOXML Vote Would be Over Now
Authored by: Anonymous on Monday, September 03 2007 @ 11:26 AM CDT
The UK has announced - No with comments.


It is also suggested that Ecuador has voted no too. Iran is a No,

  The Open Sourcerer
[ # ]
If this were any other JTC1 Proposal, the OOXML Vote Would be Over Now
Authored by: Anonymous on Monday, September 03 2007 @ 11:57 AM CDT
It is still possible that some of those new P countries will vote no. We had been operating under the assumption that MS bought the new votes. We might be wrong. May be IBM bought a few as well, who knows ;-)

However, Brian Jones seems to be confidence to get 60%+. He must know something I don't, coz the incumbant vote is a rather strong "No".

If all the new countries voted "Yes", then ISO will have to seriously consider whether someone really stacked the voting process, as this is an unlikely result for 10+ new countries to come in with the same vote, particularly if incumbants voted "No" rather strongly.
[ # ]
If this were any other JTC1 Proposal, the OOXML Vote Would be Over Now
Authored by: Anonymous on Monday, September 03 2007 @ 01:01 PM CDT
For some reason, I'm minded of Japan's attempts to subvert the international whaling commission , which picked up countries from the caribbean and africa, countries that receive a moderate amount of 'aid' from japan and always vote to resume whaling. I wonder how many countries are in both lists.
[ # ]
Table of votes cast so far
Authored by: Anonymous on Monday, September 03 2007 @ 01:59 PM CDT
Hi Andy,

I have been trying to collate the votes cast so far. But I have managed to end up with 50 P members from various sources around the 'net.

The score I have so far with links to the news item where possible:
Yes = 10,
No = 14,
Abstain = 8,
Unkown = 18.

[ # ]
Authored by: Anonymous on Monday, September 03 2007 @ 11:41 PM CDT

I would suspect that there are far more irregularities than shown on the map at NOOOXML.org. Finland, for example gave MS an abstention, like Sweden later did, despite having a government mandate for use of ISO/IEC 26300 and several ministries already putting the format into production.

When this is over and done with, the relationship between Ecma and other standards bodies needs to be re-examined. This mess came from their collective desk.

Furthermore, fast-tracking may have outlived its usefulness and might be reconsidered.

Lastly, ISO should take a page from IETF's book and require that any specification have at least two working, independent implementations (e.g. OOo and Koffice) before even being considered.

[ # ]