7.7 Topic Naming

Go To Top

Return to Naming and File Conventions

DDS topic names should follow a consistent, architecture-facing convention. Topic names should identify the plane, domain, and subject of the topic.

The recommended topic naming pattern is:

<Plane>.<Domain>.<Subject>

Representative examples include:

• Control.Node.Status
• Control.Node.Command
• Data.Reference.FxTransaction
• Data.Financial.CashFlow
• Data.Audit.Provenance
• Release.External.Package

The first element should identify the plane or major interaction category. For Phase 0, the team should distinguish at least the Control Plane and Data Plane topics. If the implementation later adds release or external exchange topics, those names should remain consistent with the architectural meaning.

Topic names should use stable business or architectural concepts rather than implementation-specific class names. A topic name should not change because the team refactors a class, moves a file, or renames a container.

The team should document every Phase 0 topic in the Topic Catalogue. A topic should not enter the Baseline unless the team can identify its purpose, data structure, participating Nodes, QoS expectations, and relationship to the Phase 0 demonstration.