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.

I have received several requests for an update on OOXML, so I will oblige with some quick observations in what (I hope) is my final update on this sad chapter in standardization.

New ODF Alliance member, more vendor support, and another, more positive way to view the i4i ruling

I have a question for Microsoft. Why didn't they tell us about this i4i patent litigation during the OOXML ISO process? Didn't we need to know?

FOSS people fed up with OOXML corruption and Microsoft fronts like Association for Competitive Technology

There is an interesting disinformation campaign being waged against ODF. You won't see this FUD splattered across the front pages of blogs or press releases. It is the kind of stuff that is spread by email and whispers, and you or I rarely will see it in the light of day. But occasionally some of it does cross my desk, and I'd like to share with you some recent examples.

Response to new disinformation from the Microsoft camp. Microsoft cheerleaders like Alex Brown and Jesper Lund Stocholm are quite deliberately misinterpreting or mis-presenting a vote related to OOXML by claiming that IBM "supports" OOXML.

Or both? ALEX Brown is pretending that all is fine and dandy with OOXML (he even shows a picture of a smiling face), despite all the OOXML corruption which had people protest out in the streets.