Slashdot Mirror
Microsoft Spokesman Says ODF "Clearly Won" Standard War
Elektroschock writes "At a Red Hat retrospective panel on the ODF vs. OOXML struggle panel, a Microsoft representative, Stuart McKee, admitted that ODF had 'clearly won.' The Redmond company is going to add native support of ODF 1.1 with its Office 2007 service pack 2. Its yet unpublished format ISO OOXML will not be supported before the release of the next Office generation. Whether or not OOXML ever gets published is an open question after four national bodies appealed the ISO decision."
Im not against Microsoft (or any software developer) having their own format, even if its the default format, however, I think that 1) ODF should be left alone (no EEE) if added to a Microsoft product, and 2) that they supply a converter (as lossless as possible) that can convert both ways, from ODF, and to ODF.
Likewise, im glad to hear them admit it, but not as glad as I would be to hear that they are dropping OOXML.
Well, yes. But that's just what they say in public. In private they're probably saying, "oh shit, we were way too obvious and public about our criminal behavior and the EU looks ready to stomp on us hard for this one. Maybe if we pretend to roll over and pretend to support ODF for a while, the EU will not make this a priority and use the courts to force us to play nice, with real consequences and oversight. At least if we look like we're willing to be open, we can subtly break compatibility with others and try to extend it with proprietary DRM or something. Really anything that stops us from being declared to have monopoly influence in the office suite market and doesn't make us compete purely on our software's merits is workable."
OK, this is the first shoe to drop. (Sorry British Columbia, no offense)
The is the "embrace" part. Once they start using the format, just you watch, like Java, HTML, CSS, SQL, C++, C, etc. they will add features that break compatibility, because of, wait for it, "customer demand." As we all know "customer demand" will be asking a room full of carefully collected idiots a set of loaded questions.
I have worked closely, in the past, with Microsoft and they view any real standard as a threat. They wield their monopoly power and "defaco" status like a sledge hammer. They've done it in the past, and they'll do it with ODF.
The computing community has to monitor the situation and fight incompatibility as the run of the mill consumer has absolutely no idea what is going on.
We are in a very important phase. We (someone) needs to create an ODF compatibility test utility, like an HTML validator, that will test the compliance of an ODF file.
It can be used to catch Microsoft's crap. Remember, a word processing document is unlike HTML. HTML is likely to be seen by a multitude of people where as a document is probably only going to be seen by a specifically targeted group. Microsoft will be able to add incompatibility and almost no one will be able to notice until they wish to open THEIR document with a non-microsoft word processor or spread sheet. At that point it will be too late.
We also have to make sure that Microsoft's products render ODF compliant documents correctly when they are created by non microsoft applications.
The price of freedom is eternal vigilance.