Microsoft Believes IBM Masterminded Anti-OOXML Initiative
mahuyar writes "Microsoft executives have accused IBM of leading the campaign against their initiative to have Office Open XML approved by the International Organization for Standardization. 'Nicos Tsilas, senior director of interoperability and IP policy at Microsoft, said that IBM and the likes of the Free Software Foundation have been lobbying governments to mandate the rival OpenDocument Format (ODF) standard to the exclusion of any other format. "They have made this a religious and highly political debate," Tsilas said. "They are doing this because it is advancing their business model. Over 50 percent of IBM's revenues come from consulting services."'"
Is that the pot calling the kettle black? If Microsoft is pulling out all the stops to steamroll their way to the front, I find it incredibly hypocritical of them to call someone else out on a counter.
So sad, that such a tiny little garage shop like Microsoft should be beaten up by the big bad IBM.
Anyone else think that this sounds like whining?
In Xanadu did Kubla Khan
A stately pleasure dome decree
You know how I know there's no God. Because if there was, a lightning bolt would come from the sky and blast this guy to smithereens.
After all the revelations of Microsoft's attempts to poison the standards process by buying votes, to accuse someone else of some dirty campaign is so hypocritical and immoral that one has to stand in awe of the kind of twisted mind that could produce it.
I thought only SCO's pathetic supporters with their claims that Groklaw was an IBM front were this warped, but Microsoft, congrats, you've produced the same specimen of irony-meter destroying beastling.
The world's burning. Moped Jesus spotted on I50. Details at 11.
IBM believes that Microsoft masterminded the Pro-OOXML Initiative.
Seriously, we've seen plenty of stories right here on Slashdot about Microsoft trying to buy the vote. Sweden comes to mind. And frankly, you can't call it lobbying when all you are doing is pointing out that Microsoft's "open" format is not actually open.
"It's not whether you win or lose, it's how drunk you get." -- H. J. Simpson
In this post and the posts above and below it I have an interesting discussion with someone who says essentially the same thing.
Personally, when it comes down to it, I don't care who is behind the standard as long as the standard meets certain *ahem* standards. Mainly I want inter-operable implementations from more than one vendor, and I would like at least one implementation that's fully Open Source and considered the reference implementation.
ODF meets all of those requirements. OOXML meets none of them. I don't think even Microsoft could make an implementation of OOXML in a clean room without using any of their other source code.
So, I care not one whit for the political machinations behind it all. All I care about is having a standard that's really a standard. Putting the political machinations to the fore is a mistake, and Microsoft is trying to capitalize on that to create a smokescreen that obscures the real issue, which is that their 'standard' is awful and unimplementable.
Need a Python, C++, Unix, Linux develop
Anyhow, not that it matters, but the truth seems to be the latter. Several groups and entities were opposed to OOXML, including many FOSS organizations like the FSF. And also IBM. Given IBM's money, perhaps it acted more than the others, I have no idea. If IBM did anything underhanded or unethical, then that would be very wrong, regardless of the worthiness of the goal. But, as it happens, Microsoft was caught buying votes, not IBM, so these accusations of Microsoft's are just ridiculous.
This should be a highly political debate - otherwise we encourage our Governments/Schools to continue to waste our taxes. If Microsoft didn't lobby such institutions then it would not be a political debate.
Calling Free Software a religious movement is a dubious and cheap slur against a movement.
Classic FUD.
Yeah, but.. " Microsoft executives have accused the rest of the world of leading the campaign against their initiative to have Office Open XML approved by the International Organization for Standardization. " doesn't have the right spin.
I've downloaded and looked at the MSOOXML spec and I thought it was some kind of insult. I seriously invite everyone who has ever read a spec, and who still doubts how bad this one really is, to download the 38 Mb PDF file from .. oh wait.. it's not there anymore..
now probably from ECMA-376 and you probably want the ZIP file "ECMA-376 part 4" (warning, 32 Mb) and also get the 2000+ pages of errata from ECMA which the countries have to read in the next 2 weeks before they get to have a final vote at the ballot resolution meeting.
You want the file titled "Office Open XML Part 4 - Markup Language Reference.pdf".
A copy of the 2200 page PDF file of criticisms can be downloaded from here.
Frankly, you can get a good laugh out of all the stuff about 1900 and 1904 date systems (response 43, I quote CH-0007
) and the mathematically wrong CEILING function (response 30 p. 121),
But I believe this is the one "killer question" that the BRM should consider discussing for those 5 days: Response 31 on p. 122 (211) to questions BE-0001, CH-0013, CL-0001, DE-0119, KR-0001, NZ-0003, PE-0010, ZA-0003
Basically, AFAIK, the comments are "We already have ODF, why do we need OOXML?" and the proposed solutions are of the gist "Develop OOXML starting from ODF". This is ECMA's response:
To be, or not to be: isn't that quite logical, Slashdot Beta?