====== FX Logical Versioning ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

FX Logical Versioning identifies versions of FX logical definitions, relationships, constraints, and profile elements.

FX Logical Versioning supports controlled evolution of FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], information structures, lifecycle states, interaction patterns, governance constraints, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships. It allows reviewers to distinguish the version of a definition used by a specific FX interaction, record, assertion, release package, replay result, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectation.

FX Logical Versioning also supports compatibility review. An FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] that produces information and an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] that consumes information rely on compatible versions of the relevant endpoint, information structure, lifecycle rule, semantic reference, or policy constraint.

===== Definition =====

//Identification and control of versions for FX logical definitions, relationships, constraints, and profile elements.//

===== Source =====

Specialization of [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_versioning|Logical Versioning]] from Part 2, Section 11.3, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1, Section 7.10; generalised from FX schema, model, semantic, topic, policy, and configuration versioning material in the original FX Demo Reference Architecture.

===== Note =====

FX Logical Versioning does not prescribe a numbering scheme, branch strategy, package format, repository layout, release process, or deployment mechanism.

===== Example =====

An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]] identifies the version of the validation expectations used to validate an FX Transaction Candidate.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>