| |||||||||||||
|
| |||||||||||||
Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)Posted Sep 16, 2005 0:41 UTC (Fri) by coolian (guest, #14818)In reply to: Microsoft Challenges Massachusetts on Open-Format Plan (eWeek) by cventers Parent article: Microsoft Challenges Massachusetts on Open-Format Plan (eWeek)
Actually, I believe that they cannot call it "Open Document Support" if it
(Log in to post comments)
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 toenforce 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,
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.
|
|
||||||||||||