[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sarif] CSD 2 update
Great, thanks! k From: Larry Golding (Myriad Consulting Inc) [mailto:v-lgold@microsoft.com]
Thanks, Yekaterina. I am tracking post-CSD.2-ballot editorial changes in
https://github.com/oasis-tcs/sarif-spec/issues/405. Larry From: Yekaterina O'Neil <katrina@microfocus.com>
Looks like only the first one still appears in the official CSD2 k From: Yekaterina O'Neil
-
Section 3.20.21, âNOTE: This is importance 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 important 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) Iâve incorporated the l last of the Microsoft feedback and closed
Issue #392: 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) 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): ... 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: â and so is the HTML version: 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 -----Original Message----- The editors have worked through the input they received, and generated issues to track what isn't already in the draft. Thanks for all your helpful feedback! The current plan is to finish updating the draft and start the e-ballot
for Committee Specification Draft 2 within the next week. The e-ballot will last 7 days and will be a formal OASIS Full Majority Ballot (meaning we need 5 yes votes out of the 9 voting members, even if someone abstains). David --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://nam06.safelinks.protection.outlook.com/?url="">
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]