# Registry

**Status** Draft · **Version** 0.1 · **Updated** 20 July 2026 · **Doc ID** META-REGISTRY-01 · **Definition ID** OCOM-DEF-0006 · **URI** `ocom:Registry`

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

> The OCOM Specification defines Registry as — A Registry is a managed collection of identifiable Objects organized according to defined governance rules.

## Definition

A Registry is a managed collection of identifiable Objects organized according to defined governance rules. A Registry provides controlled access to Objects while preserving identity, traceability, and operational consistency.

## Purpose

This document defines Registry within the OCOM Specification. A Registry provides a governed collection of Objects that enables consistent identification, discovery, management, and governance across the OCOM ecosystem. Registries establish authoritative sources for managed Objects.

## Business meaning

Registries enable organizations to maintain authoritative records of operational Objects. They improve consistency, interoperability, governance, and organizational visibility by ensuring that managed Objects are discoverable and governed throughout their lifecycle.

## Design principles

Every Registry shall:

- contain identifiable Objects
- preserve Object Identity
- support governance
- support discoverability
- support traceability
- remain technology independent

## Core characteristics

- Identifier
- Name
- Purpose
- Registry Scope
- Registered Object Types
- Ownership
- Classification
- Access Policy
- Registration Rules
- Retention Policy
- Versioning Policy

## Relationship to other specifications

Registry interacts with:

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Reference`](/vocabulary/reference)
- [`ocom:Ownership`](/vocabulary/ownership)
- [`ocom:Classification`](/vocabulary/classification)
- [`ocom:Policy`](/vocabulary/policy)

Registries organize managed Objects but do not alter Object semantics.

## Referenced by

- [`ocom:Identity`](/vocabulary/identity)
- [`ocom:Metadata`](/vocabulary/metadata)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Reference`](/vocabulary/reference)
- [`ocom:Classification`](/vocabulary/classification)
- [`ocom:Policy`](/vocabulary/policy)
- [`ocom:Ownership`](/vocabulary/ownership)

## Independence — does not prescribe

- database technologies
- directory services
- catalog platforms
- implementation architectures

## Conformance

A compliant implementation shall ensure that every managed Registry:

- manage identifiable Objects
- preserve Object Identity
- support governed registration
- maintain traceability
- preserve auditability
- remain technology independent

## Provenance

Governance records: —

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

## Recommended citation

OCOM Specification. Registry. META-REGISTRY-01 (OCOM-DEF-0006). Version 0.1. https://ocom.uno/vocabulary/registry

---

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

Generated as a deterministic projection of one canonical record.