dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-The [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL NOT treat metadata release or aggregate release as authorisation to release full transaction detail.+The [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL NOT treat metadata release or aggregate release as authorization to release full transaction detail.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Metadata release, aggregate release, and full transaction detail release represent different release scopes and sensitivity implications. Authorising one release form does not authorise another release form with greater detail or different risk.+Metadata release, aggregate release, and full transaction detail release represent different release scopes and sensitivity implications. Authorizing one release form does not authorize another release form with greater detail or different risk.
  
 This requirement prevents the release scope from expanding and preserves the conceptual separation among metadata, aggregate, and full-detail releases. This requirement prevents the release scope from expanding and preserves the conceptual separation among metadata, aggregate, and full-detail releases.
Line 26: Line 26:
   * Aggregate release   * Aggregate release
   * Full transaction detail release   * Full transaction detail release
-  * Release authorisation+  * Release authorization
   * Release scope control   * Release scope control
  
 ===== Verification ===== ===== Verification =====
  
-Verification SHALL confirm that the Policy and Release Plane does not treat metadata release or aggregate release as authorisation to release full transaction detail.+Verification SHALL confirm that the Policy and Release Plane does not treat metadata release or aggregate release as authorization to release full transaction detail.
  
 Verification activities include review checks confirming that: Verification activities include review checks confirming that:
Line 37: Line 37:
   * Metadata release remains distinct from the full transaction detail release   * Metadata release remains distinct from the full transaction detail release
   * Aggregate release remains distinct from the full transaction detail release   * Aggregate release remains distinct from the full transaction detail release
-  * Release authorisation identifies the authorised release scope +  * Release authorization identifies the authorized release scope 
-  * Full transaction detail release requires explicit release authorisation+  * Full transaction detail release requires explicit release authorization
  
 ===== Traceability ===== ===== Traceability =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-5-015/start.1783799875.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido