Rocom Specification

Changes — Correction Proposals & Supplements

Edition 2026a (draft) · CC-BY 4.0 · Source on GitHub

What Is a Change Record?

The Rocom specification evolves through a structured change process with three mechanisms, modeled after standards bodies like DICOM and IEC:

Correction Proposals

Each CP below shows its current status. A PROPOSAL is under review and is not yet normative text. A RATIFIED has been accepted and incorporated into the specification. SUPERSEDED has been replaced by a later change.

CPTitleStatusDatePart
CP-007Agent Identity Model (issuer-agnostic, UDI-aligned)PROPOSAL2026-08-28Part 3
CP-008Resource Authority ModelPROPOSAL2026-08-30General
CP-009Priority and Preemption ModelPROPOSAL2026-08-31General
CP-004—RESERVED—General
CP-006CostModel generalization — cost_factors arrayRATIFIED2026-08-22Part 3
CP-005Pin VDA 5050 version to 2.1RATIFIED2026-08-21Part 5
CP-001Split architecture figure from Part mapRATIFIED2026-08-12Part 1
CP-002Remove FILE scaffolding from CONFORMANCE.md; fix requirement formatRATIFIED2026-08-12Part 2
CP-003GOVERNANCE.md — funding, held-in-trust, Advisory BoardRATIFIED2026-08-12Part 7

Supplements

SupTitleStatusDate
Sup-001Orchestrator Service InterfaceRATIFIED2026-08-12
Sup-002Annex A — Engineering Practice NotesRATIFIED2026-08-18
Sup-003BMS Infrastructure ContractDRAFT2026-08-21
Sup-004—RESERVED—