| Next revision | Previous revision |
| dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-1-specific-implementations:start [2026/07/10 13:02] – created nick_dido | dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:01-4-2-1-specific-implementations:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[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]] |
| |
| This specification defines architectural responsibilities and governance boundaries, not executable systems or concrete implementations. It does not define reference implementations, deployment configurations, runtime architectures, or technology-specific realisations of the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. | This specification defines architectural responsibilities and governance boundaries, not executable systems or concrete implementations. It does not define reference implementations, deployment configurations, runtime architectures, or technology-specific realisations of the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. |
| |
| Accordingly, FDIS-RA does not specify or endorse particular [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] representation languages, reasoning engines, rule engines, artificial intelligence models, tooling frameworks, or other implementation mechanisms used to realise the architectural responsibilities defined by this specification. | Accordingly, FDIS-RA does not specify or endorse particular [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] representation languages, reasoning engines, rule engines, artificial intelligence models, tooling frameworks, or other implementation mechanisms used to realize the architectural responsibilities defined by this specification. |
| |
| Domain-specific standards bodies, system architects, acquisition authorities, and implementers retain responsibility for selecting implementation mechanisms appropriate to their operational, jurisdictional, regulatory, and technical contexts. Such selections do not alter the architectural responsibilities, governance boundaries, or conformance obligations defined by FDIS-RA. | Domain-specific standards bodies, system architects, acquisition authorities, and implementers retain responsibility for selecting implementation mechanisms appropriate to their operational, jurisdictional, regulatory, and technical contexts. Such selections do not alter the architectural responsibilities, governance boundaries, or conformance obligations defined by FDIS-RA. |
| |
| The exclusion of implementation artefacts does not preclude the use of formal architectural or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] models to express, refine, analyse, or assess the Reference Architecture at a conceptual or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform-Independent Model (PIM)]] level. | The exclusion of implementation artifacts does not preclude the use of formal architectural or [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] models to express, refine, analyze, or assess the Reference Architecture at a conceptual or [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform-Independent Model (PIM)]] level. |
| |
| Downstream [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Models (PSMs)]], implementation profiles, reference implementations, and product architectures may realise the responsibilities defined by FDIS-RA, but those artefacts remain outside the scope of this specification. | Downstream [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Models (PSMs)]], implementation profiles, reference implementations, and product architectures may realize the responsibilities defined by FDIS-RA, but those artifacts remain outside the scope of this specification. |
| |
| ---- | ---- |