| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane to dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane nick_dido | dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Policy And Release Plane ====== | ====== Policy And Release Plane ====== |
| |
| [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] | [[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| The Policy and Release Plane supports governed decisions about access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, and controlled movement of information. It separates the distribution of internal information from authorised release to another participant, authority, community, jurisdiction, or external recipient. | The Policy and Release Plane supports governed decisions about access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, and controlled movement of information. It separates the distribution of internal information from authorized release to another participant, authority, community, jurisdiction, or external recipient. |
| |
| The Policy and Release Plane helps the architecture preserve control over information that crosses organisational, jurisdictional, supervisory, public, community-of-interest, regional, treaty-based, bilateral, national, or global boundaries. It identifies how the system decides what information may be shared, with whom, in what form, for what purpose, under which authority, and subject to which obligations. | The Policy and Release Plane helps the architecture preserve control over information that crosses organizational, jurisdictional, supervisory, public, community-of-interest, regional, treaty-based, bilateral, national, or global boundaries. It identifies how the system decides what information may be shared, with whom, in what form, for what purpose, under which authority, and subject to which obligations. |
| |
| The Policy and Release Plane also supports data sovereignty and data residency concerns. Full transaction detail may be required to remain within a local, institutional, national, or otherwise authorised residency domain. At the same time, selected metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, or recipient-specific release products may be authorised for broader regional, bilateral, treaty-based, agency, or global oversight. The conceptual distinction between full transaction detail and lower-sensitivity metadata or aggregate information allows local authorities to retain control over detailed transaction management while still supporting governed cross-boundary oversight. | The Policy and Release Plane also supports data sovereignty and data residency concerns. Full transaction detail may be required to remain within a local, institutional, national, or otherwise authorized residency domain. At the same time, selected metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, or recipient-specific release products may be authorized for broader regional, bilateral, treaty-based, agency, or global oversight. The conceptual distinction between full transaction detail and lower-sensitivity metadata or aggregate information allows local authorities to retain control over detailed transaction management while still supporting governed cross-boundary oversight. |
| |
| A later logical architecture or implementation profile may realise Policy and Release Plane interactions through Policy Enforcement Points, Policy Decision Points, Policy Administration Point capabilities, Policy Information Point capabilities, release services, redaction services, transformation services, metadata or aggregate view builders, information markings, obligation records, release packages, release-specific endpoints, or audit records. Those mechanisms do not redefine the Policy and Release Plane. | A later logical architecture or implementation profile may realize Policy and Release Plane interactions through Policy Enforcement Points, Policy Decision Points, Policy Administration Point capabilities, Policy Information Point capabilities, release services, redaction services, transformation services, metadata or aggregate view builders, information markings, obligation records, release packages, release-specific endpoints, or audit records. Those mechanisms do not redefine the Policy and Release Plane. |
| |
| The Policy and Release Plane is IEF-inspired. It uses information-sharing and safeguarding concepts such as policy-mediated release, enforcement, decision, administration, attributes, obligations, and evidence. This conceptual architecture does not require a later profile to claim full IEF compliance. A later profile may become more closely aligned with OMG IEF as the architecture matures. | The Policy and Release Plane is IEF-inspired. It uses information-sharing and safeguarding concepts such as policy-mediated release, enforcement, decision, administration, attributes, obligations, and evidence. This conceptual architecture does not require a later profile to claim full IEF compliance. A later profile may become more closely aligned with OMG IEF as the architecture matures. |