9.3 DDS Topic Naming Principles

Go To Mapping from FX Logical Communication Endpoints to DDS Topics

DDS Topic names shall follow the Phase 0 topic naming convention defined by this Implementation Profile and elaborated in the Phase 0 Developer Handbook.

The Topic name should identify the Runtime Plane, FX domain context, and subject carried by the Topic. The Topic name should remain stable enough to support traceability, review, artifact generation, configuration, scripting, and later deployment planning.

A recommended naming pattern is:

<Plane>.<Domain>.<Subject>

Examples include:

 Data.FX.TransactionCandidate
Data.FX.ValidationResult
Data.FX.SemanticAssertion
Data.FX.ContractState
Data.FX.CashFlowObligation
Policy.FX.PolicyDecision
Policy.FX.ReleasePackage
Audit.FX.AuditRecord
Audit.FX.ProvenanceRecord
Health.FX.NodeStatus
Control.FX.ControlCommand
Audit.FX.ReplayRequest
Audit.FX.ReplayResult

The Topic name is an implementation artifact. It does not redefine the FX logical Communication Endpoint or the FX logical information structure.