Microsoft Blasts IBM Over XML Standards
carlmenezes writes "Ars Technica has up an article discussing Microsoft's latest salvo against IBM. Microsoft's open letter to IBM adds fresh ammunition to the battle of words between those who support Microsoft's Open XML and OpenOffice.org's OpenDocument file formats. Microsoft has strong words for IBM, which it accuses of deliberately trying to sabotage Microsoft's attempt to get Open XML certified as a standard by the ECMA. In the letter, general managers Tom Robertson and Jean Paol write: 'When ODF was under consideration, Microsoft made no effort to slow down the process because we recognized customers' interest in the standardization of document formats.' In contrast, the authors charge that IBM 'led a global campaign' urging that governments and other organizations demand that International Standards Organization (ISO) reject Open XML outright."
It does not take a rocket scientist with a good look at the spec to figure out it sucks. The fact that it sucks has little to do with IBM.
Got Code?
Besides being an open standard, the standard needs to be usable by people other than Microsoft. Why would any document standard need specific tags for Windows 95? IBM lobbied against it because it was a bad standard, not because it was made by Microsoft.
After all they had to create a 6000 page document without releasing any information on how to make their "open" standard work. There are so many statements like "functions as per Word 95" without explaining what that means. They must have worked long hours creating a specification that doesn't actually specify how to implement it.
IBM is being a big bully and not allowing Microsoft to screw the public and private companies of the world as Microsoft wants to.
Naughty Naughty Big Blue.
After reading the Open letter, it's very clear that Microsoft claims IBM's want to stop Open XML stems from their ODF format making it through the standards group first and being adopted. MS claims that people should be able to choose their open standards...
Call me crazy but having two different standards doesn't really capture the idea of having Standards at all. I thought the point of standards was to make it so we (the developers) only have to implement one thing. I can fully understand IBM's reasoning here. The only thing it seems MS wants to do is create more vendor lock.