9.2 Topic Mapping Principles [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.
====== 9.2 Topic Mapping Principles ======

[[fxdemo:04-part:09-mapping-from-fx-logical-communication-endpoints-to-dds-topics:start | Go To Mapping from FX Logical Communication Endpoints to DDS Topics ]]

The Phase 0 Implementation Profile applies the following principles when mapping FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]] to [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics.

Each DDS Topic mapping identifies:

  * the FX logical Communication Endpoint it realizes;
  * the FX logical information structure carried by the endpoint;
  * the [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structure and generated type used for the Phase 0 exchange;
  * the producing FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] or [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Role]];
  * the consuming FX logical Node or Node Role;
  * the [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] or Runtime Planes associated with the exchange;
  * the Quality of Service (QoS) profile or QoS profile family used for the Topic;
  * the applicable governance, versioning, and compatibility expectations; and
  * the traceability relationship back to the Part 3 FX logical Communication Endpoint.

The mapping does not require every future endpoint to exist in Phase 0. Phase 0 maps only the selected endpoints needed for the implementation baseline.

----

<WRAP centeralign>

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

</WRAP>