9.1 Role of IDL in Phase 0 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 9.1 Role of IDL in Phase 0 ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:09-dds-idl-type-generation:start | Return to DDS / IDL / Type Generation ]]

[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] defines the data structures that Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] exchange through [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topics. The team should treat IDL files as governed source definitions, not as incidental implementation files. IDL definitions provide the basis for generated DDS type support, language bindings, topic payloads, and compatibility checks.

Phase 0 should use IDL to define the minimum structures required for the initial Node network. These structures should support [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status reporting, Control Plane command handling, and any placeholder [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] messages required by the FX demonstration profile.

IDL should not become a dumping ground for speculative future structures. The team should add IDL definitions when a structure supports a current Phase 0 topic, Node interaction, generated type, test, or documented extension point. If a future structure does not yet participate in the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], the team should record it as a future requirement rather than adding unused IDL.

The team should keep architectural meaning outside generated implementation code. IDL defines typed Data Structures for exchange. The Topic Catalogue, Node Catalogue, architecture documents, and handbook define the meaning, purpose, participants, and [[dido:99_annexes:annex-b-terms-and-definitions:g:governance|Governance]] of those structures.

----

<WRAP centeralign>

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

</WRAP>