Hi David and Mike,
I'm attaching two documents here to assist with the editorial changes to publish your Errata for public review and planned adoption as "Approved Errata".
The editorial changes as we prepare this for publication (based on discussion and approval among the TC Editor(s) and OASIS Project Administration staff) should not trigger the need for additional TC review and approval. However, you and the TC may decide to hold another approval ballot if desired. So far, it appears that no change to any content is necessary, just formatting the documents as expected for OASIS publications.
First, instead of just sending a template, I found that it was very simple to go ahead and reformat the Errata list (https://www.oasis-open.org/committees/document.php?document_id=69397&wg_abbrev=sarif) as expected for an OASIS publication, with all front matter, page footers, etc. I believe that this correctly incorporates everything from the document approved by the TC, but I urge you to review it carefully. If you find that any changes are needed to correctly represent the approved document, please send me the updated document. The attached Errata list document is "sarif-v2.1.0-errata01-csd01.docx".
Second, I've set up the published OASIS Standard .DOCX file with the appropriate changes to the front pages, etc., so it can be marked with the Errata. Please apply the Errata changes, similar to the TC's approved document "SARIF Standard with Errata incorporated (w/change bars)" (https://www.oasis-open.org/committees/document.php?document_id=69398&wg_abbrev=sarif). (First turn on change tracking, of course.) The attached document for this is "sarif-v2.1.0-errata01-csd01-redlined.docx".
After you apply the Errata changes, please send me this document. It will be published as the "redlined" document, and I'll plan to use it to prepare the usual companion "complete" document (with all changes accepted).
Since the Errata publication must include the JSON schema files, you will need to decide on the naming of the files, since the approved JSON schema "SARIF Schema with Errata incorporated" (https://www.oasis-open.org/committees/document.php?document_id=69399&wg_abbrev=sarif) has a file name which is different from the file names used in all previous publications of SARIF v2.1.0. A correction to this file name (back to the expected "sarif-schema-2.1.0.json") would be considered a normal part of publication.Â
I'm looking forward to working with you to publish the Errata and initiate the public review.
Best regards,
Paul
-- I'm attaching two documents here to assist with the editorial changes to publish your Errata for public review and planned adoption as "Approved Errata".
The editorial changes as we prepare this for publication (based on discussion and approval among the TC Editor(s) and OASIS Project Administration staff) should not trigger the need for additional TC review and approval. However, you and the TC may decide to hold another approval ballot if desired. So far, it appears that no change to any content is necessary, just formatting the documents as expected for OASIS publications.
First, instead of just sending a template, I found that it was very simple to go ahead and reformat the Errata list (https://www.oasis-open.org/committees/document.php?document_id=69397&wg_abbrev=sarif) as expected for an OASIS publication, with all front matter, page footers, etc. I believe that this correctly incorporates everything from the document approved by the TC, but I urge you to review it carefully. If you find that any changes are needed to correctly represent the approved document, please send me the updated document. The attached Errata list document is "sarif-v2.1.0-errata01-csd01.docx".
Second, I've set up the published OASIS Standard .DOCX file with the appropriate changes to the front pages, etc., so it can be marked with the Errata. Please apply the Errata changes, similar to the TC's approved document "SARIF Standard with Errata incorporated (w/change bars)" (https://www.oasis-open.org/committees/document.php?document_id=69398&wg_abbrev=sarif). (First turn on change tracking, of course.) The attached document for this is "sarif-v2.1.0-errata01-csd01-redlined.docx".
After you apply the Errata changes, please send me this document. It will be published as the "redlined" document, and I'll plan to use it to prepare the usual companion "complete" document (with all changes accepted).
Since the Errata publication must include the JSON schema files, you will need to decide on the naming of the files, since the approved JSON schema "SARIF Schema with Errata incorporated" (https://www.oasis-open.org/committees/document.php?document_id=69399&wg_abbrev=sarif) has a file name which is different from the file names used in all previous publications of SARIF v2.1.0. A correction to this file name (back to the expected "sarif-schema-2.1.0.json") would be considered a normal part of publication.Â
I'm looking forward to working with you to publish the Errata and initiate the public review.
Best regards,
Paul
|