Capabilities live in PDFs and memory
What a registry can offer sits in a PDF refreshed a year ago and in two engineers’ heads. Partners make their first technical decisions before any reliable description exists.
Registry Manifest · Describe
Describe the registry you already run, once.
Registry Manifest is a portable metadata contract: one validated file that says what a registry holds, what it may answer, and under which policy, rendered into the standard formats catalogs and partners already read. It works as plain static files, without adopting anything else.
The live lab includes a static metadata publisher serving exactly this kind of output, on synthetic data.
The problem it solves
Nobody can use a registry they cannot see.
Before any data flows, partners need to know what a registry holds, what it may answer, and on what authority. That description is infrastructure in its own right.
Every catalog wants a different format
The national portal wants DCAT-AP, a standards body wants service descriptions, a partner wants schemas. Hand-maintaining each one guarantees they drift apart.
Metadata dies with the platform
Descriptions locked inside one product disappear at replatforming time. A registry’s public contract should outlive whichever software currently serves it.
How it works
One manifest in, every required format out.
One manifest
A reviewed metadata file describing datasets, entities, fields, policies, and evidence offerings. No server required.
Registry Manifest
- Validate the description
- Compile the model
- Render each standard
- Publish static files
Standard artifacts
DCAT-AP, BRegDCAT-AP, CPSV-AP, SHACL, JSON Schema, OGC API Records, and policy documents at well-known paths.
Worked scenario
An existing registry becomes legible without changing.
Write one description
A civil registration team writes a single metadata manifest: which datasets and entities exist, what each field means, which evidence the registry can offer, under which policy.
Validate and render
The manifest is validated, then rendered into DCAT-AP, SHACL, JSON Schema, and the other formats catalogs and partners expect. No hand-maintained copies.
Publish as static files
The output is a plain directory of files at well-known paths. Any web server can host it; harvesters and partners discover it; no new runtime is adopted.
Open by design
One open format, every standard partners ask for.
A registry’s public description should outlive whichever software currently serves it. Registry Manifest keeps that description in one open, reviewable file and renders the rest.
- Renders DCAT-AP, BRegDCAT-AP, CPSV-AP, SHACL, JSON Schema, OGC API Records, and policy documents from one description.
- Publishes as plain static files: any web server can host them, and there is no runtime to operate.
- Feeds the catalogs and harvesters that already exist; descriptions travel, records never do.
- The same manifest can later drive Registry Relay and Registry Notary, with no rework.
In the stack
Where Registry Manifest sits.
The answering point runs three checks on every request. Registry Manifest owns the middle one: the shared description that lets both sides agree on what the fields mean. Each product runs on its own; together they share one answering point.
For your technical team