Schemas
The seven JSON Schemas (draft 2020-12) of the public protocol objects, from docs/specification/schemas/ of loquitur-protocol. Each page lists every field with its type, whether it is required, its constraints and its description. The $id is a stable schema identity; nothing is promised to be served at it.
| Schema | $id |
|---|---|
change_summary.schema.json |
https://schemas.loquitur.dev/v1/change_summary.schema.json |
coverage_summary.schema.json |
https://schemas.loquitur.dev/v1/coverage_summary.schema.json |
lineage_summary.schema.json |
https://schemas.loquitur.dev/v1/lineage_summary.schema.json |
registry_entry.schema.json |
https://schemas.loquitur.dev/v1/registry_entry.schema.json |
trust_registry.schema.json |
https://schemas.loquitur.dev/v1/trust_registry.schema.json |
verification_receipt.schema.json |
https://schemas.loquitur.dev/v1/verification_receipt.schema.json |
verification_summary.schema.json |
https://schemas.loquitur.dev/v1/verification_summary.schema.json |
How the schemas, the reason-code catalog and the other machine-readable artifacts are owned and mirrored is in the index of normative artifacts. To validate a document against them, see Validate objects against the schemas.
Project site: loquitur.dev
Written for this site; text licensed CC BY 4.0.