Office applications Toolkit
Story: Google: OOXML 'insufficient and unnecessary'
A bit of background...
I've ducked out of this discussion for a bit to do a little research. To that end I provide a couple of links:
http://www.groklaw.net/articlebasic.php?story=20051128191449853
http://www.grokdoc.net/index.php/EOOXML_objections
I'm going to be very blunt. Any discussion here is small potatoes compared to the extensive analyses of OOXML for example that have already been done. Just follow the above links as examples. Also look at the following:
http://www.ariplex.com/tina/tcfact01.htm
It is extremely educational to go over the discovery papers and discussions of Microsoft's business practices, as revealed by various law suits brought against the company.
In the end, Microsoft has a very very long and colorful history that clearly paints them as a dishonest law-breaking monopoly that is not to be trusted. For those willing to take the time to look, you can see a clear pattern of behavior from the company.
Perhaps Google has it's own agenda for ODF. Fine. However, look at Microsoft and THEIR history! There is an old phrase, "Better the devil you know..." In this case I dare say Microsoft is the exception to that saying.
Full Talkback thread
Story: Google: OOXML 'insufficient and unnecessary'
-
Very nice Albert lars -
Microsoft double-tongued Anonymous123
-
ODF useless for Microsoft needs Albert
-
OOXML is fully open Albert
-
Sorry, the comment was cut short. Here'... garyedwards
-
Reasons for lack of interoperbility in ODF Albert
-
ODF, The Big Picture Goldie Simmons
-
Breaking the Web garyedwards
-
Google has invested in competing format Albert
-
Document standards 2000355890
-
Questioning Google’s objectiveness harpless
-
Microsoft's Argument is Ridiculous Goldie Simmons
-
insufficient and unnecessary standard, designed pu... ator1940
-
Interoperability and the binary ODF conversion di... garyedwards
-
A bit of background... Anonymous123 -
Microsoft moves forward with OOXML SDK Karen Friar
-
The rest of the text in the previous tal... lars -
Google motivation Albert
-
Which OOXML features in particular can't... Chris Rankin
-
XML in spirit isn't going to be as effic... Anonymous123
-
But does even Microsoft Office use OOXML... Chris Rankin
-
Thanks Gary, very informative Goldie Simmons
-
Durusau's proposal is preposterous Marbux
-
A very Interesting Take Moley
-
Features not in ODF Albert
-
OOXML performance explained Albert
-
Office and OOXML David Meyer
-
MS Office 2007 does fully support O... Albert
-
ISO Credibility garyedwards
-
Thank you for an intelligent r... Anonymous123
-
Of course ODF isn't backwards... Chris Rankin
-
Then why add "read"... Chris Rankin
-
00o writes compliant files Goldie Simmons
-
You are contradicting Rupert G... Chris Rankin
-
Terse markup for speed -- NOT Marbux
-
Tail end of previous comment garyedwards
-
Cut to the chase garyedwards
-
ODF also has backwards compati... Albert
-
MS influencing ODF development... Albert
-
No, OOo is not fully complient... Albert
-
MS Office 2007 files fully val... Albert
-
That's OK, I contradict R... Rupert Goodwins
-
Widespread support for OOXML a... Albert
-
Actually OOXML is not really t... Albert
-
Actually MS Office 2007 compli... Albert
-
Actually, you're making all th... Chris Rankin
-
It's a question of greate... Chris Rankin
-
Questions for the community Goldie Simmons
-
Do tell me more, Albert Marbux
-
Albert, give me a single examp... Marbux
-
Open Standards Moley
-
If you plan for incompatiblity... Albert
-
Believe is in the prove Albert
-
ODF and OOXML are standards in... Marbux
-
explaination Albert
-
ODF better readable but less g... Albert
-
Interoperability Albert
-
OOXML is Open Albert
-
Then why does the same spreads... Marbux
-
Extensions are bugs, not featu... Marbux
-
OOXML interop is abysmal Marbux
-
Extensions to ODF realistic ? Albert
-
Undocumented eXtensions and St... garyedwards
-
Not 1,500 extensions Marbux
-
You've got to be kidding,... Marbux
