====== P4-REQ-21-5-006 ======

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

===== Statement =====

Each DDS Topic mapping SHALL identify the consuming FX logical Node or Node Role.

===== Source =====

Part 4, Section 21.5: Communication Endpoint Mapping Requirements.

===== Rationale =====

Identifying the consuming Node or Node Role makes the receiving responsibility for each DDS exchange explicit.

This allows reviewers to confirm that subscriptions and downstream processing remain aligned with the logical responsibilities defined in Part 3.

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

This requirement applies to:

  * DDS Topic mappings;
  * consuming implementation participants;
  * FX logical Nodes;
  * FX logical Node Roles; and
  * subscription mappings.

===== Verification =====

Verification SHALL confirm that each DDS Topic mapping identifies the consuming FX logical Node or Node Role.

Verification activities should include review checks confirming that:

  * the consuming logical responsibility is explicitly identified;
  * the implementation subscriber maps to the identified Node or Node Role;
  * consumer responsibility agrees with Part 3; and
  * subscription responsibility remains traceable.

===== Traceability =====

This requirement connects DDS subscription responsibility to the applicable FX logical Node or Node Role.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-005]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-4-003]]

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>