Part 2 of Rob Weir's coverage of Microsoft's very controversial OOXML Standard, which they, themselves don't even support.!

"In Part I of this OOXML update, my first post on the topic in over a year, I showed you how Microsoft maintains strong control over the OOXML standard. Despite their earlier promises that control of OOXML would be handed over to an independent, international committee, a look at attendance records reveals that the committee that maintains OOXML (JTC1/SC34/WG4) consists mainly of Microsoft employees, who outnumber any other company or organization on the committee 10-to-1."

"In Part III of this Update, I'll bring the story up to the present day, and in Part IV I'll update the story through the year 2016."

The Final OOXML Update: Part II
http://www.robweir.com/blog/2009/10/final-...te-part-ii.html

The Final OOXML Update: Part III
This is Part III of an 5-part series on the state of OOXML today. Previous to starting this series, I had not posted about OOXML in over a year. Part I showed how Microsoft, despite their promises that control of OOXML would be handed over to an independent, international committee, have instead stuffed the committee that maintains OOXML (JTC1/SC34/WG4) with Microsoft employees. And in Part II I looked at how the final published text of OOXML failed to account for all BRM decisions, and described the steps that ISO was taking to remedy this obvious procedural flaw.

In this Part I'll look at how Microsoft is using their dominance in SC34 to push through hundreds of changes and additions to OOXML, in a misuse of a procedure intended for correcting drafting errors, to make OOXML "conform" to Microsoft's monopoly product.

An Antic Disposition - Rob Weir
http://www.robweir.com/blog/