dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Governance and Authority ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Governance and Authority define who may define, change, approve, apply, release, review, or rely on structured information, semantic definitions, interpretation rules, policies, versions, and evidence.
 +
 +Governance controls the lifecycle and accountability. Authority identifies the source or body responsible for a definition, rule, policy, decision, release, or interpretation. Together, they prevent meaning and control from drifting silently across systems, tools, implementations, or organizations.
 +'
 +Governance and Authority remain distinct from the technical mechanisms that implement them. A repository, policy engine, approval workflow, access-control mechanism, or configuration service may support governance, but it does not replace the governance concern.
 +
 +===== Definition =====
 +
 +//responsibility and control over definition, change, approval, application, release, review, or reliance//
 +
 +===== Source =====
 +
 +Informed by SIP-RA governance and authority concerns, aligned with FDIS-RA semantic governance, version context, auditability, and institutional accountability; adapted from FX Demo Reference Architecture material on IEF policy release, schema governance, ontology governance, QoS governance, topic governance, data governance, and node role governance.
 +
 +===== Note =====
 +
 +Governance and Authority apply to concepts, models, definitions, policies, rules, profiles, artifacts, deployment configurations, and evidence.
 +
 +===== Example =====
 +
 +A policy authority may approve which transaction details may be released to a regulator, while a semantic authority may approve the meaning of a regulatory classification.