Back in March 2007 JTC1/SC34 issued the following statement:
Liaison Statement from JTC1/SC34 to OASIS ODF TC
Defects have been identified in ISO/IEC 26300 and defect reports will be submitted to the OASIS ODF TC.
SC 34 requests that the OASIS ODF TC respond to these defect reports in a timely fashion and publish errata in accordance with OASIS procedures.
SC 34 requests that the Project Editor of ISO/IEC 26300 submit draft technical corrigenda consistent with OASIS approved errata conforming to ISO requirements for SC 34 ballot.
However, a defect report was not submitted by SC34 until seven months later, when a formal defect report (N0942) was eventually submitted.
I’m pleased to report that the OASIS ODF TC has created and approved a response to this defect report. The official announcement is here.
You won’t find any substantive changes to the standard. The document mainly addresses trivial editorial errors. No implementation will need to change because of these errata. Some might argue that it is a complete and utter waste of time to make editorial changes to a standard when they can have no effect on implementations. And this is true, up to a point. But there is always the possibility that a minor grammatical or spelling error might, when the ODF standard is translated into another language, be transformed into a more substantive error. So, perfecting the text of a standard, even 4 years after publication, does serve a minor purpose and deserves proportionate attention.
Since several members of JTC1/SC34 have expressed a strong desire of keeping the OASIS and ISO/IEC versions of the ODF in sync, I’m sure they will be eager to turn this errata document into technical corrigenda for approval by SC34, now that OASIS has done what was asked of it, i.e., “published errata in accordance with OASIS procedures.” The ball is in their court now.