Differences
This shows you the differences between two versions of the page.
| fxdemo:04-part:13-phase-0-qos-profile-model:13-3-qos-profile-mapping-principles:start [2026/07/25 10:10] – created owen | fxdemo:04-part:13-phase-0-qos-profile-model:13-3-qos-profile-mapping-principles:start [2026/07/25 10:15] (current) – owen | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| [[fxdemo: | [[fxdemo: | ||
| - | The Phase 0 Implementation Profile applies the following principles when mapping DDS Topics to QoS profiles. | + | The Phase 0 Implementation Profile applies the following principles when mapping |
| Each QoS profile mapping identifies: | Each QoS profile mapping identifies: | ||
| - | * Runtime Plane or Runtime Planes it supports; | + | * [[dido: |
| * DDS Topic or Topic family that uses the profile; | * DDS Topic or Topic family that uses the profile; | ||
| * Communication purpose of the profile; | * Communication purpose of the profile; | ||
| Line 17: | Line 17: | ||
| * Compatibility expectations for publishers and subscribers; | * Compatibility expectations for publishers and subscribers; | ||
| * Configuration artifact that defines the profile; and | * Configuration artifact that defines the profile; and | ||
| - | * Traceability relationship to FX logical Communication Endpoint and Runtime Plane. | + | * [[dido: |
| 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. | 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. | ||