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:g:governance_and_authority [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Governance and Authority ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Governance and Authority define who may define, change, approve, apply, release, review, or rely on structured information, | ||
| + | |||
| + | 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, | ||
| + | ' | ||
| + | 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 ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Informed by SIP-RA governance and authority concerns, aligned with FDIS-RA semantic governance, version context, auditability, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Governance and Authority apply to concepts, models, definitions, | ||
| + | |||
| + | ===== 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. | ||