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
Most predicates in the in-toto/attestation namespace already follow this convention for the predicateTypes, but we have two that were defined before we introduced this convention and don't:
My recommendation for SCAI is to remove the "attribute-report" piece since it somehow implies that there may be other subtypes of SCAI, and we don't currently support predicate subtypes. This may break existing tooling (mostly in-toto/scai-demos), and we may need to bump the predicate version number.
My suggestion for vuln may be to update the predicate name to vulns.md since that won't break current tools.
Any other thoughts? If this looks good, I'll open a PR to make the relevant changes.
The text was updated successfully, but these errors were encountered:
We recently introduced the notion of the predicate name, which we use in a couple ways: as a hint in the envelope mediaType, and in the
predicateType
URI for predicates in the in-toto/attestation namespace (see step 4).Most predicates in the in-toto/attestation namespace already follow this convention for the predicateTypes, but we have two that were defined before we introduced this convention and don't:
How should we resolve these two cases?
My recommendation for SCAI is to remove the "attribute-report" piece since it somehow implies that there may be other subtypes of SCAI, and we don't currently support predicate subtypes. This may break existing tooling (mostly in-toto/scai-demos), and we may need to bump the predicate version number.
My suggestion for vuln may be to update the predicate name to
vulns.md
since that won't break current tools.Any other thoughts? If this looks good, I'll open a PR to make the relevant changes.
The text was updated successfully, but these errors were encountered: