Glossary

Use this page to look up unfamiliar terms. Product names are always in English, including on future translated pages.

BRegDCAT-AP: SEMIC profile of DCAT-AP for base registries. Registry Relay and Registry Manifest emit BRegDCAT-AP-shaped registry and data-service metadata.
CCCEV: Core Criterion and Core Evidence Vocabulary. Registry Manifest emits CCCEV-shaped requirement, evidence type, and evidence type list metadata. Registry Atlas consumes those lists as grouped evidence options. Registry Notary renders CCCEV-shaped JSON-LD for claim evaluation results. Media type: application/ld+json; profile="cccev".
claim evaluation: Registry Notary process that evaluates configured evidence rules against data from one or more source services and returns a structured claim result.
claim level: The evidence discipline these docs use for standards claims: implements, emits, maps_to, aligns_with, inspired_by, or compares_against. Defined fully in the standards register.
DCAT: Data Catalog Vocabulary. W3C recommendation. Registry Relay and Registry Manifest emit DCAT-shaped JSON-LD catalogs. Spell out on first use per page: “Data Catalog Vocabulary (DCAT)”.
CPSV-AP: Core Public Service Vocabulary Application Profile. Registry Manifest emits CPSV-AP service catalogue JSON-LD. Registry Atlas uses it as the public-service entry point for service-first discovery.
DPI: Digital Public Infrastructure. Shared, interoperable digital systems (identity, payments, data exchange) deployed at population scale to support public service delivery. These projects cover the registry-consultation slice of a DPI deployment. See DPI safeguards alignment.
DID: Decentralized Identifier. W3C DID Core 1.0. Registry Relay publishes a did:web document at /.well-known/did.json when provenance is enabled. Registry Notary parses did:jwk values for credential subjects.
disclosure profile: Registry Notary control over what the caller receives: Value (full value disclosed), Predicate (only true/false satisfaction), or Redacted (value fully hidden).
distributed custody: The architectural premise that each authority retains control of its own registry data. The registry stack provides the API surface for lawful exchange between authorities; it does not aggregate data into a central system. Equivalent terms include data sovereignty (Gaia-X, IDS, EU dataspaces vocabulary), subsidiarity (governance literature), and federated custody.
entity route: A Relay API route shaped around a domain resource such as household or individual, not around storage table identifiers.
evidence offering: Metadata entry that describes a verification capability and the access path a client uses to reach it. Can point to a Relay-native verification endpoint or to an external evidence service.
evidence claim: Registry Stack product term for a verifiable claim, attestation, credential claim, or status assertion that Registry Notary evaluates from configured sources.
evidence type list: CCCEV list of evidence types that satisfy a requirement. In Registry Manifest and Registry Atlas, one list is one grouped option; multiple lists on the same requirement are alternatives.
executable safeguards: Registry Stack product term for runtime-enforced safeguards: scoped routes, disclosure policy, audit events, machine-readable metadata, and other policy enforcement point behavior that can be checked by software.
historical docs: Older specs, implementation reviews, or pre-rename documents that remain useful evidence but are not current user guidance. Historical pages are visibly marked and linked only from the historical docs index.
interoperability: Commitment that every registry in the stack publishes its catalog, schemas, services, and policies in standards-shaped form (DCAT, BRegDCAT-AP, CPSV-AP, CCCEV, SHACL, JSON Schema, ODRL, OpenAPI, SD-JWT VC), so downstream systems integrate against stable contracts rather than per-deployment ones.
JSON-LD: JSON-based linked data format. W3C recommendation (JSON-LD 1.1). Used for catalog, policy, CCCEV render output, and provenance contexts.
metadata manifest: Portable metadata.yaml document (schema version registry-manifest/v1) that describes datasets, entities, fields, public services, forms, requirements, policies, and evidence offerings. Must not include Relay runtime bindings such as source paths, table names, or scopes.
minimized evidence: Registry Stack product term for an evidence response shaped by data minimization, selective disclosure, or verifiable attestation. The response can be narrower than the full source record when the configured use case supports that pattern.
ODRL: Open Digital Rights Language. W3C recommendation. Relay and Manifest emit ODRL Offer documents for dataset-scoped policies.
OGC API Records: Open Geospatial Consortium API specification for records. Relay exposes records endpoints behind the ogcapi-records feature flag. Manifest renders OGC Records item bodies.
PROV-O: W3C Provenance Ontology. Currently listed as design influence (inspired_by). Provenance-shaped concepts appear in audit fields and the claim provenance struct, but no PROV-O vocabulary terms are emitted as JSON-LD at reviewed commits.
registry stack: The six related projects: Registry Platform, Registry Relay, Registry Manifest, Registry Notary, Registry Atlas, and Registry Lab. Use lowercase when referring to the concept.
purpose-bound request: Registry Stack product term for a request that carries or is evaluated against purpose limitation, policy-based access control, or context-aware authorization. Relay records the Data-Purpose header in audit records where present.
Registry Atlas: Browser SPA with a Rust/WASM semantic analysis engine for inspecting published service catalogue, catalog, and registry discovery artifacts. Repo slug: registry-atlas.
Registry Lab: Compose-based runnable local demo that starts three Registry Relay instances, four Registry Notary instances, live Postgres and Zitadel services, a private OpenFn sidecar path, a static metadata publisher, and narrated clients. Repo slug: registry-lab.
Registry Manifest: Rust workspace for modeling, validating, and rendering standards-facing service, registry, form, and policy metadata without running Registry Relay. Provides a library (registry-manifest-core) and a CLI (registry-manifest-cli). Repo slug: registry-manifest.
Registry Platform: Shared Rust workspace for registry security and operational primitives, including auth helpers, OIDC verification, audit envelopes, HTTP security, outbound HTTP policy, crypto, SD-JWT VC helpers, and test fixtures. Repo slug: registry-platform.
Registry Relay: Config-driven Rust service that turns sensitive government tabular files and database tables into protected, read-only, domain-oriented consultation APIs. Repo slug: registry-relay.
Registry Notary: Standalone Rust service for claim evaluation, disclosure policy, credential issuance, and audit. Decoupled from Registry Relay application code by design, while sharing Registry Platform primitives. Repo slug: registry-notary.
registry-manifest/v1: Schema version string for portable metadata manifests.
reviewability: Commitment that every promise the stack makes is backed by an artifact a third party can inspect without trusting the operator’s word. Examples include the published DCAT catalog, the SHACL shapes, the ODRL policy documents, the audit envelope schema, the JWKS public key endpoint, and the credential profile configuration. Registry Atlas implements the inspection workflow.
runtime binding: Relay configuration that connects logical manifest concepts to actual files, database tables, scopes, and backend credentials. Lives in Relay config, not in the manifest.
safeguards: Commitment that every exchange the stack mediates is authorized, scoped, and audited. Concretely: authentication by API key or OIDC; scope-checked routes; per-claim disclosure control (value, predicate, or redacted); no write paths in v0; audit envelopes for every request that touches person-level data.
SD-JWT VC: Selective Disclosure JWT Verifiable Credential (IETF draft). Registry Notary issues SD-JWT VC credentials signed with EdDSA. Media type: application/dc+sd-jwt.
SHACL: Shapes Constraint Language. W3C recommendation. Relay and Manifest emit SHACL node shapes for entity validation.
SP DCI: Social Protection Digital Convergence Initiative. Relay exposes an SP DCI adapter behind the spdci-api-standards feature flag. Registry Notary ships an HTTP source connector that maps SP DCI search responses into claim evaluation inputs.
static publication bundle: Manifest-generated directory containing catalog.json, dcat.jsonld, cpsv-ap.jsonld, shacl.jsonld, entity and form JSON Schemas, evidence offering JSON, and policy JSON-LD. Can be hosted as static files without running Registry Relay.
standards-shaped metadata: Registry Stack product term for machine-readable metadata emitted through formats such as DCAT, CPSV-AP, CCCEV, SHACL, JSON Schema, ODRL, OpenAPI, and OGC API Records.

Style notes

Product names (Registry Platform, Registry Relay, Registry Manifest, Registry Notary, Registry Atlas, Registry Lab) are always title case.
Repo slugs (registry-platform, registry-relay, registry-manifest, registry-notary, registry-atlas, registry-lab) are always lowercase and monospace.
Legacy underscore forms (registry_relay) and old repo names (decentralized-evidence-demo) appear only in historical pages or rename_status fields. Do not use them in prose on current pages.
Spell out standards acronyms on first use per page. The glossary provides a reference but does not replace per-page first-use expansion.