This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:i:idl [2026/07/18 12:33] – external edit 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:i:idl [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| Interface Definition Language (IDL), often referred to as OMG IDL in Object Management Group specifications, defines data types and interfaces in a language-neutral form. | Interface Definition Language (IDL), often referred to as OMG IDL in Object Management Group specifications, defines data types and interfaces in a language-neutral form. |
| |
| In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, IDL belongs to implementation and platform-specific mapping concerns. IDL does not define logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. | In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, IDL belongs to implementation and platform-specific mapping concerns. IDL does not define logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. |
| |
| An implementation profile maps selected logical information structures and logical Communication Endpoints to IDL modules, structures, enumerations, constants, annotations, generated language bindings, and generated type-support artifacts when DDS or another IDL-based technology serves as the selected implementation technology. | An implementation profile maps selected logical information structures and logical Communication Endpoints to IDL modules, structures, enumerations, constants, annotations, generated language bindings, and generated type-support artifacts when DDS or another IDL-based technology serves as the selected implementation technology. |