-
The current schema contains a restriction on the semantics of version identifiers that is not refelcted in the pattern and IMO is not beneficial to the producers and consumers.
```json
"version_t"…
-
It is not conclusive to me why we allow multiple `full_product_names` in `product_tree/relationships`. One `relationship` element links two products and may produce one new product name and identifier…
tolim updated
3 years ago
-
The OAXAL entry for projects looks correct but the displayed view wraps all the words into a stack. Maybe word wrapping caused by the graphic? See if there is a way to fix it.
Also CSAF, UBL.
-
Hello,
I use the API to retrieve information from an advisory by parsing the "summary" section of the json output.
My problem is _sometimes_ I don't have enough information in this section beca…
-
JSON schema mechanics use description as meta information on the weaved in CSAF properties,
We have some same name properties in our CSAF language. One with at least 8 occrurences is description - …
-
# Time
Monday October 5th, 2020 7:00 AM Pacific
# Links
- Zoom link: https://auth0.zoom.us/j/96101652486?pwd=SXNJaE1yK1hGd0ZaRHJZQW1RZG4zdz09
The invite is also available on the [OpenSSF C…
-
The current version of `scores` doesn't reflect the relationship between the list of products and (CVSS-) scores correctly. I suggest the following changes:
- define an object which contains: "produ…
-
@tschmidtb51 suggests to revisit the CWE referencing in the CSAF. Should we allow place for the longer descriptions or should we stay with the CVRF v1.2 wa of clearly going for the CWE-ID matching the…
-
The schema should have an $id property.
"The $id property is a URI-reference that serves two purposes:
- It declares a unique identifier for the schema.
- It declares a base URI against which $ref…
-
The object "product_status" should have a least one property as stated in the specification of CVRF 1.2 (see CSAF-6.10-1).