OSNews

Personally I can see your point. However, there is a fundamental difference between the ODF/OOXML debate and the RPM/DEB problem. I think that this fundamental difference, which may have been otherwise stated (I'm neither an expert nor an historian on this matter), is that the RPM/DEB problem is about variety in composing the standard ELF file format and LSB system structure into a package, whereas the ODF/OOXML debate is about the standard itself. Or in simple terms, RPM/DEB works at a much higher level, and with much interoperability compared to ODF/OOXML.

Although ODF and OOXML are basically zip-ed XML files, the crucial need for the document saved to be sufficiently reproducible by their implementations makes the argument a lot lower level than RPM/DEB. Additionally, the similarity between the role of both ODF/OOXML and RPM/DEB as containers of data do not correlate sufficiently since ODF/OOXML encapsulate so much crucial metadata that basic functionality will be lost if even the syntax of the metadata is changed. RPM/DEB, on the other hand, are so similar, converters exists that preserve all data and sufficient metadata for most functionality to survive conversion. This is simply due to the fact that RPM/DEB are constructed out of ELF and LSB that are high level enough for a common playground of innovation be viable, whereas XML is simply too implementation-specific and mission critical for them to coexist.

This is the reason I urge you to treat the discussions differently. Please do note that this discussion has begun to oppose OOXML before even touching on technical merits. Which is where the rest of the discussion will dwell upon.

As a simple google will verify, many people have stated that OOXML is not a viable standard because of various issues. Its documentation may be huge, but its size is self-detrimental -- it is huge but has little content, and the rest of the bulk is simply there to cloud judgement, as some point out.

Well, if content is little, at the least it should be implementable. However, with just the documentation alone, it is not possible since much of the documentation allows for binary blobs of older, proprietary technology and references to Microsoft Office (where behaviour is supposed to just mimic Microsoft Office, with no indication of what it might be, especially if access to Microsoft Office is not possible)

Moreover, ODF is an extensible standard which has shown that it can make up for shortcomings by revisions. The only example known to the author is ODF's Formulas, which are a later addition to the standard after much complaints from the Microsoft camp. Outrageously, since Microsoft was originally in the OASIS, they could have simply made improvements to the standard instead of competing with the standard in a lose-lose situation.

Last but not least, OOXML is so obviously an attempt by a monopolist to defend its monopoly through lobbying and the spreading of misleading terms (regardless of whether it is intentional, most notable in the example of Office Open XML which is confused with OpenOffice, the rival using ODF). A convicted monopolist trying to lobby for itself will surely hurt the consumer if allowed.