M. Fioretti wrote:
On Mon, Jul 02, 2007 11:59:14 AM +0000, jonathon ([EMAIL PROTECTED]) wrote:
NoOp wrote:
That said, I'm not sure that I fully understand the issue with MS
wishing to register OOXML as an ISO standard; wouldn't that require MS
to fully publish all specifications regarding the protocol/software and
maintain that on a regular basis?
* Microsoft bribed the ECMA committee to accept the
submission. {The ECMA committee has publicly admitted to this.)
...
* The "specification" submitted to ECMA require that
calculations in the spreadsheet violate known mathematical
laws and principles; [IOW, the answers in your spreadsheet
will be incorrect, because the standard that they adhere to
requires wrong answers.];
Links to the two points above, please? I knew about the other
problems, but these two escaped me.
Thanks,
Marco
I already posted a link for the last one. Rather than find the link
again, I will be specific on the second point.
There is a bug in date handling for Excel so they propigated this to the
format rather than storing the correct date and then transforming inside
of Excel.
Here are some section references.
* OOXML does not conform to ISO 8601:2004 "Representation of Dates and
Times." Instead, OOXML section 3.17.4.1, "Date Representation," on page
3305, requires that implementations replicate a Microsoft bug that
dictates that 1900 is a leap year, which in fact it isn't. Similarly, in
order to comply with OOXML, your product would be required to use the
WEEKDAY() spreadsheet function, and therefore assign incorrect dates to
some days of the week, and also miscalculate the number of days between
certain dates.
* OOXML does not follow ISO 639 "Codes for the Representation of Names
and Languages."
* Similarly, 6.2.3.17 "Embedded Object Alternate Image Requests Types
(page 5679) and section 6.4.3.1 "Clipboard Format Types" (page 5738)
refer back to Windows Metafiles or Enhanced Metafiles – each of which
are proprietary formats that have hard-coded dependencies on the Windows
operating system itself.
* OOXML also apparently violates section 2.14 of the ISO/IEC Directives,
Part 1, in that not all of what it takes to implement OOXML appears to
be covered by Microsoft's patent pledge, in two respects. First, the
pledge does not explicitly cover material that is referenced, but not
included in the specification, and second, the Microsoft patent
commitment does not cover optional features. Sections of OOXML that are
not fully described include those that require compliant implementations
to mimic the behavior of Microsoft products, such as those products and
capabilities referred to above (OLE, etc.) Microsoft will need to
clarify whether its patent commitment will in fact extend to these
requirements.
Download the docs here:
http://www.ecma-international.org/publications/standards/Ecma-376.htm
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info: http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
