dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-011

P4-REQ-21-5-011

DDS Topics SHALL NOT redefine FX logical Communication Endpoints.

Part 4, Section 21.5: Communication Endpoint Mapping Requirements.

DDS Topics are selected Phase 0 implementation mechanisms for realizing logical communication. They do not define the logical purpose, participants, information meaning, Runtime Plane classification, or governance of the corresponding Communication Endpoint.

This constraint preserves separation between the Part 3 logical architecture and the Part 4 DDS implementation profile.

This requirement applies to:

  • DDS Topics;
  • DDS Topic mappings;
  • QoS profiles;
  • publishers and subscribers;
  • configuration artifacts; and
  • FX logical Communication Endpoints.

Verification SHALL confirm that DDS Topics do not redefine FX logical Communication Endpoints.

Verification activities should include review checks confirming that:

  • logical endpoint definitions remain governed by Part 3;
  • DDS Topic names do not replace logical endpoint definitions;
  • DDS data types and QoS choices remain implementation concerns;
  • publisher and subscriber mappings remain subordinate to the logical exchange; and
  • changes to DDS mappings do not silently alter logical meaning.

This requirement preserves the separation between the FX logical Communication Endpoint model and its selected Phase 0 DDS realization.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-04/p4-req-21-5-011.txt
  • Last modified: 2026/08/06 16:09
  • by owen