ITB and SEMIC evidence
This page summarizes selected external validation evidence for Registry Manifest. It is not a certification statement, and it does not claim every generated artifact or every runtime deployment has been tested.
Registry Relay and Evidence Gateway have no external ITB or SEMIC evidence recorded yet.
Summary
Section titled “Summary”| Product | Artifact | External check | Result | Boundary |
|---|---|---|---|---|
| Registry Manifest | Generated JSON Schema Draft 2020-12 files for the civil-registration fixture | ITB JSON validator, any domain, with the Draft 2020-12 metaschema embedded | SUCCESS, 0 errors, 0 warnings | Selected generated schemas only |
| Registry Manifest | Generated DCAT JSON-LD for the civil-registration fixture | Public ITB/SEMIC SHACL validator, dcatap.3_0_1_base0 | SUCCESS, 0 errors, 0 warnings | Selected DCAT artifact only |
| Registry Manifest | Generated BRegDCAT-AP JSON-LD for the civil-registration fixture | Public ITB/SEMIC SHACL validator, bregdcatap.2_0_0 and bregdcatap.2_1_0 | SUCCESS, 0 errors, 2 warnings per profile | Passes with warnings; see the owning Manifest PR |
Source links
Section titled “Source links”- Validator outputs and the warning boundary are recorded in registry-manifest PR #27.
- Registry Manifest documents the BRegDCAT warning boundary in the Manifest ITB and SEMIC validation guide.
What is not covered
Section titled “What is not covered”- No maintained runtime has been validated by a GITB scenario suite.
- 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.
Public wording
Section titled “Public wording”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.
- Review the standards register for the broader claim-level model.
- Review the contracts register for machine-readable surfaces and their owning repos.