You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using some fresh markdown boilerplate to fill in a best effort transcription of the
SARIF v2.1.0-os-errata-01 candidate prose.
We may want to refactor or change some "things" of the 2.1 era to ease future work (and reading):
reduce the linkage (there are approx. 1400 §#.#.# links for a tad more than 200 pages which makes on the average 7 such opaque links per page) and make more links have a "speaking" link text
externalize the JSON examples as example files (inside the /sarif-2.2/example/ folder)
explicitly name all artifacts on file level
rewrite tables with two columns as definition lists
migrate to two slot versioning (2.2) for the spec
...
The text was updated successfully, but these errors were encountered:
sthagen
changed the title
Provide a SARIF v2.2.0 Seed Prose by Transcribing the v2.1.0 Errata 01 Prose to Markdown
Provide a SARIF v2.2 Seed Prose by Transcribing the v2.1.0 Errata 01 Prose to Markdown
May 20, 2023
Work in progress at https://github.com/sthagen/oasis-tcs-sarif-spec/blob/versioned-spec-folders/sarif-2.2/prose/sarif-v2.2-editor-draft.md (in fork)
Using some fresh markdown boilerplate to fill in a best effort transcription of the
SARIF v2.1.0-os-errata-01 candidate prose.
We may want to refactor or change some "things" of the 2.1 era to ease future work (and reading):
§#.#.#
links for a tad more than 200 pages which makes on the average 7 such opaque links per page) and make more links have a "speaking" link text/sarif-2.2/example/
folder)The text was updated successfully, but these errors were encountered: