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-1-in-scope:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_didodido:01-fdis-ra:01-introduction:01-4-scope:01-4-1-in-scope: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:start|Return to 1.4 Scope]] [[dido:01-fdis-ra:01-introduction:01-4-scope:start|Return to 1.4 Scope]]
  
-This [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] defines architectural responsibilities for interpreting, governing, and supporting the controlled evolution of meaning in regulated data environments. It addresses [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] representation, interpretation logic, validation, provenance, and comparability across systems and reporting periods.+This [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] defines architectural responsibilities for interpreting, governing, and supporting the controlled evolution of meaning in regulated data environments. It addresses [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] representation, interpretation logic, validation, provenance, and comparability across systems and reporting periods.
  
-The Reference Architecture addresses these concerns at the architectural level. It defines responsibilities, boundaries, interactions, governance mechanisms, and lifecycle controls without prescribing the technologies, products, or implementation mechanisms used to realise them.+The Reference Architecture addresses these concerns at the architectural level. It defines responsibilities, boundaries, interactions, governance mechanisms, and lifecycle controls without prescribing the technologies, products, or implementation mechanisms used to realize them.
  
 The Reference Architecture excludes standards that concern only networking, transport, operating systems, or infrastructure, except where such standards support or convey information associated with an in-scope architectural responsibility. The Reference Architecture excludes standards that concern only networking, transport, operating systems, or infrastructure, except where such standards support or convey information associated with an in-scope architectural responsibility.
  • dido/01-fdis-ra/01-introduction/01-4-scope/01-4-1-in-scope/start.1783793232.txt.gz
  • Last modified: 2026/07/11 11:07
  • by nick_dido