Looks like only the first one still appears in the official CSD2
k
From: Yekaterina O'Neil
Sent: Wednesday, May 01, 2019 10:04 PM
To: Larry Golding (Myriad Consulting Inc) <
v-lgold@microsoft.com>; David Keaton <
dmk@dmk.com>;
sarif@lists.oasis-open.org Subject: RE: [sarif] CSD 2 update
-
Section 3.20.21, NOTE: This is import ance in compliance scenarios, where, for example, a corporate policy might require that a project s
entire code base be analyzed with a specified set of rules. -> NOTE: This is import ant in compliance scenarios, where, for example, a corporate policy might require that a project s entire code
base be analyzed with a specified set of rules.
-
Section 3.57.4, If the condition described by the notification object is relevant to one or more locations, the notification object MAY contain a property named locations whose value is an array
of zero of zero or more unique ( 3.7.3) location objects ( 3.27) that identify those locations.
-
3.31.3
" fullyQualifiedName property
k
From:
sarif@lists.oasis-open.org [ mailto:
sarif@lists.oasis-open.org ]
On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Thursday, April 25, 2019 10:54 AM
To: Larry Golding (Myriad Consulting Inc) <
v-lgold@microsoft.com >; David Keaton <
dmk@dmk.com >;
sarif@lists.oasis-open.org Subject: RE: [sarif] CSD 2 update
I ve incorporated the l last of the Microsoft feedback and closed
Issue #392 :
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-6.docx Please look over the issue s summary comment for the list of normative changes and let me know immediately of any concerns.
I will now address the remaining open issues as quickly as I can.
Larry
From:
sarif@lists.oasis-open.org <
sarif@lists.oasis-open.org >
On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Tuesday, April 23, 2019 5:47 PM
To: David Keaton <
dmk@dmk.com >;
sarif@lists.oasis-open.org Subject: RE: [sarif] CSD 2 update
Importance: High
Thank you David!
Friends, remember that
Issue #392 contains a list of all the normative changes (mostly minor) resulting from the Microsoft feedback. Please take a look, and also look at the sequence of change drafts that include both these normative changes and many editorial changes (mostly
clarifications and expanded explanations of certain points):
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-1.docx https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-2.docx https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-3.docx https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-4.docx https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-392-Microsoft-feedback-5.docx ... because if any of these changes is of concern, it's important we know right away. Microsoft-feedback-6.docx, which covers the Conformance clauses and the appendices, will be available tomorrow.
As always, the provisional draft is up to date with what I ve done so far:
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ProvisionalDrafts/sarif-v2.0-csd02-provisional.docx and so is the HTML version:
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ProvisionalDrafts/sarif-v2.0-csd02-provisional.htm After the Microsoft feedback is fully incorporated, there are still 7 items in the issue list, plus incorporating the tail end of Jim s feedback. It will take another couple-to-few days, and then we ll go to the ballot.
Thanks for your continued efforts we are almost there!
Best regards,
Larry