OASIS Static Analysis Results Interchange Format (SARIF) TC

I pushed a change draft for the following two closely related issues:   Issue #63 : Clarify that the keys in the run.files dictionary must be distinct when normalized Issue #64 : run.files keys can collide if specified by relative URLs   Please take a look at those issues, especially the solution described in Issue #64, before reading the change draft, which is here:   Documents/ChangeDrafts/Active/sarif-v2.0-issue-29-rule-configuration.docx   I added these items to the Agenda that’s checked into the repo, and I’ll move for their adoption at the next TC meeting.   Thanks, Larry

If you haven’t yet read this draft, you can ignore this mail.   I made a small mistake in this draft. The draft correctly states that the “uri base id prefix” is mandatory if it’s needed to avoid a file dictionary key collision. But the language of the draft effectively prohibits the prefix if there are no collisions. There’s nothing inherently wrong with that, but it’s contrary to what Michael and I agreed on and intended to propose. We intended to allow the prefix, even if it wasn’t necessary, to accommodate SARIF producers that didn’t want to take the trouble to look for collisions before deciding whether to include the prefix.   You can read the draft as it is; just be aware that I’m going to update it to fix that problem.   Larry   From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Comcast) Sent: Saturday, March 10, 2018 11:28 AM To: sarif@lists.oasis-open.org Subject: [sarif] Change draft for #63 and #64: files dictionary property names   I pushed a change draft for the following two closely related issues:   Issue #63 : Clarify that the keys in the run.files dictionary must be distinct when normalized Issue #64 : run.files keys can collide if specified by relative URLs   Please take a look at those issues, especially the solution described in Issue #64, before reading the change draft, which is here:   Documents/ChangeDrafts/Active/sarif-v2.0-issue-29-rule-configuration.docx   I added these items to the Agenda that’s checked into the repo, and I’ll move for their adoption at the next TC meeting.   Thanks, Larry

I corrected the section that explains when the “uri base id prefix” is required and pushed a revision to the change draft. The change draft is here ( NOT at the link I provided below, which was a copy-paste error):   Documents/ChangeDrafts/Active/sarif-v2.0-issues-63-64-distinct-run-file-keys.docx   Unfortunately, to make this precise, I had to essentially rewrite §3.11.11.2, “Property names”. Please do read it carefully.   Thanks, Larry   From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Comcast) Sent: Sunday, March 11, 2018 5:56 PM To: sarif@lists.oasis-open.org Subject: RE: [sarif] Change draft for #63 and #64: files dictionary property names   If you haven’t yet read this draft, you can ignore this mail.   I made a small mistake in this draft. The draft correctly states that the “uri base id prefix” is mandatory if it’s needed to avoid a file dictionary key collision. But the language of the draft effectively prohibits the prefix if there are no collisions. There’s nothing inherently wrong with that, but it’s contrary to what Michael and I agreed on and intended to propose. We intended to allow the prefix, even if it wasn’t necessary, to accommodate SARIF producers that didn’t want to take the trouble to look for collisions before deciding whether to include the prefix.   You can read the draft as it is; just be aware that I’m going to update it to fix that problem.   Larry   From: sarif@lists.oasis-open.org < sarif@lists.oasis-open.org > On Behalf Of Larry Golding (Comcast) Sent: Saturday, March 10, 2018 11:28 AM To: sarif@lists.oasis-open.org Subject: [sarif] Change draft for #63 and #64: files dictionary property names   I pushed a change draft for the following two closely related issues:   Issue #63 : Clarify that the keys in the run.files dictionary must be distinct when normalized Issue #64 : run.files keys can collide if specified by relative URLs   Please take a look at those issues, especially the solution described in Issue #64, before reading the change draft, which is here:   Documents/ChangeDrafts/Active/sarif-v2.0-issue-29-rule-configuration.docx   I added these items to the Agenda that’s checked into the repo, and I’ll move for their adoption at the next TC meeting.   Thanks, Larry