Closed sthagen closed 3 years ago
/acknowledgment_t/description --> /acknowledgment_t/summary
/references_t/[]/description --> /references_t/[]/summary
/document/tracking/revision_history/[]/description --> /document/tracking/revision_history/[]/summary
/product_tree/product_groups/[]/description --> /product_tree/product_groups/[]/summary
/vulnerabilities/[]/involvements/[]/description --> /vulnerabilities/[]/involvements/[]/summary
/vulnerabilities/[]/remediations/description --> /vulnerabilities/[]/remediations/details
/vulnerabilities/[]/remediations/restart_required/description --> /vulnerabilities/[]/remediations/restart_required/details
/vulnerabilities/[]/threats/description --> /vulnerabilities/[]/threats/details
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 - which for itself is not very specific. Proposal is to replace these occurences to make the CSAF vs. JSON Schema terms separation more clear.
We have (triplets of TO_BE_REWORDED, title, description) currently:
TLDR summary proposed changes in pseudo path notation
/acknowledgment_t/description
-->/acknowledgment_t/details
/references_t/[]/description
-->/references_t/[]/details
/document/tracking/revision_history/[]/description
-->/document/tracking/revision_history/[]/details
/product_tree/product_groups/[]/description
-->/product_tree/product_groups/[]/details
/vulnerabilities/[]/description
-->/vulnerabilities/[]/details
/vulnerabilities/[]/remediations/description
-->/vulnerabilities/[]/remediations/discussion
/vulnerabilities/[]/remediations/restart_required/description
-->/vulnerabilities/[]/remediations/restart_required/details
/vulnerabilities/[]/threats/description
-->/vulnerabilities/[]/threats/discussion
Detailed proposal to rename as follows (title and description maintained to ease comparison with above):