AboutWelcome to Free Software Daily (FSD). FSD is a hub for news and articles by and for the free and open source community. FSD is a community driven site where members of the community submit and vote for the stories that they think are important and interesting to them. Click the "About" link to read more...
Alex Brown recently tweeted to Microsoft's Doug Mahugh the following about OOXML:OOXML=tought [sic] fights; revealed JTC 1 procedures were rubbish. The OOXML approval was marred by procedures that were rubbish, eh? How about the result, then? Wasn't that exactly what the four appeals against adoption of OOXML stated as one basis, that the process was essentially rubbish? Were they right?
A gentler way to put this would be hard to find because ISO continues to show what a disgrace it has become. It was given a chance to change. It was given a chance to listen to polite critics and respond sensibly. It was given a chance to tell the world that it had been captured. But no.
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.
The ODFalliance.org now has a new OOXML Resource Section. Bellow you will find the complete text from “OOXML Implementations: A Community of One”. If anything, the ODF Alliance analysis is too charitable. OOXML is NOT CLOSE TO a community of one. Documents produced by Microsoft Office 2007 are not OOXML (Ecma 376), DIS 29500, or even DIS 29500 as amended at the BRM.
"As you will recall, V1, the INCITS Technical Committee that addresses document format standards, was unable to reach consensus on a recommended US vote to either approve or reject DIS 29500, the draft ISO/IEC standard that describes Microsoft's OOXML formats. As expected, Microsoft is seeking to gain a US vote in favor of OOXML..."
There is somewhat of an OOXML revolt brewing, claims one source while rather astounding developments from RedOffice remind of the threat to Microsoft Office (#1 cash cow) and power of FOSS.
Can anyone tell me what OOXML is for, other than for opening legacy Microsoft documents? What else is it for? When would you choose OOXML and when would you choose ODF, if you were, let's say, a government or a government agency?
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.
