a 'mooh' point

clearly an IBM drone

ISO publishes OOXML

ISO today decided to make OOXML ISO-edition (IS29500:2008) publically available.

You can choose to purchase a physical print of the specification or you can download it for free at the ITTF website.






Comments (8) -

It seems like only yesterday...

Allthough the integrated schemas are looking nice and actually the whole spec looks very good (wihtout adressing the content) I would rather have separate schemas.


It seems like only yesterday...

Yes, it's quite amazing ... I almost can't imagine we're finally there.



I would rather have separate schemas.

The schemas in W3C Schema-format as well as RelaxNG-format are located in the files "electronic inserts".

Part 1: standards.iso.org/.../...08_Electronic_inserts.zip


Part 2: standards.iso.org/.../...08_Electronic_inserts.zip


Part 4: standards.iso.org/.../...E)_Electronic_inserts.zip


Thanks I had not spotted that there were two sperate links for those items on the ITTF page.

Could you upgrade some of your ealier handmade testfiles to the ISO standard to see if they are still being read by current OOXML implementations ?


That's not a half-bad idea and I'll look into it when I have some time.


I would like to try to predict the outcome, however:

There are two possible things to do:

1. Make an ISO 29500:2008 edition of the with the goal of making it readable for existing applications supporting ECMA-376

2. Making an ISO 29500:2008 edition with the goal of making it the way most applications will likely do it in the future.

ad 1)
This will likely be rather easy since most of the changes made during the approval process of OOXML left existing ECMA-376 documents compliant (in essence, the existing functionality was left in the transitional schemas)

ad 2)
This will most likely fail completely when trying to load them in existing applications (at least the documents that uses "new" functionality). This will include using ISO-8601 dates in SpreadsheetML, bitmasks, comments in SpreadSheetML using DrawingML etc.

Also, one thing is the XML-fragments being conformant. Another thing is that the namespace-references have also changed, so any application that does not support the new -"strict" and "-transitional" suffixes will almost guaranteed fail when loading these - to them - unknown namespace references.

I am unsure if there is anything to identify files using the ISO/IEC version with.
Else currently producing Ecma implementations depending on the extent of their implementation would qualify as (nearly) ISO/IEC compliant producers.

Comments are closed