dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-4-infrastructure-and-platform-standards:start

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-4-infrastructure-and-platform-standards: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-2-out-of-scope:01-4-2-4-infrastructure-and-platform-standards:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
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]]
  
-Standards and specifications concerned solely with networking, transport, operating systems, or underlying infrastructure, including TCP/IP and related protocols, fall outside the scope of this [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].+Standards and specifications concerned solely with networking, transport, operating systems, or underlying infrastructure, including TCP/IP and related protocols, fall outside the scope of this [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
  
 FDIS-RA considers such standards only to the extent that they enable, convey, protect, or support an architectural responsibility defined as in scope. Their inclusion within an implementation does not make them part of the platform-independent architectural specification. FDIS-RA considers such standards only to the extent that they enable, convey, protect, or support an architectural responsibility defined as in scope. Their inclusion within an implementation does not make them part of the platform-independent architectural specification.
Line 9: Line 9:
 FDIS-RA does not define infrastructure configurations, platform baselines, deployment environments, operational topologies, transport protocols, message brokers, network architectures, or runtime communication mechanisms. FDIS-RA does not define infrastructure configurations, platform baselines, deployment environments, operational topologies, transport protocols, message brokers, network architectures, or runtime communication mechanisms.
  
-Implementations and downstream [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Models (PSMs)]] may select and constrain infrastructure and platform standards based on their operational, security, jurisdictional, and performance requirements, provided that these choices preserve the architectural responsibilities and governed boundaries defined by FDIS-RA.+Implementations and downstream [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Models (PSMs)]] may select and constrain infrastructure and platform standards based on their operational, security, jurisdictional, and performance requirements, provided that these choices preserve the architectural responsibilities and governed boundaries defined by FDIS-RA.
  
 ---- ----
  • dido/01-fdis-ra/01-introduction/01-4-scope/01-4-2-out-of-scope/01-4-2-4-infrastructure-and-platform-standards/start.1783793232.txt.gz
  • Last modified: 2026/07/11 11:07
  • by nick_dido