Digital Registries Building Block Specification
Specification metadata
Section titled “Specification metadata”| Field | Value |
|---|---|
| Version | 3.0.0-alpha.2 |
| Release date | Not assigned |
| Short description | Defines the draft Registry Core, service discovery, and independently selected Consultation and Write operations. |
| Specification URN | govstack:spec:bb:registries |
| Owner group | govstack:wg:registries-registration |
| Canonical URL | https://specs.govstack.global/registries/ |
| Repository | https://github.com/GovStackWorkingGroup/bb-digital-registries |
| Extensions | None declared |
Capabilities
Section titled “Capabilities”Registry Service Discovery
Section titled “Registry Service Discovery”Key: registry-discovery
An adopter identifies a Registry’s responsible authority, authoritative scope, and available service contracts.
Authoritative Registry Services
Section titled “Authoritative Registry Services”Key: registry-services
An authorised consumer uses the Registry’s declared services within its responsible authority’s scope and access policy.
Authors
Section titled “Authors”| Name | Role | URN |
|---|---|---|
| Sebastian Leidig | Author | govstack:person:sebastian-leidig |
| Jeremi Joslin | Author | govstack:person:jeremi-joslin |
| David Higgins | Author | govstack:person:david-higgins |
Version 3.0.0-alpha.2, an authoring draft. The specification inherits
govstack-cfr-2.1.0. Its requirements remain DRAFT and do not establish an
implementation conformance or certification claim.
The Digital Registries Building Block defines interoperable behaviour for software that maintains authoritative records about persons, organisations, places, assets, or events. It specifies Registry identity, authority, metadata, discovery, stable Record references, and permitted representations without prescribing a database product, administrative user interface, storage model, deployment topology, or domain data model.
The target conformance model combines Registry Core with at least one declared
Registry operation. This draft defines six independently selectable Consultation options and four
Write options: direct creation, direct update, direct named transition, and
approval-based change requests. No particular operation is universal. A deployment
can offer direct writes, approval-based writes, both, or only declared reads.
The other six API families remain informative roadmap material until their
requirements, contracts, and tests are defined.
Business-outcome capabilities in metadata.yml are informative and are realised
by the functionalities; operation choices are declared by option key.
The six read operations share a Record representation and bounded pagination over explicit logical Collections. Operations can separately declare conditional reads, field selection, complete traversal, snapshot traversal, recorded-time, effective-time, or purpose binding; caller capability discovery can also be offered as supporting metadata. The same Registry API can expose read, direct Write, Change Request, and asynchronous Operation resources while keeping their grants and selection independent. The HTTP binding supplies Registry, Collection, schema, capability, and selectable feature declarations through its versioned contract. Source history, revision, lifecycle, recording-time, and effective-time metadata remain conditional on the source and the selected capability or feature.
Reading guide
Section titled “Reading guide”- Architects and procurement teams: read the overview and scope for purpose, boundaries, draft maturity, and conformance conditions.
- Implementers: use Discover Registry Services for metadata and discovery, then Provide Registry Services for the Record model, Consultation, Write, and workflows.
- API consumers: use the unified Registry API reference. The API examples illustrate deployment choices and add no requirements to the shared contract.
- Assessors: use the verification procedures, Write verification, and the applicability declarations in the functionality files.
Source and contributions
Section titled “Source and contributions”The Digital Registries repository contains the source, contributor instructions, validation tools, and Git history.
Attribution
Section titled “Attribution”Current coordinating authors are Sebastian Leidig, Jeremi Joslin, and David Higgins. The repository release history retains historical authors, coordinators, editors, reviewers, and changes.
The repository licence applies to the specification source.
Unofficial preview · 3.0.0-alpha.2 · Source revision 2350fdf8.
Content snapshot 5e66af7b9724.