Ok, a new change draft is available that covers both #86 and #95: Documents/ChangeDrafts/Active/sarif-v2.0-issues-86-95-url-normalization-executableLocation.docx Michael and James have expressed particular interest in this change. NOTE: As part of this change, I have at editorial discretion changed the name and type of the property rule.helpUri , which held a string value. It now holds a fileLocation object, and I’ve changed its name to rule.helpLocation. This was AFAIK the only remaining URI-valued property which held a URI as a string instead of as a fileLocation . If I find any others, I’ll fix them too. Larry From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Comcast) Sent: Tuesday, March 20, 2018 9:05 AM To:
sarif@lists.oasis-open.org Cc: 'Michael Fanning' <
Michael.Fanning@microsoft.com>; 'James A. Kupsch' <
kupsch@cs.wisc.edu> Subject: RE: [sarif] Change draft for #95: invocation.fileName => invocation.executableLocation Please don’t review this draft. Michael and James suggested a better way to organize this material. With their suggestions, it becomes natural to combine these two issues into a single change draft: Issue #95 : “invocation.fileName => invocation.executableLocation” Issue #86 : “Add path normalization guidance for URLs” So I’m going to move the existing change draft to the “Rejected” folder and start a new one that covers both issues. Thanks, Larry From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org > On Behalf Of Larry Golding (Comcast) Sent: Sunday, March 18, 2018 3:46 PM To:
sarif@lists.oasis-open.org Subject: [sarif] Change draft for #95: invocation.fileName => invocation.executableLocation I pushed a change draft for Issue #95 , “invocation.fileName => invocation.executableLocation”: Documents/ChangeDrafts/Active/sarif-v2.0-issue-95-invocation-executableLocation.docx I’ll move for its adopt this change at the next TC meeting. Thanks, Larry