public:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer

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:a:architectural_governance_layer [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer to public:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer nick_didopublic:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Architectural Governance Layer ====== ====== Architectural Governance Layer ======
  
-[[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:
 An architectural governance layer identifies the abstraction layer at which lifecycle control, authority retention, structural governance, and semantic governance are defined. An architectural governance layer identifies the abstraction layer at which lifecycle control, authority retention, structural governance, and semantic governance are defined.
  
-The architectural governance layer separates governance obligations from implementation technologies. This separation allows the [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] to define authority, lifecycle, versioning, and semantic responsibilities without prescribing a specific platform, product, language, repository, runtime, or deployment environment.+The architectural governance layer separates governance obligations from implementation technologies. This separation allows the [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] to define authority, lifecycle, versioning, and semantic responsibilities without prescribing a specific platform, product, language, repository, runtime, or deployment environment.
  
 An architectural governance layer differs from an implementation governance mechanism. An implementation governance mechanism realizes governance through a selected technology. The architectural governance layer defines the governance meaning, responsibilities, and relationships independently of those implementation mechanisms. An architectural governance layer differs from an implementation governance mechanism. An implementation governance mechanism realizes governance through a selected technology. The architectural governance layer defines the governance meaning, responsibilities, and relationships independently of those implementation mechanisms.
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:r:reference_architecture]] defines authority retention, lifecycle control, semantic governance, and structural governance at the architectural governance layer before mapping those responsibilities to a repository, ontology store, message bus, database, workflow engine, or runtime platform.+A [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] defines authority retention, lifecycle control, semantic governance, and structural governance at the architectural governance layer before mapping those responsibilities to a repository, ontology store, message bus, database, workflow engine, or runtime platform.
  
 ---- ----
  • public/99_annexes/annex-b-terms-and-definitions/a/architectural_governance_layer.1789260133.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido