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.
specification of how a platform-independent concept, information structure, relationship, constraint or behavior is represented using a selected implementation technology
DIDO Solutions, Inc.
An Implementation Mapping differs from a 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 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 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.
© 2026 DIDO Solutions, Inc. All Rights Reserved.