How to resolve
/resolve/ocom:Object→ /vocabulary/object/resolve/OCOM-DEF-0001→ /vocabulary/object/resolve/META-OBJECT-01→ /vocabulary/object
Machine map: resolve.json. Search: /search.
Beyond the 39 term identifiers below, resolve.json also maps the nine comparison records (COMP-*) and the Specification chapters and annexes (SPEC-00 to SPEC-08, SPEC-A1 to SPEC-A3).
All identifiers
| URI | Definition ID | Doc ID | Resolves to |
|---|---|---|---|
ocom:Object | OCOM-DEF-0001 | META-OBJECT-01 | /vocabulary/object |
ocom:Identity | OCOM-DEF-0002 | META-IDENTITY-01 | /vocabulary/identity |
ocom:Metadata | OCOM-DEF-0003 | META-METADATA-01 | /vocabulary/metadata |
ocom:Relationship | OCOM-DEF-0004 | META-RELATIONSHIP-01 | /vocabulary/relationship |
ocom:Reference | OCOM-DEF-0005 | META-REFERENCE-01 | /vocabulary/reference |
ocom:Registry | OCOM-DEF-0006 | META-REGISTRY-01 | /vocabulary/registry |
ocom:Classification | OCOM-DEF-0007 | META-CLASSIFICATION-01 | /vocabulary/classification |
ocom:Capability | OCOM-DEF-0008 | META-CAPABILITY-01 | /vocabulary/capability |
ocom:Contract | OCOM-DEF-0009 | META-CONTRACT-01 | /vocabulary/contract |
ocom:Policy | OCOM-DEF-0010 | META-POLICY-01 | /vocabulary/policy |
ocom:Constraint | OCOM-DEF-0011 | META-CONSTRAINT-01 | /vocabulary/constraint |
ocom:Ownership | OCOM-DEF-0012 | META-OWNERSHIP-01 | /vocabulary/ownership |
ocom:Organization | OCOM-DEF-0013 | META-ORGANIZATION-01 | /vocabulary/organization |
Referenced concepts that are not terms
Seven identifiers this site prints name concepts that Core Vocabulary terms refer to without defining, and the eighth row below is the identifier of the term set itself. They resolve to the page that answers for them and say which tier defines them, rather than returning not found.
| Identifier | Resolves to | Defined at |
|---|---|---|
ocom:Lifecycle | Chapter 6 | Models tier |
ocom:Workflow | Chapter 5 | Models tier |
ocom:Memory | Governance candidates | Memory tier, not published here |
ocom:Agent | Governance candidates | AI extension, not published here |
ocom:Tool | Governance candidates | AI extension, not published here |
ocom:Evaluation | Governance candidates | AI extension, not published here |
ocom:Governance | Governance candidates | No tier defines it as a per-Object characteristic (AO-023, AO-050) |
ocom:CoreVocabulary | Core Vocabulary | The term set itself, thirteen records |
Identifier families
Five families of identifier appear on this site. Two are canonical, three are minted by the publication layer and appear nowhere in the repository.
| Family | Example | Minted by | Rule |
|---|---|---|---|
META-*, GOV-*, LANG-*, SPEC-00 to SPEC-08 | META-OBJECT-01 | the canonical repository | The Document ID in the document's own header. This is the identifier the specification recognizes. |
OCOM-DEF-* | OCOM-DEF-0001 | this publication | Assigned once per Core Vocabulary term, in publication order, never reused and never renumbered. |
ocom:* | ocom:Object | this publication | The term name in the ocom: namespace, one per Core Vocabulary term. |
SPEC-A1 to SPEC-A3, COMP-* | COMP-BPMN-001 | this publication | Assigned to the informative annexes and to each comparison record. They look like repository identifiers and are not. |
| Record identifiers of site-published pages | OCOM-REVIEW-01, OWN-OCOM-UNO-01, REG-URI-01 | this publication | One per site-published record, so that every page this site prints an identifier for can be resolved. |
Identifiers are never reused, in line with Meta/Identity.md. A minted identifier carries no normative weight: the canonical identifier of a document is its Document ID, and the canonical source is the repository.