Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:v:version [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:v:version [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Version ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Version identifies a distinguishable state of an [[public: | ||
| + | |||
| + | An Artifact can have multiple Versions when its content, structure, behavior, configuration, | ||
| + | |||
| + | A Version can identify the state of an Artifact such as a: | ||
| + | |||
| + | * Document | ||
| + | * Specification | ||
| + | * Requirement | ||
| + | * [[public: | ||
| + | * Data model | ||
| + | * Schema | ||
| + | * Configuration | ||
| + | * Policy | ||
| + | * Interface | ||
| + | * Software component | ||
| + | * Executable artifact | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | |||
| + | A Version should have a Version Identifier that distinguishes it from other Versions of the same Artifact. | ||
| + | |||
| + | A Version can also identify: | ||
| + | |||
| + | * The Artifact to which it applies | ||
| + | * Its Version Identifier | ||
| + | * Its creation time | ||
| + | * Its creator or responsible authority | ||
| + | * Its relationship to preceding and succeeding Versions | ||
| + | * The changes represented by the Version | ||
| + | * Its applicable status | ||
| + | * Its applicable dependencies | ||
| + | * Its content digest | ||
| + | * Its applicable [[public: | ||
| + | * Its [[public: | ||
| + | * Its [[public: | ||
| + | |||
| + | The applicable versioning policy determines: | ||
| + | |||
| + | * Which changes require a new Version | ||
| + | * How Version Identifiers are assigned | ||
| + | * Whether Version Identifiers imply an ordering | ||
| + | * Whether a Version can be modified after identification | ||
| + | * How Versions relate to releases | ||
| + | * How obsolete or superseded Versions are treated | ||
| + | * How compatibility among Versions is represented | ||
| + | |||
| + | [[public: | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | This definition establishes Version as the identified state managed through Version Control. It separates the Version itself from the process and system used to manage it. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Version is distinct from [[public: | ||
| + | |||
| + | * A Version identifies a distinguishable state of an Artifact | ||
| + | * Version Control is the process for managing distinguishable revisions and the relationships among them | ||
| + | |||
| + | A Version is distinct from a [[public: | ||
| + | |||
| + | * A Version identifies the state being managed | ||
| + | * A Version Control System provides the mechanisms used to manage Versions | ||
| + | |||
| + | A Version is not necessarily a [[public: | ||
| + | |||
| + | A Version is not necessarily: | ||
| + | |||
| + | * Approved | ||
| + | * Accepted | ||
| + | * Released | ||
| + | * Published | ||
| + | * Deployed | ||
| + | * Operational | ||
| + | * Current | ||
| + | * Compatible with another Version | ||
| + | |||
| + | Those characteristics require separate status, governance, release, deployment, or compatibility information. | ||
| + | |||
| + | A Version Identifier does not necessarily indicate chronological order, precedence, maturity, approval status, or compatibility unless the applicable versioning policy defines that meaning. | ||
| + | |||
| + | Two copies of an Artifact can represent the same Version when they preserve the same identified state. Conversely, two Artifacts with similar names do not represent the same Version unless their identities and governed states establish that relationship. | ||
| + | |||
| + | A change in storage location, packaging, encoding, or representation does not necessarily create a new Version when the governed content and semantics remain unchanged. The applicable versioning policy determines whether such a change requires a new Version. | ||
| + | |||
| + | A reproducible [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | That Version identifies: | ||
| + | |||
| + | * The executable instructions | ||
| + | * The applicable [[private: | ||
| + | * The required dependencies | ||
| + | * The entry point | ||
| + | * The execution requirements | ||
| + | * The executable artifact digest | ||
| + | * The applicable [[public: | ||
| + | |||
| + | A later change to the executable instructions creates Version '' | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||