Vocabulary fields
Shared fields for Observables and Origins: catalog snapshots, exact term references and attributed connections to claims.
Catalog snapshot · object
Document structure
Start with a top-level field, then follow its values and alternatives. The index stays available as you explore.
Required fields must be present. Lists may be empty unless a minimum is specified.
Extra fields: Not allowed at this object root. Only the catalog provides an extensions field.
Fields
9 fieldskindstringIdentifies a vocabulary catalog document.RequiredschemaVersionstringThe catalog contract version, separate from its revision and npm version.RequiredidstringID of this catalog document.RequiredcatalogIdstringAuthority-qualified identity of the vocabulary. This is an identifier, not a URL the evaluator fetches.RequiredrevisionstringImmutable catalog revision. The moving label latest is rejected.Required4 nestedpublishedBystringDeclared publisher; parsing does not authenticate this identity.RequiredpublishedAtstringWhen this revision was declared published.Required4 nestedtermslist of objectNonempty list of terms. IDs and supplied short codes must be unique within the catalog.Required9 nestedextensionsobjectNamespaced additional JSON. Core vocabulary checks do not validate its domain meaning.Optional2 nested
How to read this reference npm 2.0.0-beta.4
Required is local. A field marked required must exist in its containing object or selected alternative. A required list can be empty unless minItems says otherwise. Choose the alternative that describes your data; do not combine every alternative.
Structure and meaning are checked separately. These entries come from the published package. Explanations and grouping are editorial. Follow the validation guide for semantic checks such as unresolved references.
- Schema identifier
urn:disclosureos:experimental:vocabulary-catalog:0.1.0- Package export
@disclosureos/records/experimental/v2/vocabulary-catalog/schema/0.1.0
Repeated keys in different branches are separate schema entries. Their exact paths and field links preserve that context. The schema version is independent of the npm package version.