====== Twin Identity ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Twin Identity provides the logical identity shared by one or more [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]] representing the same twin. The Twin Identity remains independent of any particular realization, implementation, deployment, process, container, network endpoint, DDS entity, or other realization-specific mechanism. A Twin Identity allows a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] to refer to the same logical twin when different Twin Realizations participate in the test. The concept derives in part from the U.S. Patent Application description of virtual and physical Twin Nodes that share an identifier and from the DIDO-TE requirement to select between virtual and real-world twin nodes during testing. ===== Definition ===== //the logical identity shared by one or more [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]] representing the same twin// ===== Source ===== * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], Twin Node concepts and identifiers shared among Twin Nodes * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], F17, //Twin Nodes Selection// * DIDO-TE normalization of the source concepts ===== Note ===== A Twin Identity is distinct from the identity of a particular Twin Realization. Changing the selected Twin Realization does not, by itself, change the Twin Identity. A Twin Identity does not prescribe how an implementation represents or transports the identity. ===== Example ===== A logical twin identified as ''T-4711'' has both a virtual Twin Realization and a real-world Twin Realization. Both realizations participate in the same Twin Identity even though each realization has its own identity and implementation characteristics. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.