Describe registries
Describe registries is how a registry owner publishes a machine-readable description of what
they offer, datasets, schemas, services, policies, and evidence offerings, before any
integration is written. The primary implementation is
Registry Manifest, which compiles a portable
metadata.yaml manifest into catalogs, schemas, service descriptions, policy documents,
evidence offerings, and an index.json discovery entry point.
What it produces
Section titled “What it produces”Registry Manifest renders:
- A DCAT/BregDCAT-AP catalog and dataset entries.
- CPSV-AP service description.
- CCCEV evidence offering definitions.
- SHACL and JSON Schema shape files.
- ODRL policy documents.
- An
index.jsondiscovery entry point consumed by Registry Atlas.
Registry Relay can also serve Manifest-rendered metadata at runtime, filtered to the authenticated caller’s metadata scopes. Registry Manifest does not read registry records, open an HTTP listener, or grant credentials.
Primary project
Section titled “Primary project”Registry Manifest: renderer, validation, and profile fixture model.
How to use it
Section titled “How to use it”Start with the manifest schema reference.
To publish, run the Manifest compiler against your metadata.yaml.
To inspect the output, use Registry Atlas.
To serve runtime metadata to authenticated callers, configure Registry Relay.
Example: a property registry run by a national land authority publishes a manifest declaring its
parcels dataset, the parcel-identifier field, the freshness window, and the evidence offerings
available against it.
Related docs
Section titled “Related docs”- Publishing pipeline: portable metadata and runtime metadata split.
- Registry Manifest overview: renderer, validation, and profile fixture model.
- Registry Manifest reference: manifest schema and publish output artifacts.
- Registry Relay overview: runtime metadata publication through protected services.
- Standards reference: standards named by the metadata surface.