


Microsoft's documentation of the format consisted of a several thousand pages long semi-binary dump of the files produced by Microsoft Office - which are not much more than memory dumps containing binary blobs, poured into an XML container with vague descriptions of what the data types actually were - often no more than 'as produced by Microsoft Office version x.y'. I called OOXML a boondoggle because that what it was. ISO - which already standardised the Open Document format - did, giving Microsoft a weapon to wield in any bidding war on which file format should be adopted as a standard. Microsoft reacted like they often did: they created their own 'open' format, deceptively named 'Office Open XML' to make it easy to confuse with the OpenOffice XML-based format and submitted it to standardisation bodies in the hope that one would bite. Microsoft produced the boondoggle 'Office Open XML' formwat in reaction to the moves made by several large organisations to standardise on the Open Document format as used by OpenOffice et al.
