Mapping [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.
====== Mapping ======

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

===== Discussion =====

A Mapping specifies correspondences between elements of two or more models, structures, vocabularies, representations, or contexts.

A Mapping may identify:

  - Source and target elements
  - Corresponding concepts, properties, values, or relationships
  - Conditions under which a correspondence applies
  - Rules for translating or transforming source elements into target elements
  - Information that cannot be represented in the target
  - Applicable authorities, versions, and lifecycle states
  - Provenance and evidence supporting the Mapping

A Mapping may be declarative or executable. A declarative Mapping describes relationships between source and target elements. An executable Mapping includes rules or procedures that can be applied to produce or interpret target elements.

A Mapping does not necessarily assert that its source and target elements are identical or semantically equivalent. It may describe exact equivalence, partial correspondence, specialization, generalization, approximation, conversion, or another explicitly defined relationship.

Within Model Driven Architecture, a Mapping may specify how elements of one [[public:99_annexes:annex-b-terms-and-definitions:m:model|Model]] are transformed into elements of another Model. A Platform Independent Model-to-Platform Specific Model Mapping is one specialized form of Mapping.

Within the Structured Information Processing Reference Architecture, Mappings may relate structural definitions, semantic concepts, Vocabulary entries, interpretive rules, Interface representations, or jurisdiction-specific artifacts. Such Mappings preserve the applicable context, authority, version, and transformation rules.

===== Definition =====

//a governed specification of correspondences between elements of two or more models, structures, vocabularies, representations, or contexts, including any rules required to translate or transform those elements//

===== Source =====

Informed by OMG Model Driven Architecture concepts and specialized for use across Dido Solutions specifications.

===== Note =====

A Mapping is distinct from a transformation. A Mapping specifies correspondences and any applicable transformation rules. A transformation applies such rules to produce a result.

Mappings should identify their directionality. A Mapping from source A to target B does not necessarily define a valid or lossless Mapping from B to A.

When a Mapping is governed, its authority, applicability, version, provenance, status, and lifecycle are explicitly controlled.

===== Example =====

Two jurisdictions use different codes for operational readiness. A Mapping relates each source code to the corresponding target concept, identifies partial or unsupported correspondences, specifies the governing authorities and versions, and defines the rules for translating values exchanged across the jurisdictional boundary.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>