Recently we mentioned the fact that Microsoft's OpenXML -- a so-called 'standard' which Novell agreed to support -- already has proprietary 'extensions'. From there onwards, the criticism just won't end. We wish to present just a couple of blog items which address the issue at hand. They are worth reading. Hilarity could ensue, if only it were not so sadly real.

Calling Captain Kirk

When you get an OOXML document, you don't know what is inside. It might use the deprecated VML specification for vector graphics, or it might using DrawingML. It might use the line spacing defined in WordProcessingML, or it might have undefined legacy compatibility overrides for Word 95. It might have all of its content in XML, or it might have it mostly in RTF, HTML, MHTML, or “plain text”. Or it may have any mix of the above. Even the most basic application that reads OOXML will also need to be conversant in RTF, HTML and MHTML.

The Open XML Lie

The basic premise of Rob’s article was that the Microsoft Open XML Specification was similar to creating a job description that would allow for only one qualified respondent. Such a job description might read as follows:

• 5 years experience with Java, J2EE and web development, PHP, XSLT
• Fluency in French and Corsican
• Experience with the Llama farming industry
• Mole on left shoulder
• Sister named Bridgetter

Let us not forget the legal issues one faces when fully implementing OpenXML support.