Open standards exist for a reason: they allow users on different platforms, with different software and different ways of doing things to collaborate and exchange information freely. Oft-quoted examples include the TCP/IP protocols that allow computers across the Internet to talk to each other, and the plethora of web standards such as XHTML and CSS.
Almost by definition, it is not possible, nor desirable, to have two formats that cover one particular domain. And a war has been brewing in none other than in the document format arena: the battle between the Open Document Format (ODF) and Microsoft’s Open Office XML (OOXML) has just begun.
A standards war is typically just that: two standards compete against each other on technical aspects, and the better one wins. This time, we have the muddying effects of large commercial interests, and the possibility of legislative action. In recent months, legislation has been brought before several U.S. states (but defeated) to mandate the use of an open XML standard for use by government documents; this has been widely interpreted to mean mandating the use of ODF, because OOXML hasn’t quite yet been promulgated as an open standard.
It is a debate that doesn’t have a clear answer. The main piece of software that uses ODF is OpenOffice, which in my opinion is inferior to Microsoft Office (all things equal, and ignoring price). Microsoft Office, in its most recent incarnation, has demonstrated that it is a mature product; it is comfortable to use, and almost anyone can become productive with it almost immediately. While I’m not disputing OpenOffice’s ability to create documents and spreadsheets and what not, it feels like a cheap clone of what Office was about ten years ago; it feels clunky and wrong, and I just don’t like it. I’m sure others agree. People who know me will just argue this is just me exhibiting my usual biases.
There are a number of reasons, however, that ODF is preferable to OOXML; Rob Weir (an IBM employee) presents his arguments quite lucidly. The primary motivation behind the legislative push towards mandating the use of an open format is the realisation that we need a way in which documents can be kept for posterity; if we rely on a closed, proprietary format, our descendants in, say, 100 years’ time, will no longer be able to open our documents. I agree with this motivation, and I support open standards because they increase interoperability; I recall the days when writing web pages that behave reasonably identical in different browsers was an arduous task.
This is where the dilemma lies. ODF is more open; it is a community driven standard that has a number of open source writers/readers. OOXML is, I suppose, open; however, the format is published in a formidable 6,000 page document, and its development will always be driven by a single company – is that really open? (Even if it isn’t strictly open, I do note that having the format in a specification does enable document longevity.) However, mandating the use of ODF practically means mandating the use of OpenOffice, because Office support for ODF is rather poor (and is likely to be for the foreseeable future). Sure, I’m muddying the waters between formats and applications, but currently, the leading office productivity suite does not effectively use ODF. This is a problem that must be taken into account in any push towards mandating the use of a particular format.
One could argue that this is one of the evils of Microsoft’s monopolistic empire – that we are so addicted to their products that we are unable to move off them. The winner will be the camp with the biggest will, and the biggest ability to muster powerful friends. Perhaps it will once again be the law, and not economics, that breaks up a monopoly (c.f. AT&T). But there is one thing that is clear: in the end, there will be one format that prevails, for two is unsustainable and impractical.
To finish, it is slightly ironic that Microsoft is attacking open format legislation; their reaction is almost tantamount to denying that OOXML is not open. As Rob Weir notes, Microsoft executives have a history of making confusing statements; if they are actually confused, that isn’t a good sign, and if they are confusing us intentionally, I’m sorry, but the community isn’t that stupid. Microsoft shouldn’t be scared of open standards; they should just look to how successful Adobe has been with PDF.
Recent Comments