====== P4-REQ-21-6-005 ====== [[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]] ===== Statement ===== Each IDL and generated type mapping SHALL identify the DDS Topic or Topics that carry the generated type. ===== Source ===== Part 4, Section 21.6: Information Structure Mapping Requirements. ===== Rationale ===== Identifying the DDS Topics that carry a generated type connects the implementation data representation to the communication exchanges in which it participates. This relationship supports communication review, type compatibility review, and end-to-end traceability from logical information structure through IDL and generated type to runtime exchange. ===== Applies To ===== This requirement applies to: * IDL and generated type mappings; * DDS Topics; * publishers and subscribers; and * communication mapping records. ===== Verification ===== Verification SHALL confirm that each IDL and generated type mapping identifies the DDS Topic or Topics that carry the generated type. Verification activities should include review checks confirming that: * applicable DDS Topics are identified; * Topic data representations agree with the generated type; * Topic mappings agree with the corresponding IDL structure; and * incompatible Topic/type relationships are not admitted to the baseline. ===== Traceability ===== This requirement connects Phase 0 generated types to the DDS Topic mappings through which they are exchanged. Related requirement identifiers: * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-6-004]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-6-006]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-004]] Related source section: * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-6-information-structure-mapping-requirements:start]] ===== Status ===== Draft ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.