IS 29500 has been sent to ITTF for publication

by jlundstocholm 26. September 2008 19:34

This email just landed in my mailbox this morning:

ISO/IEC JTC1/SC34 N1080
Final Text for ISO/IEC 29500-1, Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 1: Fundamentals and Markup Language Reference
Status: This text has been submitted to ITTF for publication. It is circulated to the SC 34 members for information.
 
ISO/IEC JTC1/SC34 N1081
Final Text for ISO/IEC 29500-2, Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 2: Open Packaging Conventions
Status: This text has been submitted to ITTF for publication. It is circulated to the SC 34 members for information.
 
ISO/IEC JTC1/SC34 N1082
Final Text for ISO/IEC 29500-3, Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 3: Markup Compatibility and Extensibility
Status: This text has been submitted to ITTF for publication. It is circulated to the SC 34 members for information.
 
ISO/IEC JTC1/SC34 N1083
Final Text for ISO/IEC 29500-4, Information technology --Document description and processing languages -- Office Open XML File Formats -- Part 4: Transitional Migration Features Due date: --
Status: This text has been submitted to ITTF for publication. It is circulated to the SC 34 members for information.
 
This will finally make it possible for the NBs of ISO to verify that the editorial instructions from the BRM has made it into the final text. I have not yet had the time to investigate and verify that the Danish changes has been implemented, but I am sure lots of blogging will take place over the next days.
 
Smile

Comments

9/26/2008 9:15:28 PM #

hAl

Probably someone seeking attention will want to publish it on the net somewhere soon enough.

hAl |

9/26/2008 9:46:35 PM #

jlundstocholm

hAl,

Probably someone seeking attention will want to publish it on the net somewhere soon enough.
I am sure that is a correct assessment. I wish I had a whistle-blower website I could send stuff to and have it "anonymously leaked".

Smile

jlundstocholm Denmark |

9/27/2008 2:15:32 AM #

franco

"IS 29500 has been sent to ITTF for publication"

so, 09/26/2008 will be remembered as the "shame day of international standardization"

franco United States |

9/27/2008 4:49:46 AM #

orcmid

Well, I went to the SC34 /open folder on the off chance the files were hidden in plain site, but it wasn't to be.  The highest-numbered document there is N1079.

Yes, it will be good to have our hands on these at some point.  I presume that they will show up as publicly-available downloads while ISO also has them for purchase at an unbelievable charge-by-weight.  I think gold is a better alternative for protection in the current economic disturbance.  (Investing in under-priced equities might be more beneficial in the long run, but you need cash to spare for that.)

orcmid United States |

9/27/2008 6:39:29 AM #

Rob Weir

These appear to be the same versions that were posted to the SC34 web site back in April, but were taken down hours later.  The April version also said that it had been sent to ITTF for publication.

So my advise would be to download them now, lest they change their mind (again).

On the other hand, any attempt to verify that the changes were correctly made in this text would be toothless.  At this point in ODF's processing SC34 had a 30-day default ballot specifically for this question -- had the Project Editor correctly carried out the NB's editing instructions?  So with ODF there was an opportunity for NB's to report such errors and have them addressed in the published text.  But this step has silently been removed from the processing of OOXML.

Rob Weir United States |

9/28/2008 12:51:55 AM #

Murata

Japan has submitted the first defect report.  This will be discussed in the SC34/WG1 meeting tomorrow.

http://www.itscj.ipsj.or.jp/sc34/open/1084.htm

Murata |

9/28/2008 2:16:54 AM #

jlundstocholm

Murata,

Japan has submitted the first defect report. This will be discussed in the SC34/WG1 meeting tomorrow.
Fabulous - I suspect the Danish NB will go through the Danish comments some time in October.

I would have loved to be in Korea to discuss these things, but due to other activities I am sadly not able to be there.

Smile

jlundstocholm Denmark |

9/28/2008 2:21:17 AM #

jlundstocholm

Rob,

So my advise would be to download them now, lest they change their mind (again).

Waaay ahead of ya ... I did this as the very first thing.

Smile

At this point in ODF's processing SC34 had a 30-day default ballot specifically for this question -- had the Project Editor correctly carried out the NB's editing instructions? So with ODF there was an opportunity for NB's to report such errors and have them addressed in the published text. But this step has silently been removed from the processing of OOXML.

I noticed that the text referenced above says "It is circulated to the SC 34 members for information." I would expect the text so say "for review" along with a due date or something similar, if the NBs were to provide feedback on the text before "real" publication. But then again, maybe my understanding of ISO-lingo is not complete.

jlundstocholm Denmark |

9/28/2008 5:56:39 PM #

Alex Brown

Jesper hi

The text that has now been made available is the text that will be published by ITTF as ISO/IEC 29500:2008. There is no opportunity for modifying it. That is the correct operation of the Fast Track procedure (such as it is).

If and when NBs discover defects in the document they can submit defect reports to SC 34 - the project editor is obliged to respond to these within eight weeks.

In Jeju we have just been discussing this and it looks likely SC 34 will ask for defects relating to BRM-mandated changes to be given priority. Any changes that need to be made can then get published as corrigenda in the normal way.

- Alex.

Alex Brown United Kingdom |

9/29/2008 8:40:54 PM #

hAl

The text that has now been made available is the text that will be published by ITTF as ISO/IEC 29500:2008. There is no opportunity for modifying it.

Why not ?
The ITTF as far as I can see has the ability to correct the text possibly together with the project editor any time before publication. Releasing the text to the natiional bodies does not imply that the text is nescesarily 100% edit error free.

It should be valid and timely for a short time to still remark edit mistakes that are not in accordance with the draft edits based on the BRM resulotions.
It should be so hard to correct errors if mistakes were found that are not in accordance with the proposed BRM resolutions.

I would certainly advise to give the national bodies a month or so to verify the improvement edits to the resolution that they submitted and submit defect rapports if needed. That should be sufficient to reasonably verify the edits made.
Defect rapports submitted later could then still be used for an errata.

hAl |

9/30/2008 8:18:16 PM #

hAl

From a response on Alex blog I get that defect reports cannot be acted upon by ITTF because they do not act on any direct input from the national bodies which is handled by the committees.
The defect reports are only a matter for maintenance within JCT1/SC34 to handle and can after a possible accept/approve lead to improvements in e newer version or errata published with the standard.

hAl |

Comments are closed