dita — archive

[Mary McRae]

Hi Paul et al, The only errata allowed by the OASIS TC Process is one that has been created and approved by the TC, submitted for a 15-day public review, and then reapproved by the TC and then associated with the relevant OASIS Standard. Note that our rules allow only non-substantive changes to be incorporated into errata. It sounds like what the TC has instead decided is to create, in effect, an issues list with suggested resolutions that will be incorporated into a future release. Some TCs do choose to post their issues lists to docs.oasis-open.org so that there is a persistent "latest-version" URI as well as version-specific URIs for historical reference. The TC can also create a v1.1.1 and approve it as a Committee Draft, and then continue to add corrections and reapprove. I'm not sure what the final intent of the TC is - that at some point an official errata for v1.1 will be issued, that a v1.1.1 will be submitted for OS approval, or that the changes will be incorporated in the next release (v1.2?) There is nothing to prevent the TC from creating a heading on the existing public page entitled "Errata" and noting such documents and having that document (or any other TC approved document - that is, anything that has reached Committee Draft status) uploaded to docs.oasis-open.org. There is also no problem in creating that Errata document, approving it by the committee as a CD, and then continuing to update it rather than submitting for public review until such time as the TC feels they've gotten through most of the flaws (our process requires a six-month period between errata releases). I'm ready and willing to help - I just need to know exactly how the TC wants to proceed. Regards, Mary