====== Implementation Mapping ======

[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

An Implementation Mapping specifies how a platform-independent concept, information structure, relationship, constraint or behavior is represented using a selected implementation technology.

The mapping may define implementation names, data types, field representations, cardinalities, encodings, precision rules, default values, validation rules, communication constructs, persistence constructs and programming-language bindings.

An Implementation Mapping may also identify implementation-specific restrictions, extensions, or information loss. The mapping retains a reference to the applicable platform-independent definition so an engineer or automated tool can determine the implementation artifact's source meaning.

===== Definition =====

> //specification of how a platform-independent concept, information structure, relationship, constraint or behavior is represented using a selected implementation technology//

===== Source =====

DIDO Solutions, Inc.

===== Note =====

An Implementation Mapping differs from a [[public:99_annexes:annex-b-terms-and-definitions:s:semantic_alignment|Semantic Alignment]]. A Semantic Alignment relates meanings across semantic contexts. An Implementation Mapping represents an authoritative meaning using a selected technology.

An Implementation Mapping contributes to a [[public:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Model (PSM)]]. The applicable platform-independent definition remains authoritative for domain meaning unless the governing specification explicitly states otherwise.

An Implementation Mapping should identify:

  * The source concept or information structure
  * The source model and version
  * The selected implementation technology
  * The target artifact
  * The mapping rules
  * Applicable restrictions or extensions
  * Validation and compatibility rules
  * Known information loss

===== Example =====

The FX Information Model defines a platform-independent `FXSwap` information structure. An FX Demo implementation profile provides an Implementation Mapping from that structure to an IDL structure carried by a DDS Topic. A separate Implementation Mapping may represent the same platform-independent structure using JSON Schema.

----
<WRAP centeralign>
© 2026 DIDO Solutions, Inc. All Rights Reserved.
</WRAP>