It's only strike one, but the first attempt to approve MS-OOXML for ISO certification on behalf of the US national body failed
late last week. It's not over until it's really
over, so be sure to read the comments
to temper the headline, especially the parts on how Microsoft has worked overtime to pack the national bodies
with its employees and business partners.
________________________________________________In related newsITworld.com - Microsoft OOXML spec "dangerously flawed"
"Microsoft’s Office Open XML (OOXML) document format specification is fatally flawed where it comes to spreadsheets, with many functions filled with careless errors, according to a critic."V1 committee gives thumbs down to Open XML doc spec
"...a number of countries argued that the Open XML proposal conflicts and overlaps with a previously established standard -- ODF -- and is poorly written and technically unsound."Standards Org Deals a Blow Against Microsoft's OOXML Format
"The group which recommends the way the U.S. votes on international technical standards failed to approve Microsoft's Open Office XML office document format."Microsoft open XML standard faces setback
"Given that pressure from many companies and governments has pushed them to creating an open standard, they have been working to doing just that – the Microsoft way."OOXML Denied INCITS V1 Approval
Among the obstacles vis-a-vis ODF, MS-OOXML faces:
— MS-OOXML is controlled by one company, not a standards body.
— Microsoft likes proprietary formats and has only gone the open format route because the market/industry forced them to do so.
— Microsoft was invited several times to join the ODF standards committee and refused all invitations.
— MS-OOXML is not actually open for anyone to implement: part of the specification references proprietary file formats (older ms-office formats)
and proprietary, binary code interdependencies off-limits to anyone else.And here's more, for argument's sake via the Free Software Foundation Europe