Skip to content
Registry stack docs v0 · draft
Search

Inspect published artifacts

Inspect published artifacts is how a reviewer or integrator reads a registry’s published metadata (catalogs, schemas, policies, evidence offerings) before any data sharing agreement is signed or any client code is written. The primary supporting tool is Registry Atlas, a browser application and proxy that fetches published catalogs and related metadata, classifies the artifacts, and runs strict capability queries over accepted machine terms.

Registry Atlas supports the Describe registries loop: Registry Manifest renders the artifacts, Registry Relay can publish scoped runtime metadata, and Atlas inspects what a registry actually emits. Atlas does not infer intent from natural language in v0.1, and the governance workflow for reviewed capability assertions is not yet implemented.

What it does

Section titled “What it does”

Registry Atlas:

  • Fetches a published index.json or catalog URL and classifies the linked artifacts by type.
  • Runs strict capability queries against accepted DCAT, CPSV-AP, CCCEV, SHACL, JSON Schema, OpenAPI, and OGC Records terms.
  • Displays the results so a reviewer can confirm what a registry actually advertises before writing an integration.

Atlas is a read-only inspection tool; it does not modify artifacts or write back to any service.

Primary project

Section titled “Primary project”

Registry Atlas: inspector model, proxy behavior, and strict capability engine.

How to use it

Section titled “How to use it”

Point Atlas at a published discovery URL or index.json. See Inspect a registry for the inspection and strict capability query workflow.

Example: an integrator from a tax authority opens Registry Atlas to read the published manifest, schema, and evidence offerings of a business register before writing any integration code.

Section titled “Related docs”