====== Logical Versioning ====== [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]] ===== Discussion ===== Logical Versioning identifies versions of logical definitions, logical relationships, and logical constraints. Logical Versioning supports controlled evolution. It allows authors and reviewers to distinguish one version of a Logical Data Structure Definition, Logical Communication Endpoint, Logical Interaction Pattern, Logical Node Role, or logical policy constraint from another. Logical Versioning also supports compatibility review. A Logical Node that produces information and a Logical Node that consumes information rely on compatible versions of the relevant Logical Data Structure Definition and Logical Communication Endpoint. Logical Versioning does not prescribe a version-numbering scheme, repository structure, branching model, package format, or deployment mechanism. Later profiles define those details for a selected implementation context. ===== Definition ===== //Identification and control of versions for logical definitions, relationships, and constraints.// ===== Source ===== Specialization of Governance and Authority, Traceability, and Data Structure Definition from Part 1, Sections 9.6, 7.10, and 7.7; generalised from schema, model, topic, QoS, ontology, and configuration versioning material in the original FX Demo Reference Architecture. ===== Note ===== Logical Versioning supports traceability by linking a logical definition or interaction to the version that governed it. ===== Example ===== A validation assertion identifies the version of the Logical Data Structure Definition and validation rule set used to produce the assertion. ---- [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]] ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.