Relational Identifier (RID) Specification

Overview

UBKDS supports an optional Relational Identifier (RID) to link multiple authoritative artifacts that belong to the same knowledge set across different functional uses.

Purpose

The RID enables deterministic, machine-readable relationships between policies, procedures, training, metrics, and other artifacts without extending or altering the classification taxonomy.

RIDs exist to:

• Preserve meaning across systems
• Support reliable linking
• Enable automation and governance
• Prevent silent drift

Canonical Structure

The canonical RID format is:

###.#.####

Components

###

UBKDS domain and sub-domain (meaning)

.#

Functional subcode (use)

.####

Relational Identifier (relationship key)

Optionality

• RID usage is optional
• Applied only when cross-artifact linkage is required
• Classification remains valid with or without an RID

Semantic Rules

• The RID identifies relationship, not order
• The RID carries no semantic meaning by itself
• The RID must never encode version, priority, or sequence

Canonical Examples

The following artifacts are distinct but governed as a single knowledge set:

All share the same RID (0003).

Canonical Rules

• RIDs are never sequential or time-based
• RIDs must not imply priority, order, or version
• Multiple RIDs may exist within the same domain
• Classification codes never change due to RID usage

UBKDS codes classify knowledge. RIDs relate artifacts.

Cross-References

• Functional Subcodes
• Canonical Domains
• Canonical Registry