dido:99_annexes:annex-b-terms-and-definitions:i:idl

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:i:idl [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:i:idl [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Interface Definition Language (IDL) ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +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: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.
 +
 +===== Definition =====
 +
 +//language-neutral specification language used to define data types and interfaces for implementation mapping and generated language bindings//
 +
 +===== Source =====
 +
 +Generalised from Object Management Group Interface Definition Language usage and its application as an implementation mapping concern in [[fxdemo:04-part:start]].
 +
 +===== Note =====
 +
 +IDL is not a logical information structure, logical Communication Endpoint, logical Node, Runtime Plane, DDS Topic, DDS Domain, message bus, programming language, deployment environment, governance model, or evidence model.
 +
 +===== Example =====
 +
 +Part 4 maps selected FX Demo logical information structures to IDL structures that support generated Python type bindings for a DDS implementation profile.