Explain · OCOM Specification

Try

/explain/OCOM-DEF-0001 → why it resolves to Object (open)
/explain/ocom:Ownership → matched by URI (open)
/explain/META-CONTRACT-01 → matched by Doc ID (open)

An explanation exists for each of the thirteen Core Vocabulary terms under each of its three identifiers, thirty-nine records in all. The Specification chapter identifiers (SPEC-00 to SPEC-08) and Comparison identifiers (COMP-*) that resolve have no explain record.

Every explanation

Term	URI	Definition ID	Doc ID
Object	`ocom:Object`	`OCOM-DEF-0001`	`META-OBJECT-01`
Identity	`ocom:Identity`	`OCOM-DEF-0002`	`META-IDENTITY-01`
Metadata	`ocom:Metadata`	`OCOM-DEF-0003`	`META-METADATA-01`
Relationship	`ocom:Relationship`	`OCOM-DEF-0004`	`META-RELATIONSHIP-01`
Reference	`ocom:Reference`	`OCOM-DEF-0005`	`META-REFERENCE-01`
Registry	`ocom:Registry`	`OCOM-DEF-0006`	`META-REGISTRY-01`
Classification	`ocom:Classification`	`OCOM-DEF-0007`	`META-CLASSIFICATION-01`
Capability	`ocom:Capability`	`OCOM-DEF-0008`	`META-CAPABILITY-01`
Contract	`ocom:Contract`	`OCOM-DEF-0009`	`META-CONTRACT-01`
Policy	`ocom:Policy`	`OCOM-DEF-0010`	`META-POLICY-01`
Constraint	`ocom:Constraint`	`OCOM-DEF-0011`	`META-CONSTRAINT-01`
Ownership	`ocom:Ownership`	`OCOM-DEF-0012`	`META-OWNERSHIP-01`
Organization	`ocom:Organization`	`OCOM-DEF-0013`	`META-ORGANIZATION-01`

Programmatic interface: Knowledge API. Resolver over every registered identifier: /resolve.