Linked by David Adams on Sat 17th May 2008 03:35 UTC, submitted by pas de calais
Peter Hintgens, writing at Freesoftware Magazine, explains why the adoption of Microsoft's OOXML as an ISO standard is a dreadful development, and explains how some open standards partisans are organizing to combat insufficiently-open "open" standards.
Permalink for comment 314690
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
I here this oft repeated, daft remark time and time again, and it's usually used as some kind of bizarre justification for Microsoft to go off and implement their own OOXML format in Office, and it makes it all OK. It's quite funny as well, because it's an admission that Office 2007 is not OOXML compatible as the specification is now.
With ODF, people involved with Open Office, KOffice and other software are continually contributing to successive versions of ODF, and no, they're not going to have all of it implemented right now. However, there is an awful lot that has been implemented that is common between different implementations of ODF, and there are test suites and coverage reports available so you can verify how far they have got.
Can Microsoft provide that? Is there a coverage report and test suite for OOXML and Office? Considering that OOXML has been set in stone before it was ever submitted to the ECMA, and no changes have ever been made to it and no successive versions have ever been made, one would have thought that Microsoft would have had a fighting chance of implementing OOXML in Office, per their own specification, properly, no?
Edited 2008-05-18 08:57 UTC