How many bad standards does one need in a given domain? Zero.
A lot of the debate around OOXML has focused on whether it is good to have competing standards or not. The debate started from the simple fact that Microsoft decided to create its own standard for office applications rather than adopt the established ISO standard for office applications: ODF.
While there is clearly a need for evolution and there are times when it makes sense to introduce a new standard to replace an old one there is no doubt in my mind that in general there is much more to lose from having multiple standards rather than a single one than there is to gain.
Interestingly enough I should point out that Microsoft defends that very point at times. In the case of XML for instance, when the W3C introduced XML 1.1 to address some internationalization limitations in XML 1.0, something important to many non-western countries, Microsoft voted against XML 1.1 arguing that the introduction of a new version of XML would be too disruptive!
Yet the tactic of introducing a competing standard to disrupt the status quo is common practice for the Redmond company. For instance, in the Web services management area, an area not so visible to the public as office applications but still very important to the IT industry, they did the same. Microsoft consistently refused to join the ongoing industry effort around Web Services Distributed Management (WSDM) at OASIS for years. They kept claiming that they had no interest in this topic. Yet, in 2005. after WSDM became an OASIS standard supported by a large segment of the industry mind you, Microsoft introduced their own technology named WS-Management, with support from some well chosen partners. Three years later the industry is still trying to figure out what to do with the mess they thus created.
But all this debate around multiple standards is somewhat of a distraction from the real issue at hand. In the end what is really being asked to National Bodies (NB) around the world isn’t to choose between ODF and OOXML, or to choose between ODF alone and ODF and OOXML. The question that NBs are asked to answer is whether OOXML deserves to become an ISO standard in its own right.
The reality is that if the OOXML specification wasn’t of such a poor quality it most certainly would have had a much easier ride through the Fast Track process. If all that could be argued against it was that it was too big, the IP license has gaps, and multiple standards aren’t good, this may not even have made headlines, no matter how true it is.
What is appalling about OOXML is that it is fundamentally a VERY BAD specification and I just can’t understand what process would allow this garbage to even be presented as an ISO standard up for vote. OOXML is from a technical point of view just terrible. All I’ve seen from it and all I’ve read about it only confirms this. And I have yet to meet any technical person arguing in all honesty that OOXML is a good specification. The latest facts reported by Rob Weir speak for themselves.
So, again, the real question isn’t so much whether the world would benefit from having several competing standards or not. The real question is how many bad standards do we need? And the answer is zero.
OOXML must be voted down simply because it is a bad standard.