Dear colleagues, please find a new editor revision at
https://github.com/oasis-tcs/csaf/blob/editor-revision-2021-04-26/csaf_2.0/prose/csaf-v2-editor-draft.md This time it has only minor changes which also can be viewed in
https://github.com/oasis-tcs/csaf/pull/238/files Based on the discussions and decisions in the last TC meeting: - We were able to resolve the interim-definition-issue (#226). To review the changes, please see
https://github.com/oasis-tcs/csaf/pull/234/files - We were able to resolve the acknowledgments-organisations-issue (#227) @mprpic: Thanks for bringing that up and providing the PR. To review the changes, please see:
https://github.com/oasis-tcs/csaf/pull/228/files - We renamed the "type" properties to "categories" (#212). To review the changes, please see:
https://github.com/oasis-tcs/csaf/pull/230/files Please review the PRs (Call to action): - #233:
https://github.com/oasis-tcs/csaf/pull/233 Versioning This PR suggests 2 ways to implement versioning in CSAF documents. The first one is "integer versioning", the second one will provide an approach for "semantic versioning". The rules for the latter one are designed to help end users to determine whether a new comparison with their asset database is needed. - #236:
https://github.com/oasis-tcs/csaf/pull/236 Tests This PR suggests a number of tests. It consists of 3 parts: 1. Mandatory test (handled as errors): A failure in one of these tests render the document invalid. These checks implement rules from section 3 which could not be implemented in the JSON schema. 2. Optional test (handled as warnings): A failure in one of these tests does not render the document invalid. As they cover mostly bad practices an issuing party should check whether they failed them on purpose or accidentally 3. Informational test (handled as information): Not implemented yet. Suggestions available at
https://github.com/oasis-tcs/csaf/issues/195#issuecomment-827008177 - Other PRs might be provided during the next 36h ;-) Best regards, Thomas -- Thomas Schmidt