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:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-3-enforcement-policy:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_didodido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-3-enforcement-policy:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 3: Line 3:
 [[dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:start|Return to 1.4.2 Out of Scope]] [[dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:start|Return to 1.4.2 Out of Scope]]
  
-Legal, regulatory, or procedural enforcement mechanisms, including compliance determinations, penalties, adjudication processes, and agency-specific policy decisions, fall outside the scope of this [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].+Legal, regulatory, or procedural enforcement mechanisms, including compliance determinations, penalties, adjudication processes, and agency-specific policy decisions, fall outside the scope of this [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
  
-FDIS-RA supports transparency, traceability, auditability, and evidentiary reconstruction in environments where enforcement decisions occur. It does not prescribe, automate, authorise, or substitute for enforcement actions, regulatory determinations, adjudicative decisions, or policy judgments.+FDIS-RA supports transparency, traceability, auditability, and evidentiary reconstruction in environments where enforcement decisions occur. It does not prescribe, automate, authorize, or substitute for enforcement actions, regulatory determinations, adjudicative decisions, or policy judgments.
  
-The Federated Data Interpretation Systems Reference Architecture addresses the architectural handling of [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] interpretation, validation, provenance, and comparability. It does not define legal standards of proof, evidentiary thresholds, statutory obligations, compliance criteria, enforcement procedures, or the legal effect of an interpretive result.+The Federated Data Interpretation Systems Reference Architecture addresses the architectural handling of [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] interpretation, validation, provenance, and comparability. It does not define legal standards of proof, evidentiary thresholds, statutory obligations, compliance criteria, enforcement procedures, or the legal effect of an interpretive result.
  
-Appropriate statutory, regulatory, judicial, and administrative authorities retain responsibility for these matters. An FDIS-aligned system may provide information to support an authorised decision-maker, but it does not acquire the authority assigned to that decision-maker.+Appropriate statutory, regulatory, judicial, and administrative authorities retain responsibility for these matters. An FDIS-aligned system may provide information to support an authorized decision-maker, but it does not acquire the authority assigned to that decision-maker.
  
 ---- ----
  • dido/01-fdis-ra/01-introduction/01-4-scope/01-4-2-out-of-scope/01-4-2-3-enforcement-policy/start.1783793455.txt.gz
  • Last modified: 2026/07/11 11:10
  • by nick_dido