Buscar en Mind w/o Soul

viernes, junio 08, 2007

Formato OOXML: no es abierto porque...





Slashdot | New York Jumps Into Open Formats Fray


I provided you with a link to explanations clearer and more concise than anything I could include here.


I'm aware you're not prepared to look at evidence which would conflict
with your view, but for the convenience of other readers, I've posted
the headers to the Groklaw articles which contain the complete
explanations.

# 7 Ecma 376 contradicts numerous international standards




* 7.1 The Gregorian Calendar


* 7.2 ISO 8601 (Representation of dates and times)


* 7.3 ISO 639 (Codes for the Representation of Names and Languages)


* 7.4 ISO/IEC 8632 (Computer Graphics Metafile)


* 7.5 ISO/IEC 26300:2006 (OpenDocument Format for Office Applications)


* 7.6 W3C SVG (Scalable Vector Graphics)


* 7.7 W3C MathML (Mathematical Markup Language)


* 7.8 ISO/IEC 10118-3, W3C XML-ENC, and other cryptographic hash standards


* 7.9 W3C SMIL (Synchronized Multimedia Integration Language)



# 8 Ecma 376 is immature and inconsistent


* 8.1 Fabricates units of measurement


* 8.2 Internal inconsistencies: the w:sz element


* 8.3 Internal inconsistencies and omissions: ST_Border


* 8.4 Confusing and inconsistent definitions of lengths of hexadecimal numbers


* 8.5 Unspecified terms: plain text


* 8.6 Poor names and inconsistent naming conventions for elements and attributes


* 8.7 Inflexible notation for percentages


* 8.8 Inappropriate non-document settings (application settings)


* 8.9 Non-XML formatting codes


* 8.10 Inflexible numbering format


* 8.11 Uses a Microsoft-specific namespace



# 9 Ecma 376 uses bitmasks, inhibiting extensibility and use of standard XML tools


* 9.1 Background: bitmasks


* 9.2 Bitmasks in Ecma 376


* 9.3 Bitmasks are not extensible


* 9.4 Bitmasks cause significant validation problems


* 9.5 Bitmasks defeat XSLT manipulation


* 9.6 Bitmasks conflict with the Ecma TC45 charter



# 10 Ecma 376 relies on undisclosed information


* 10.1 Undisclosed proprietary specifications


* 10.2 Cloning the behaviour of proprietary applications


* 10.3 Relies on application-defined behaviors



# 11 Ecma 376 cannot be adequately evaluated within the 30-day evaluation period


* 11.1 Ecma 376 has not met the stability requirement


# 12 Ecma 376 cannot be reasonably implemented by other vendors


* 12.1 Ecma 376 requires implementation of undisclosed specifications


* 12.2 The "compatibility with legacy formats" can only be implemented by Microsoft


* 12.3 Patent rights to implement the Ecma 376 specification have not been granted


o 12.3.1 The Microsoft covenants not to sue grant no rights


o 12.3.2 Microsoft licensing documents are ambiguous


+ 12.3.2.1 The Microsoft Open Specification Promise is ambiguous


+ 12.3.2.2 The Microsoft Covenant Not to Sue is irrelevant and ambiguous in any event


* 12.4 End-User License Agreements (EULAs) may forbid full implementation



Anyone
wishing to understand the full risks of implementing OOXML in their own
software should read the Groklaw page very carefully.

No hay comentarios: