13.3 QoS Profile 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.

====== 13.3 QoS Profile Mapping Principles ======

[[fxdemo:04-part:13-phase-0-qos-profile-model:start | Go To Phase 0 QoS Profile Model ]]

The Phase 0 Implementation Profile applies the following principles when mapping [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics to QoS profiles.

Each QoS profile mapping identifies:

  * [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] or Runtime Planes it supports;
  * DDS Topic or Topic family that uses the profile;
  * Communication purpose of the profile;
  * Expected reliability behavior;
  * Expected durability behavior;
  * Expected history behavior;
  * Expected ordering behavior;
  * Expected liveliness or availability behavior;
  * Compatibility expectations for publishers and subscribers;
  * Configuration artifact that defines the profile; and
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship to FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoint]] and Runtime Plane.

The QoS profile mapping does not require production-grade QoS maturity in Phase 0. It defines the selected communication behavior needed for the Phase 0 demonstration baseline.

----

<WRAP centeralign>

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

</WRAP>