Governance and Authority [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Governance and Authority ======

[[public: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.