public:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition to public:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition nick_didopublic:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Version-Controlled Condition ====== ====== Version-Controlled Condition ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 7: Line 7:
 A version-controlled condition is one in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms. A version-controlled condition is one in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms.
  
-Version-controlled conditions support traceability, reproducibility, auditability, controlled evolution, and conformance evaluation within the [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].+Version-controlled conditions support traceability, reproducibility, auditability, controlled evolution, and conformance evaluation within the [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
  
 A version-controlled condition differs from an informal change state. An informal change state lacks governed identification, versioning, and change control. A version-controlled condition establishes the controlled state of an artifact for review, use, comparison, release, or evaluation. A version-controlled condition differs from an informal change state. An informal change state lacks governed identification, versioning, and change control. A version-controlled condition establishes the controlled state of an artifact for review, use, comparison, release, or evaluation.
Line 17: Line 17:
 ===== Source ===== ===== Source =====
  
-Structured Information Processing [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]+Structured Information Processing [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]
  
 ===== Note ===== ===== Note =====
Line 25: Line 25:
 ===== Example ===== ===== Example =====
  
-A [[private:99_annexes:annex-b-terms-and-definitions:s:semantic_artefact]], [[private:99_annexes:annex-b-terms-and-definitions:s:structural_artefact]], [[private:99_annexes:annex-b-terms-and-definitions:i:interface_contract]], or [[private:99_annexes:annex-b-terms-and-definitions:i:interpretive_artefact]] is in a version-controlled condition when it has an explicit version identifier, approved change history, and governed release status.+A [[public:99_annexes:annex-b-terms-and-definitions:s:semantic_artefact]], [[public:99_annexes:annex-b-terms-and-definitions:s:structural_artefact]], [[public:99_annexes:annex-b-terms-and-definitions:i:interface_contract]], or [[public:99_annexes:annex-b-terms-and-definitions:i:interpretive_artefact]] is in a version-controlled condition when it has an explicit version identifier, approved change history, and governed release status.
  
 ---- ----
  • public/99_annexes/annex-b-terms-and-definitions/v/version-controlled_condition.1789260175.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido