A Twin Data Mapping identifies the semantic correspondence between a represented characteristic in a Twin Relationship and the data used by participating Twin Realizations to represent that characteristic.
Participating Twin Realizations may use different names, data structures, types, units, encodings, Topics, fields, or communication mechanisms for the same represented characteristic.
A Twin Data Mapping makes those differences explicit and provides a controlled basis for interpreting corresponding data across Twin Realizations.
The mapping defines semantic correspondence independently of the communication mechanism used to transport the data. A DDS Topic match, compatible datatype, or Quality of Service match does not, by itself, establish a Twin Data Mapping.
a mapping that identifies the semantic correspondence between a represented characteristic in a Twin Relationship and the data used by participating Twin Realizations to represent that characteristic
A Twin Data Mapping applies only to characteristics identified as participating in the applicable Twin Relationship.
A Twin Data Mapping may identify differences in:
A Twin Data Mapping does not require participating Twin Realizations to use identical data representations.
A communication mechanism transports data associated with a Twin Data Mapping but does not establish the semantic correspondence represented by the mapping.
A real-world Twin Realization reports temperature as a field named temperature_f using degrees Fahrenheit, while a virtual Twin Realization represents the same characteristic as temperature_c using degrees Celsius.
The Twin Data Mapping identifies both data elements as representations of the same temperature characteristic and identifies the correspondence required between their units and values.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.