Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Miscellaneous final cleanup for errata #568

Closed
dmk42 opened this issue Apr 11, 2023 · 4 comments
Closed

Miscellaneous final cleanup for errata #568

dmk42 opened this issue Apr 11, 2023 · 4 comments

Comments

@dmk42
Copy link
Contributor

dmk42 commented Apr 11, 2023

  • In the definition of opaque, fix reable --> readable. (Credit goes to Craig Schlaman for finding this.)
  • Change Luke Cartey's company from Semmle to Microsoft.
  • Put version before $schema in the examples to match the document's suggestion.
  • Enumerate both schemas explicitly under the artifacts section.
  • Change all references to the schema URLs to point to the official OASIS location instead of github.
  • Correct "artifact" in example K.3 to "artifacts".
  • Add the missing normative reference to ECMA-404.
  • Fix the broken link to the definition of the term artifact in the definition of the term result management system.
@dmk42 dmk42 changed the title Correct additional misspelling and update co-chair's company Miscellaneous final cleanup for errata May 16, 2023
@dmk42
Copy link
Contributor Author

dmk42 commented Jun 13, 2023

This issue now incorporates #571 , #577 , #578 , #589 , #592 , and #593 .

@KalleOlaviNiemitalo
Copy link

In https://www.oasis-open.org/committees/download.php/71149/errata_bundle_20230622.zip downloadable from https://www.oasis-open.org/committees/document.php?document_id=71149&wg_abbrev=sarif, the file sarif-v2.1.0-errata01-csd01.docx includes a heading:

2.15 Issue #568: Miscellaneous final cleanup

which shows the number of this issue #568, but the hyperlink instead points to issue #494.

@dmk42
Copy link
Contributor Author

dmk42 commented Aug 29, 2023

@KalleOlaviNiemitalo - thanks for catching this.

It turns out that the public comment period has passed and the TC made it an Approved Errata document that is in the publication process, so we can't fix it. Fortunately, it causes no damage.

Once the Approved Errata document is published, we will be closing any open issues that it addresses, including this one.

@dmk42
Copy link
Contributor Author

dmk42 commented Dec 19, 2023

As noted above, this issue is being closed because the Errata document has been published.

@dmk42 dmk42 closed this as completed Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants