Spelling #486

jsoref · 2021-02-28T09:44:42Z

This PR corrects misspellings identified by the check-spelling action.

The misspellings have been reported at jsoref@78057e0#commitcomment-47652525

The action reports that the changes in this PR would make it happy: jsoref@6a36cbf

Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Agendas/20180314.md

...ts/BallotDrafts/sarif-v2.1.0-final-e-ballot-1/sarif-external-property-file-schema-2.1.0.json

Documents/BallotDrafts/sarif-v2.1.0-final-e-ballot-1/sarif-v2.1.0-final.htm

jsoref · 2021-02-28T09:48:49Z

Documents/CommitteeSpecifications/2.1.0/sarif-v2.1.0-committee-specification.htm

@@ -19985,7 +19985,7 @@ <h3><a name="_Hlk7091462"></a><a name="_Toc13414331">3.38.14 taxa property</a></

 <p class=Code style='margin:0in;margin-bottom:.0001pt;background:#D9D9D9'><span
 style='color:black'>��������� &quot;name&quot;:
-&quot;SubstrPropogatesTaint&quot;,</span></p>
+&quot;SubstrPropagatesTaint&quot;,</span></p>


jsoref · 2021-02-28T09:50:36Z

README.md

@@ -9,7 +9,7 @@
 <div>
 <h3>Description</h3>

-<p>The purpose of the SARIF TC is to define a standard output format for static analysis tools, which will be called the Static Analysis Results Interchange Format (SARIF).  <a href="https://github.com/oasis-tcs/sarif-spec">This GitHub repository</a> supports development of the draft SARIF standard. Requests for modification should be made via <a href="https://github.com/oasis-tcs/sarif-spec/issues">Github Issues</a>.</p>
+<p>The purpose of the SARIF TC is to define a standard output format for static analysis tools, which will be called the Static Analysis Results Interchange Format (SARIF).  <a href="https://github.com/oasis-tcs/sarif-spec">This GitHub repository</a> supports development of the draft SARIF standard. Requests for modification should be made via <a href="https://github.com/oasis-tcs/sarif-spec/issues">GitHub Issues</a>.</p>


This is a brand

Please revert that change as that text is owned by OASIS (and not the TC) - we should separate such concerns from TC content.

Schemata/sarif-2.0.0-csd.2.beta.2018-10-10.json

meetings/sarif-minutes-20170920-meeting-2.html

meetings/sarif-minutes-20171011-meeting-4.html

EditorsReports/Editor's report 2018-12-12.md

michaelcfanning · 2021-09-15T14:15:12Z

@jsoref, we are finally getting around to looking at the PR, which I greatly appreciate. We will accept all corrections into a revision of SARIF 2.1 (which addresses all known errata). I will also accept all changes to our historical agenda reports, etc. I need to check into whether we can update definitive copies of things like the spec, those errors may need to remain (but will be corrected shortly in a versioned copy).

sthagen · 2022-07-19T18:57:48Z

@dmk42 @michaelcfanning I assume that this PR will not technically be merged but rather per the manual errata editing process already have been "woven" into the upcoming corrected version?

dmk42 · 2023-09-14T17:50:33Z

Many items in this PR are addressed in the Approved Errata document, which is in the queue to be published any day now.

There are other items that remain valid, and we should sweep them into SARIF v2.2.0.

jsoref · 2023-10-04T18:50:48Z

Sorry for the multiple force-pushes, I've rebased what's left of this branch. Note that this is naive rebase, it isn't applying the current version of the tooling to identify any additional errors.

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

sthagen

Thank you for investing the effort.
I propose to revert all changes on approved minutes and the README.md.
We can use this PR to apply the changes to the artifacts we standaradized in version 2.1.0 though.

Given that these are only few changes and the commit history of this PR is very noisy, I suggest we create a fresh focused PR on these latter artifacts only and close this PR without action.

sthagen · 2023-10-05T04:58:26Z

README.md

@@ -9,7 +9,7 @@
 <div>
 <h3>Description</h3>

-<p>The purpose of the SARIF TC is to define a standard output format for static analysis tools, which will be called the Static Analysis Results Interchange Format (SARIF).  <a href="https://github.com/oasis-tcs/sarif-spec">This GitHub repository</a> supports development of the draft SARIF standard. Requests for modification should be made via <a href="https://github.com/oasis-tcs/sarif-spec/issues">Github Issues</a>.</p>
+<p>The purpose of the SARIF TC is to define a standard output format for static analysis tools, which will be called the Static Analysis Results Interchange Format (SARIF).  <a href="https://github.com/oasis-tcs/sarif-spec">This GitHub repository</a> supports development of the draft SARIF standard. Requests for modification should be made via <a href="https://github.com/oasis-tcs/sarif-spec/issues">GitHub Issues</a>.</p>


Please revert that change as that text is owned by OASIS (and not the TC) - we should separate such concerns from TC content.

sthagen · 2023-10-05T04:59:13Z

README.md

@@ -38,5 +38,5 @@
 <div>

 <h3>Contact</h3>
-<p>Please send questions or comments about <a href="https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work">OASIS TC GitHub repositories</a> to <a href="mailto:robin@oasis-open.org">Robin Cover</a> and <a href="mailto:chet.ensign@oasis-open.org">Chet Ensign</a>.  For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the SARIF TC's <a href="https://www.oasis-open.org/committees/sarif/">home page</a>.</p>
+<p>Please send questions or comments about <a href="https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work">OASIS TC GitHub repositories</a> to <a href="mailto:robin@oasis-open.org">Robin Cover</a> and <a href="mailto:chet.ensign@oasis-open.org">Chet Ensign</a>.  For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the SARIF TC's <a href="https://www.oasis-open.org/committees/sarif/">home page</a>.</p>


This may also need reverting (to push upstream to OASIS)

sthagen · 2023-10-05T05:05:31Z

Documents/CommitteeSpecifications/2.1.0/sarif-external-property-file-schema-2.1.0.json

@@ -153,7 +153,7 @@
    },

    "addresses": {
-      "description": "Addresses that will be merged with with an external run.",
+      "description": "Addresses that will be merged with an external run.",


Please create a different PR for changes on published artifacts (on docs.oasis-open.org i.e. standards work products.

sthagen · 2023-10-05T05:05:41Z

Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json

@@ -2702,7 +2702,7 @@
      "properties": {

        "guid": {
-          "description": "A stable, unique identifer for the suprression in the form of a GUID.",
+          "description": "A stable, unique identifer for the suppression in the form of a GUID.",


Please create a different PR for changes on published artifacts (on docs.oasis-open.org i.e. standards work products.

sthagen · 2023-10-05T05:07:29Z

Schemata/sarif-external-property-file-schema-2.1.0.json

@@ -153,7 +153,7 @@
    },

    "addresses": {
-      "description": "Addresses that will be merged with with an external run.",
+      "description": "Addresses that will be merged with an external run.",


Please create a different PR for changes on published artifacts (on docs.oasis-open.org i.e. standards work products.

sthagen · 2023-10-05T05:11:29Z

meeting_minutes/221110_SARIF_TC_70.md

@@ -105,14 +105,14 @@ None noted

 ## 4.4 Discuss end-to-end results management

-* Mary: Presented a video from Chris Meyer demonstrating two changes to the Visual Studio SARIF Viewer targeting the interop with Github advanced security features
+* Mary: Presented a video from Chris Meyer demonstrating two changes to the Visual Studio SARIF Viewer targeting the interop with GitHub advanced security features
