Dear colleagues, we have worked on the new editor revision. It addresses various issues that have been discovered by TC members and programmers working on the implementation of the standard. This is a PR [1] to merge it into the master branch. Please review this PR before our next TC meeting on 2022-02-23. If you have comments, please mark them in your review or open a new issue. You can review the changes via the Files changed tab [2] or read the whole editor revision as rendered markdown [3]. In my opinion, all these changes are straight-forward and clarify parts of the standard. We will provide separate suggestions for the following issues that IMHO should be discussed by the TC: - Add conformance target CSAF SBOM matching system (
https://github.com/oasis-tcs/csaf/issues/429 ) - Enhance category semantics (
https://github.com/oasis-tcs/csaf/issues/426 ) - Clarify usage of version ranges (
https://github.com/oasis-tcs/csaf/issues/392 ) - Add VEX flags (
https://github.com/oasis-tcs/csaf/issues/390 ) - Add flags for product lifecycle (
https://github.com/oasis-tcs/csaf/issues/386 ) Please have a look at these issues and support the process with your opinion. Your feedback is very much welcome. Thank you! Stefan and Thomas [1]
https://github.com/oasis-tcs/csaf/pull/450 [2]
https://github.com/oasis-tcs/csaf/pull/450/files [3]
https://github.com/oasis-tcs/csaf/blob/editor-revision-2022-02-23/csaf_2.0/prose/csaf-v2-editor-draft.md Attachment: smime.p7s Description: S/MIME cryptographic signature