# Reference

**Status** Draft · **Version** 0.1 · **Updated** 20 July 2026 · **Doc ID** META-REFERENCE-01 · **Definition ID** OCOM-DEF-0005 · **URI** `ocom:Reference`

Canonical: https://ocom.uno/vocabulary/reference

> The OCOM Specification defines Reference as — A Reference is a directed association from one Object to another.

## Definition

A Reference is a directed association from one Object to another. A Reference identifies a target Object but does not define the semantic nature of the association. The meaning of the association is defined separately by the Relationship specification.

## Purpose

This document defines Reference within the OCOM Specification. A Reference enables one Object to identify, locate, or associate with another Object without defining the business meaning of their relationship. References support navigation, interoperability, traceability, and object connectivity throughout the OCOM ecosystem.

## Business meaning

References enable Objects to interact without embedding implementation details. They provide stable connections between Objects while preserving object independence and modularity.

## Design principles

Every Reference shall:

- identify a target Object
- remain independent of implementation technology
- support traceability
- preserve object independence
- support interoperability
- remain reusable

## Core characteristics

- Source Object
- Target Object
- Reference Direction
- Reference Type
- Reference Purpose
- Validity Period
- Status

## Relationship to other specifications

Reference interacts with:

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Registry`](/vocabulary/registry)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Ownership`](/vocabulary/ownership)
- `ocom:Governance`

Reference provides connectivity between Objects without defining business semantics.

## Referenced by

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Registry`](/vocabulary/registry)

## Independence — does not prescribe

- storage mechanisms
- pointer formats
- database keys
- communication protocols
- implementation technologies

## Conformance

A compliant implementation shall ensure that every managed Reference:

- support directed References
- preserve reference traceability
- maintain reference integrity
- support governance
- remain technology independent

## Provenance

Governance records: —

| Version | Date | Change |
| --- | --- | --- |
| 0.1 | 20 July 2026 | Initial draft |

## Recommended citation

OCOM Specification. Reference. META-REFERENCE-01 (OCOM-DEF-0005). Version 0.1. https://ocom.uno/vocabulary/reference

---

Machine representations — JSON: https://ocom.uno/vocabulary/reference.json · JSON-LD: https://ocom.uno/vocabulary/reference.jsonld · Markdown: https://ocom.uno/vocabulary/reference.md · Source: https://github.com/DenisHogberg/OCOM/blob/main/docs/Meta/Reference.md · History: https://github.com/DenisHogberg/OCOM/commits/main/docs/Meta/Reference.md

Generated as a deterministic projection of one canonical record.