LWN.net Logo

Advertisement

Front, Kernel, Security, Distributions, Development. See your byline here on LWN.net.

Advertise here

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 15, 2005 17:44 UTC (Thu) by cventers (subscriber, #31465)
Parent article: Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

I hope Massachusetts follows through. This decision could snowball and
destroy Microsoft's proprietary XML bullshit - a format which if not
stopped will lead to even *less* compatibility with their crap than
before.

Microsoft claims they won't support OpenDocument. I think they're
bluffing. I'm betting they already have OpenDocument support implemented
and ready to deploy at a moment's notice. The decision will likely come
down if they can't kill OpenDocument. They can still implement
OpenDocument in a generally buggy way to try and damage interoperability,
and they can certainly still play the three E's.

But the XML schema Microsoft has developed is a real danger to the
computing community, so I hope it dies.


(Log in to post comments)

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 15, 2005 18:32 UTC (Thu) by thomask (guest, #17985) [Link]

"they can certainly still play the three E's."

maybe I'm the only one here who doesn't know what "the three E's" are, but could you play E for enlightenment for me, please?

Thanks.

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 15, 2005 18:38 UTC (Thu) by meffie (guest, #3120) [Link]

3Es = embrace extend extinguish

http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 15, 2005 18:39 UTC (Thu) by eli (subscriber, #11265) [Link]

I had to pause a moment when I read that too, having not seen it
compressed that far. But anyway, I believe the "three E's" are Embrace,
Extend, Extinguish.

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 16, 2005 0:41 UTC (Fri) by coolian (guest, #14818) [Link]

Actually, I believe that they cannot call it "Open Document Support" if it
doesn't pass a certain amount of tests the OASIS Foundation set up, for
just this type of occurrence. So, perhaps the triple-E will be a bit
harder to do this time...

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 16, 2005 0:48 UTC (Fri) by cventers (subscriber, #31465) [Link]

Let us hope then that the OASIS Foundation has the backing / balls to
enforce this rule.

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 16, 2005 7:15 UTC (Fri) by Wol (guest, #4433) [Link]

I think, basically, all the OASIS group have to do is publish the DTD.

ANYBODY can then test a document to see whether it is well-formed and valid, and if MS-Office starts producing faulty documents then everyone will know where the blame lies.

It's a bit difficult for MS to do even the second E when any Tom, Dick or Harry can spot it. Especially as Mass. requirements are that the format should be stable and non-changing.

Cheers,
Wol

Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)

Posted Sep 16, 2005 8:52 UTC (Fri) by hingo (guest, #14792) [Link]

Nope. You can be fully compliant with a DTD or Schema, but still position everything wrong when the document is viewed in your word processor.

Similarly, no amount of testing can guarantee 100% interoperability. That's like there could be an automated test that guarantees there are no bugs in your software. I'm sure whatever certification process OASIS has in place, a hundred well paid MS engineers can easily implement an Open Document filter that passes the tests but is useless for interoperability purposes.

Copyright © 2012, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds