# Relationship

**Status** Draft · **Version** 0.1 · **Updated** 20 July 2026 · **Doc ID** META-RELATIONSHIP-01 · **Definition ID** OCOM-DEF-0004 · **URI** `ocom:Relationship`

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

> The OCOM Specification defines Relationship as — A Relationship is a governed semantic association between Objects.

## Definition

A Relationship is a governed semantic association between Objects. A Relationship expresses how Objects are connected within the operational model. Unlike a Reference, a Relationship conveys business meaning.

## Purpose

This document defines Relationship within the OCOM Specification. Relationship represents the semantic association between two or more Objects. Relationships enable organizations to model operational structures, dependencies, ownership, collaboration, and business meaning independently of implementation technologies.

## Business meaning

Relationships enable organizations to describe operational reality as interconnected Objects rather than isolated elements. They provide the structural foundation for business models, workflows, governance, memory, knowledge, and artificial intelligence.

## Design principles

Every Relationship shall:

- connect identifiable Objects
- express business semantics
- remain explicit
- support governance
- preserve traceability
- remain technology independent

## Core characteristics

- Identifier
- Source Object
- Target Object
- Relationship Type
- Direction
- Cardinality
- Status
- Validity Period
- Constraints
- Governance Rules

## Relationship to other specifications

Relationship interacts with:

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Reference`](/vocabulary/reference)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Registry`](/vocabulary/registry)
- [`ocom:Ownership`](/vocabulary/ownership)
- [`ocom:Policy`](/vocabulary/policy)
- [`ocom:Constraint`](/vocabulary/constraint)
- [`ocom:Organization`](/vocabulary/organization)

Organization connects to other Objects exclusively through Relationship (see Meta/Organization.md).

## Referenced by

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Reference`](/vocabulary/reference)
- [`ocom:Registry`](/vocabulary/registry)
- [`ocom:Capability`](/vocabulary/capability)
- [`ocom:Contract`](/vocabulary/contract)
- [`ocom:Organization`](/vocabulary/organization)

## Independence — does not prescribe

- database relationships
- graph technologies
- object models
- APIs
- implementation technologies

## Conformance

A compliant implementation shall ensure that every managed Relationship:

- define Relationships explicitly
- preserve business semantics
- support lifecycle management
- maintain traceability
- support governance
- remain technology independent

## Provenance

Governance records: CAND-005

| Version | Date | Change |
| --- | --- | --- |
| 0.1 | 20 July 2026 | Initial draft |
| 0.1 | 25 July 2026 | Added Organization to Relationship to Other Specifications, per ADR CAND-005 (Option C) |

## Recommended citation

OCOM Specification. Relationship. META-RELATIONSHIP-01 (OCOM-DEF-0004). Version 0.1. https://ocom.uno/vocabulary/relationship

---

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

Generated as a deterministic projection of one canonical record.