Differences

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

--- dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-2-product-architectures:start [2026/07/10 13:08] – created nick_dido
+++ dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-2-product-architectures: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]]
-Vendor-specific solutions, proprietary platforms, and product-level design decisions, including packaging, deployment topology, and vendor-specific configuration models, fall outside the scope of this [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+Vendor-specific solutions, proprietary platforms, and product-level design decisions, including packaging, deployment topology, and vendor-specific configuration models, fall outside the scope of this [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 FDIS-RA does not endorse, evaluate, certify, or constrain any particular product, platform, service, vendor, or commercial offering. The use of a particular product or platform does not, by itself, demonstrate alignment or conformance with FDIS-RA.
-Product architectures may realise the architectural responsibilities, boundaries, interfaces, and governance mechanisms defined by FDIS-RA. Product-specific design and implementation decisions remain the responsibility of vendors, system architects, integrators, acquisition authorities, and implementing organisations.
+Product architectures may realize the architectural responsibilities, boundaries, interfaces, and governance mechanisms defined by FDIS-RA. Product-specific design and implementation decisions remain the responsibility of vendors, system architects, integrators, acquisition authorities, and implementing organizations.
 ----