Definition
Classification is the assignment of one or more descriptive categories to an Object. Classification enables Objects to be grouped, filtered, governed, and managed according to organizational requirements. Classification supplements an Object without altering its identity or business meaning.
Purpose
This document defines Classification within the OCOM Specification.
Classification provides a standardized mechanism for organizing, categorizing, and labeling Objects to support governance, discovery, interoperability, and operational management.
Business meaning
Classification allows organizations to organize Objects consistently across business domains and operational environments.
It improves discoverability, governance, reporting, access control, automation, and decision-making.
Design principles
Classification shall:
- be independent of Object Identity
- support multiple classifications
- be extensible
- support governance
- preserve consistency
- remain technology independent
Core characteristics
Every Classification shall define:
- Identifier
- Classification Name
- Classification Type
A Classification may additionally define:
- Description
- Parent Classification
- Classification Rules
- Validity Period
- Status
Relationship to other specifications
Classification interacts with:
Classification organizes Objects but does not define operational behavior.
Compared with
Read as: OCOM term, the nearest concept in the other model, and how close they are. Similar means the two carry the same intent; Partial means they overlap but differ in scope or obligation; None means the other model has no counterpart. The verdicts are site-published editorial judgments, not normative.
- OCOM vs Ontology: Similar (Class, subClassOf)
- OCOM vs Data Model: Partial (Type / Subtype table)
Independence
The Classification specification does not prescribe:
- taxonomy models
- ontology languages
- directory structures
- implementation technologies
Organizations remain free to implement Classification using any compatible approach.
Classification Types
Organizations may define classifications including:
- Type
- Category
- Tag
- Label
- Priority
- Criticality
- Sensitivity
- Business Area
- Operational Status
Additional classification types may be introduced.
Multiple Classification
An Object may belong to multiple Classifications simultaneously.
Multiple Classifications shall not change the Identity of the Object.
Organizations shall define rules for resolving conflicting classifications.
Classification Hierarchies
Organizations may organize Classifications into hierarchies.
Examples include:
- Parent / Child
- Taxonomy
- Functional Grouping
- Organizational Structure
Hierarchy structures are organization-specific.
Classification Lifecycle
Classifications may evolve over time.
Organizations shall preserve:
- classification history
- effective periods
- previous values
- governance decisions
Changing a Classification shall not change Object Identity.
Governance
Organizations shall define policies governing:
- classification creation
- modification
- retirement
- approval
- usage
Governance shall preserve consistency across Registries.
Auditability
Organizations shall retain:
- classification assignments
- assignment history
- governance decisions
- effective periods
Audit records shall remain immutable.
Conformance
A compliant implementation shall:
- support multiple Classifications
- preserve Object Identity
- support governance
- maintain classification history
- remain technology independent
Provenance
Governance records: —
| Version | Date | Change |
|---|---|---|
| 0.1 | 20 July 2026 | Initial draft |