You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we define a separator for tags, we can allow tool producers to serialized a hierarchized set of tags. For example, by using a forward slash, a user could tag a result with multiple CWE designations:
["CWE/973", "CWE/435"]
Similarly, a SARIF converter that transforms Polyspace Verifier output to SARIF might preserve validation-relevant annotations produced by its abstract interpretation engine like so:
"Polyspace/Dead"
"Polyspace/Open"
etc.
The text was updated successfully, but these errors were encountered:
ghost
pushed a commit
that referenced
this issue
Oct 20, 2017
If we define a separator for tags, we can allow tool producers to serialized a hierarchized set of tags. For example, by using a forward slash, a user could tag a result with multiple CWE designations:
["CWE/973", "CWE/435"]
Similarly, a SARIF converter that transforms Polyspace Verifier output to SARIF might preserve validation-relevant annotations produced by its abstract interpretation engine like so:
"Polyspace/Dead"
"Polyspace/Open"
etc.
The text was updated successfully, but these errors were encountered: