Slashdot Log In
Microsoft Spokesman Says ODF "Clearly Won" Standard War
Posted by
kdawson
on Friday June 20, @09:36AM
from the it's-just-better dept.
from the it's-just-better dept.
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."
Related Stories
[+]
Microsoft Office 2007 to Support ODF - But Not OOXML 377 comments
Andy Updegrove writes "About two hours ago, Microsoft announced that it will update Office 2007 to natively support ODF 1.1, but not to implement its own OOXML format. Not until Office 14 is released (no date given so far for that) will anyone be able to buy an OOXML ISO-compliant version. Why will Microsoft do this after so many years of refusal? Perhaps because the only way it can deliver a product to government customers that meets an ISO/IEC document format standard is by finally taking the plunge, and supporting 'that other format.' Still, many questions remain, such as when this upgrade will actually be released, how good a job it will do, and whether the API Microsoft has said it will make available to permit developers to supply 'save to ODF' default plugins will be supported by a patent non-assertion promise allowing implementations under the GPL (the upgrade supplied by Microsoft will not allow ODF as the default setting)."
[+]
ISO Puts OOXML On Hold 138 comments
schliz alerts us that ISO, in response to the four appeals (Venezuela, India, Brazil, South Africa) filed in recent weeks, has put the OOXML standardization process on hold. Here is ISO's press release, which says that ISO/IEC DIS 29500 will not be published for at least "several months" while the appeals process goes forward.
Update: 06/11 10:13 GMT by KD : Reader Alsee points out that the fourth officially recognized appealing country is Venezuela, not Denmark as originally stated. The protests of Denmark and Norway are being disregarded, as they do not come from the administrative heads of their national organizations.
Update: 06/11 10:13 GMT by KD : Reader Alsee points out that the fourth officially recognized appealing country is Venezuela, not Denmark as originally stated. The protests of Denmark and Norway are being disregarded, as they do not come from the administrative heads of their national organizations.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.

The end of vendor lock-in for Microsoft? (Score:5, Insightful)
Sadly, no, this is not the end of vendor lock-in for Microsoft. I guarantee that ODF will not be the default format and that Microsoft's implementation of ODF will clearly be some variation of 'embrace, extend, extinguish,' just like everything else they do.
Still, it feels good to hear a Microsoft employee admit that OOXML lost.
Reply to This
Re:The end of vendor lock-in for Microsoft? (Score:5, Interesting)
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.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Funny)
however, I think that 1) ODF should be left alone (no EEE)
Hey, I'm using OpenOffice on my Eee PC right now, you insensitive clod!
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Insightful)
Word format documents probably hold 80% of the world's knowledge.
You have got to be kidding. I don't pretend to know what percentage of the world's knowledge is in .doc format, but I'd be amazed if you weren't at least an order of magnitude out.
Just think of all the knowledge that is in text fields in databases, on web sites in HTML, in PDFs (extremely popular especially online, even MS offer documents in PDF), and of course *printed out on paper*.
80% of the world's knowledge in .doc? Rubbish.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Insightful)
your getting ahead of yourself. First it is Embrace.
What is MSFT doing right now? Embracing ODF, next comes a slow extension of ODF to make it MSFT only.
1) Embrace --- MSFT is doing this part now
2) Extend -- wait about a year for this to start happening
3) Extinguish --- OOXML rulez. in about 2010 or when the next version of Office Ships.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Insightful)
No, it doesn't mean that Microsoft will make ODF the default format. It does mean, however, that I could send an Office 2007 user an ODF document that I made with OpenOffice.org and they would be able to open it. They, in turn, could save their file as ODF and send it over to me if I ask for all documents to be sent in ODF format. This represents a serious hole in the "must send everything DOC to ensure compatibility"* lock-in.
* Yes, I know that DOC had troubles across Office versions, but still sending DOC was your best bet if you wanted the party at the other end to be able to open and edit the document you were sending.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Insightful)
And render correctly, just like if you created a W3C-compliant HTML 4 document with a W3C-compliant CSS style sheet that displays correctly in every other browser other than IE, right?
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Insightful)
Yes, I know that DOC had troubles across Office versions, but still sending DOC was your best bet if you wanted the party at the other end to be able to open and edit the document you were sending.
Your statement, taken as a whole is correct. I just don't believe the last part "and edit the document you were sending" comes up very often. I can't think of one time I've been sent a document that someone wanted me to edit during the whole 18 years I've had internet access. 99.99% of the time I get documents someone wants me to review, but not edit in any way. In those cases I'd much rather get a PDF.
If it's a collaborative editing situation, I'd rather use something like Google docs (and have).
The bigger deal for a single document format is really just archival purposes. I want to be able to save a document today, and open the same document in 10 years with totally different software, on a completely different OS and computer. You're not really even guaranteed of doing that TODAY with .doc.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Funny)
And we know Office will render/produce ODF just as well as IE 6 renders standards compliant HTML.
The ODF version of this comment is best opened with Microsoft Office 2007 or higher.
Reply to This
Parent
Re:The end of vendor lock-in for Microsoft? (Score:5, Informative)
http://www.betanews.com/article/Next_Office_2007_service_pack_will_include_ODF_PDF_support_options/1211343807 [betanews.com]
There will be an option in both the installer and options menu to choose ODF as the default format, if you want.
Reply to This
Parent
In other news... (Score:5, Funny)
Ice-capades grand opening in hell marred by dive-bombing pigs.
Reply to This
Wait and See (Score:5, Insightful)
Now we shall all have to wait and see if MS plays nice with ODF because they are scared of the EU, or if they try to extend and break the standard to prevent true interoperability, as they have done with HTML, CSS, etc. since being late to the Web standards game.
Reply to This
In other news... (Score:5, Funny)
Reply to This
Ok, this is the "embrace"-part... (Score:5, Insightful)
... wait for the next phase!
Reply to This
Consumer vs Professional (Score:5, Insightful)
The question is whether Microsoft is going to really support ODF or just give lip-service token support. For example, how fast are bugs in the ODF support going to be fixed? Remember how Micorsoft "supported" Java with their non-compliant, buggy implementation?
Reply to This
Let's not get too excited! (Score:5, Interesting)
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.
Reply to This
I was in this session... (Score:5, Informative)
And in fact asked the question "Is this just Microsoft doing the first stage of embrace, extend, extinguish?" I was not happy with his response. He floated the idea of merging the two standards, which really concerns me, and also seemed to acknowledge that there was going to be some extension.
From the impression I got, we got thrown a bone, and ODF and OOXML are going to be merged in the next couple of years, and MS will have de facto control because OOXML allows for proprietary extensions.
MS is not going to take this lying down.
I did shake Stuart's hand afterwards, however. He deserves props for showing up and taking a little abuse, although I was not near as hard on him as I would have liked to be, just because other people also deserved a chance to ask questions.
One thing that struck me is that one of the Singapore standards guys was there, and he was NOT happy. He was pretty pissed off that they could not provide even one reference implementation.
But... like I said. Props for showing up, MS. Now you just have many years of monopolistic behavior to live down, and I'll never trust anything you say again.
Reply to This
ODF Compatibility test utility (Score:5, Interesting)
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.
Reply to This
Re:ODF Compatibility test utility (Score:5, Insightful)
a). A Reference implementation conforming 100% to ODF 1.1 . Open source, freely reusable.
b). Requirement for any conforming implementation which wishes to be known as ISO ODF to be certified to pass a standard test suite.
c). Any "extensions" introduced after MS does the "embrace" to be by some standard mechanism which enables other implementations to quickly adapt to it.
Since (c) is practically a given where MS is concerned I'm most worried about that one.
Andy
Reply to This
Parent
Re:ODF Compatibility test utility (Score:5, Informative)
Reply to This
Parent
standard business tactics (Score:5, Insightful)
Of course, they will support ODF. It's too big a thing to ignore.
Also of course, their implementation will have a few... quirks. You know, implementation bugs that happen symmetrical on both import and export, so they never show up to you, as long as you stay within the MS world. Meanwhile, everything someone with a different ODF implementation sends you will show up buggy, and everything you send them will not quite properly work.
Details, of course. Like footnotes misaligned, or small formation differences. Just enough that nobody calls it bugs, just "quirks", but enough to make sure nobody within a corporation, for example, uses something different.
Reply to This
Re:That's It???! (Score:5, Interesting)
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."
Reply to This
Parent
Re:That's It???! (Score:5, Insightful)
Given the lengths they went to, first to fight the very notion of an open standard format, and then to push OOXML, it seems hard to believe that this is over.
I'm as happy as anyone else if it is, but it's very unlike MS. To my knowledge, this has happened only once before, with HTML, and we're still paying for the fallout of that one.
Reply to This
Parent
Re:That's It???! (Score:5, Funny)
"The cake is a lie."
"Beware of Greeks bearing gifts."
Reply to This
Parent
Re:That's It???! (Score:5, Funny)
Reply to This
Parent