====== P4-REQ-21-9-010 ======

[[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]

===== Statement =====

Each QoS profile mapping SHALL identify publisher and subscriber compatibility expectations.

===== Source =====

Part 4, Section 21.9: QoS Profile Requirements.

===== Rationale =====

DDS communication depends on compatible QoS expectations between publishers and subscribers.

Explicit compatibility expectations allow reviewers to determine whether participating implementations can communicate using the selected reliability, durability, history, ordering, liveliness, and related QoS behaviors.

===== Applies To =====

This requirement applies to:

  * QoS profile mappings;
  * DDS publishers;
  * DDS subscribers;
  * DDS Topic mappings; and
  * communication compatibility review.

===== Verification =====

Verification SHALL confirm that each QoS profile mapping identifies publisher and subscriber compatibility expectations.

Verification activities should include review checks confirming that:

  * publisher expectations are identified;
  * subscriber expectations are identified;
  * selected QoS settings are compatible;
  * incompatible combinations are detected during review; and
  * compatibility changes follow implementation governance.

===== Traceability =====

This requirement connects Phase 0 QoS profile mappings to publisher and subscriber compatibility expectations.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-005]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-006]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-008]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-009]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-9-qos-profile-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>