Skip to content
Registry StackDocsDocumentation preview

ITB and SEMIC evidence

View as Markdown

This page summarizes selected external validation evidence for Registry Manifest and Registry Notary. It is not a certification statement, and it does not claim every generated artifact or every runtime deployment has been tested.

ProductArtifactExternal checkResultBoundary
Registry ManifestGenerated JSON Schema Draft 2020-12 files for the civil-registration fixtureITB JSON validator, any domain, with the Draft 2020-12 metaschema embeddedSUCCESS, 0 errors, 0 warningsSelected generated schemas only
Registry ManifestGenerated DCAT JSON-LD for the civil-registration fixturePublic ITB/SEMIC SHACL validator, dcatap.3_0_1_base0SUCCESS, 0 errors, 0 warningsSelected DCAT artifact only
Registry ManifestGenerated BRegDCAT-AP JSON-LD for the civil-registration fixturePublic ITB/SEMIC SHACL validator, bregdcatap.2_0_0 and bregdcatap.2_1_0SUCCESS, 0 errors, 2 warnings per profilePasses with warnings; see the owning Manifest PR
Registry NotaryGenerated OpenAPI 3.1 documentITB JSON validator against the OpenAPI 3.1 schemaSUCCESS, 0 errors, 0 warningsOpenAPI hygiene only, not runtime GITB coverage
  • Validator outputs and the warning boundary are recorded in registry-manifest PR #27.
  • Registry Notary records the protected discovery policy and GITB runtime-suite target in jeremi/registry-notary#245.
  • Registry Manifest documents the BRegDCAT warning boundary in the Manifest ITB and SEMIC validation guide.
  • Registry Notary runtime behavior has not been validated by a GITB scenario suite.
  • Registry Notary OpenAPI validation proves that the generated API document is structurally valid; it does not prove authenticated evaluation, credential issuance, federation replay handling, or SD-JWT VC verification.
  • Registry Manifest BRegDCAT-AP output passes the selected public validators with warnings. The warning profiles differ on dcat:themeTaxonomy, so the warnings are documented rather than hidden.
  • The evidence applies to selected fixtures and profiles, not to every possible operator manifest or deployment.

This evidence supports statements that the published examples validate against the SEMIC validators with zero errors; it does not support claims of certification, official validation, or full conformance.