20.3 DDS Topics Do Not Redefine Logical Communication Endpoints [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 20.3 DDS Topics Do Not Redefine Logical Communication Endpoints ======

[[fxdemo:04-part:start | Go To Top ]]

[[fxdemo:04-part:20-phase-0-implementation-rules-and-constraints:start | Return to Phase 0 Implementation Rules and Constraints ]]

A [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic realises an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] for the selected Phase 0 implementation context.

The DDS Topic name, [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype|Data Type]], [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] profile, publisher, subscriber, and [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] provide the implementation mechanism for exchange. They do not redefine the logical Endpoint, its purpose, participating FX logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Roles]], carried information structure, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classification, governance constraints, or [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

Later phases may extend, refine, supersede, or replace the DDS Topic mapping while preserving Traceability to the FX logical Communication Endpoint.

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>