====== P4-REQ-21-5-009 ======

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

===== Statement =====

Each DDS Topic mapping SHALL identify the applicable governance, versioning, and compatibility expectations.

===== Source =====

Part 4, Section 21.5: Communication Endpoint Mapping Requirements.

===== Rationale =====

DDS Topic mappings must remain governed and compatible across producers, consumers, data representations, and QoS configurations.

Recording governance, versioning, and compatibility expectations allows changes to communication mappings to be reviewed without silently breaking the Phase 0 implementation baseline.

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

This requirement applies to:

  * DDS Topic mappings;
  * publishers and subscribers;
  * IDL structures and generated types;
  * QoS profiles; and
  * configuration artifacts.

===== Verification =====

Verification SHALL confirm that each DDS Topic mapping identifies applicable governance, versioning, and compatibility expectations.

Verification activities should include review checks confirming that:

  * applicable versions are identifiable;
  * publisher and subscriber expectations are compatible;
  * IDL and generated-type versions are compatible;
  * QoS compatibility is reviewable; and
  * changes follow implementation governance.

===== Traceability =====

This requirement connects communication mappings to the Phase 0 implementation governance and compatibility model.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-008]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-010]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-5-communication-endpoint-mapping-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>