A result as a VSA writes it: one of the SLSA-defined results SlsaResult lists, or one of the issuer’s own, which never starts with SLSA._
URI: xsd:string
| Property |
Value |
| Regex Pattern |
`^(SLSA_BUILD_LEVEL_(UNEVALUATED |
- An issuer’s own result, such as an organization’s ORG_SOURCE_ property, is printable ASCII with no spaces and does not start with SLSA_ in any letter case, so that it cannot pass for an SLSA result.
- It names the base its typeof already gives, because the SQL generator reads base alone and reports a type without one.
- The pattern lists the values of SlsaResult that start with SLSA_ and then admits any other value that does not, written without a lookahead, which SHACL’s regular expressions lack. One type in place of any_of over the enum and a pattern keeps the OWL output valid, since gen-owl makes the enum a class.
- verified_levels and verified_level repeat the pattern through a YAML anchor, because gen-pydantic checks a slot’s pattern but not its type’s.
- tests/test_schema_rules.py checks the pattern against SlsaResult.
| Mapping Type |
Mapped Value |
| self |
slsa:SlsaResultValue |
| native |
slsa:SlsaResultValue |