Scope SPEC-01
This specification defines the OCOM Core Vocabulary and the rules governing its use. It does not mandate a serialization, storage engine, or query language.
Where this specification and the Core Vocabulary appear to differ, the Core Vocabulary term record is authoritative for that term's definition.
Normative References SPEC-02
The definitions in the Core Vocabulary are normative and are incorporated by reference. This specification MUST NOT restate them.
Each term record carries its own status and version; a term is normative only at the status recorded in its record.
References
Core Concepts SPEC-03
The OCOM Specification defines the following core concepts. Each is defined normatively and only in the Core Vocabulary; this section references them and does not define them.
Conformance SPEC-04
A conforming implementation SHALL assign every managed object a stable Identity, SHALL record its Metadata and Ownership, and SHALL preserve its Relationships and Lifecycle as required by the corresponding Core Vocabulary term records.
A conforming implementation SHALL NOT redefine a core term; it MAY extend the model through additional, clearly separated concepts.
References
Extensibility SPEC-05
OCOM favours extension over enumeration. Implementations MAY introduce domain concepts, provided they do not alter the meaning of a core term.
Extensions SHOULD reference the core terms they build upon so that the extended model remains traceable to the canonical source.
References