From this code and below (defining 1st category, in JSON called "predicates" information is not exposed in human readable format).
In particular, let's take following predicates - some of them do not have bigger descriptions, but some have:
The ones which do not have (example):
"value": "abusive-content"
"description": "Abusive Content.",
"value": "information-gathering"
"description": "Information Gathering.",
While some predicates (1st classification category) has longer texts, which are not exposed in the human readable table):
"value": "malicious-code"
"description": "Software that is intentionally included or inserted in a system for a harmful purpose. A user interaction is normally necessary to activate the code.",
Suggestion - to modify https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force/blob/master/working_copy/humanv1.md - probably provide additional table for only predicates, or provide extra lines for each 1st category.
From this code and below (defining 1st category, in JSON called "predicates" information is not exposed in human readable format).
Reference-Security-Incident-Taxonomy-Task-Force/working_copy/machinev1
Line 254 in 034cea9
In particular, let's take following predicates - some of them do not have bigger descriptions, but some have:
The ones which do not have (example):
"value": "abusive-content"
"description": "Abusive Content.",
"value": "information-gathering"
"description": "Information Gathering.",
While some predicates (1st classification category) has longer texts, which are not exposed in the human readable table):
"value": "malicious-code"
"description": "Software that is intentionally included or inserted in a system for a harmful purpose. A user interaction is normally necessary to activate the code.",
Suggestion - to modify https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force/blob/master/working_copy/humanv1.md - probably provide additional table for only predicates, or provide extra lines for each 1st category.