Microsoft's Open XML Project A Short-Term Fix
TechPro writes "In an interview with eWeek the managing director of the ODF Alliance (Marino Marcich) was pretty dismissive of Microsoft's Open XML Translator project. While the move was a recognition of the ODF Format's acceptance by government's around the world, the installable software plug-ins that would be created under the project were really 'only a bridge, a stopgap measure that will probably not be acceptable to government's around the world over the long term. Plug-ins simply don't give the benefits of open file formats and standards,' he said."
I don't understand the problem. If it's a plug-in, and it reads and writes to the ODF standard, where is the problem?
The only thing I can think of is if people worry about a Microsoft "upgrade" breaking this plug-in. And then having to wait for the patch to the plug-in.
Excuse me, but, fuck "translating". This isn't about "translating". This is about being able to read ODF files and save your work to the ODF format.
"Translating" only comes into play when you're talking about:
a. Converting all your previous work to a new format.
b. When some people you are communicating with are restricted to the
c. And Microsoft's "Open" XML format will only be available in their NEXT release so it won't affect anyone who is still using their current or a previous release.
Am I missing something, somewhere?
Microsoft's claims seem to center around an organization upgrading to the next release of MS Office and then migrating to the ODF format.
While I see most situations as an organization migrating to the ODF format from an existing installation of MS Office 2000 or previous.
how long till they embrace and extend? Microsoft Open Document Format ODF with extensions, you can open ODF documents, but once you do microsoft starts "updating them" with MS only extensions, making MS documents all but unreadable in other word processors, and once an ODF file is opened in MS office it is modified so no longer conforms to ODF. They would surely claim, hey we support ODF see, everyone else is just not smart enough to offer you the extra stuff we put in, aren't we the greatest? 1. take someone elses great idea 2. break ...mmmmm extend it so it only works with MS windows
3. claim everyone else is broken
4. profit!
A Smith & Wesson beats four aces -- Murphy's Law of Poker
More money. Microsoft's driving force. Change gets folks to upgrade that Office Suite cash cow.
People bought Office95 and ran it for 3 years on one machine, and then put it on the replacment for that computer for another 3 years. Same with Office '97 and Office 2000 lasting for six years ... and $149 for Small Office Edition works out to be less than fifty cents a week for Microsoft.
Time to change document creation -- to a new distribution model like the antivirus publishers did.
The real problem for MS here is going to be OpenOffice. OpenOffice has already broken from the ODF spec to accomplish some things. If MS follows the ODF spec people will scream about it not working 100% with OpenOffice. If They break from the spec to support ODF, people will scream about "embrace and extend". Its pretty much lose-lose, but to you original point its OpenOffice that did the embrace and extend in this case and now MS has to decide how to deal with it.
"reality has a well-known liberal bias" - Steven Colbert
OpenOffice has already broken from the ODF spec to accomplish some things.
Interesting. Care to elaborate/give a link?
USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
Perhaps you just like saying things without really understanding what it is you said, but...
Windows has a kernel, and IE, GUI, command shell, filesystem browser, etc aren't part of it. Infact the Win32 API isn't even part of it. If you weren't aware, the windows kernel even has 2 other subsystems shipped for it (Posix, OS/2 1.1). Feel free to google to learn more.
In what way has ODF been extended by Open Office? A link would be nice...
The race isn't always to the swift... but that's the way to bet!