Repository navigation
Labels
EpicLarge-scale issues that represent multi-step implementations, used to thematically link other issuesLarge-scale issues that represent multi-step implementations, used to thematically link other issuesenhancementNew feature or requestNew feature or requestintegrationRelated to integration of SSVC into another framework or systemRelated to integration of SSVC into another framework or systemtech/backendBack-end tools, code, infrastructureBack-end tools, code, infrastructuretech/dataData implementation (content of /data, data object instances, etc.)Data implementation (content of /data, data object instances, etc.)
Description
We're collaborating with the CSAF folks to integrate SSVC representation into CSAF. This is a parent issue to organize that effort. Please add sub-issues as needed. (Or comment in existing issues to get our attention so we can link them.)
In the near future, we'll be organizing these as:
Integration Blockers
- Clarify distinction between private and extension namespaces #780
- Add a minimalist selection object #820
- ABNF suggestions #858
Tip
Use the integration-blocker label to denote these
Nice-to-haves
The remainder of the sub-issues below are in the "nice-to-have" category.
Reacted by j---
Metadata
Metadata
Assignees
Labels
EpicLarge-scale issues that represent multi-step implementations, used to thematically link other issuesLarge-scale issues that represent multi-step implementations, used to thematically link other issuesenhancementNew feature or requestNew feature or requestintegrationRelated to integration of SSVC into another framework or systemRelated to integration of SSVC into another framework or systemtech/backendBack-end tools, code, infrastructureBack-end tools, code, infrastructuretech/dataData implementation (content of /data, data object instances, etc.)Data implementation (content of /data, data object instances, etc.)
Activity
doctools.pyshould also generate outcome group examples #739doctools.pyshould also generate outcome group examples #739namespaceentries should point to a url of a JSON list of decision points in that namespace #75213 remaining items
$schemaand$idmissing #901tschmidtb51 commentedon Aug 25, 2025
In CSAF, the transition to SSVC v2 is now tracked as oasis-tcs/csaf#1152.
description#903minLengthin JSON schema #904target_idsshould be unique #905invalid#907minLengthin JSON schema #904ahouseholder commentedon Sep 15, 2025
Removing this mega-issue from the 2025-09 milestone because it contains child issues that we're not going to get resolved for this release. The child issues we have resolved will of course be included, so it's not that we're not "integrating with CSAF" in the forthcoming release, it's just that we haven't completed everything listed here.