| Both sides previous revision Previous revision | |
| dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:01-fdis-ra:01-introduction:01-4-scope:01-4-2-out-of-scope:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| The exclusions defined in this section are deliberate. They preserve the role of the Federated Data Interpretation Systems Reference Architecture (FDIS-RA) as a technology-neutral, implementation-independent architectural framework focused on responsibilities for interpreting, validating, and comparing reported data in regulated reporting contexts, including financial data. | The exclusions defined in this section are deliberate. They preserve the role of the Federated Data Interpretation Systems Reference Architecture (FDIS-RA) as a technology-neutral, implementation-independent architectural framework focused on responsibilities for interpreting, validating, and comparing reported data in regulated reporting contexts, including financial data. |
| |
| This focus allows the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] to apply across organisational, jurisdictional, and regulatory boundaries without binding conforming architectures or implementations to particular technical ecosystems, products, platforms, or deployment models. | This focus allows the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] to apply across organizational, jurisdictional, and regulatory boundaries without binding conforming architectures or implementations to particular technical ecosystems, products, platforms, or deployment models. |
| |
| To preserve its platform-independent scope, FDIS-RA does not define specific technologies, products, operational procedures, deployment architectures, or implementation strategies. It does not prescribe software architectures, infrastructure configurations, security mechanisms, performance targets, or procurement models. | To preserve its platform-independent scope, FDIS-RA does not define specific technologies, products, operational procedures, deployment architectures, or implementation strategies. It does not prescribe software architectures, infrastructure configurations, security mechanisms, performance targets, or procurement models. |
| |
| FDIS-RA does not mandate modelling formalisms, [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] languages, rule engines, databases, artificial intelligence platforms, integration technologies, transport mechanisms, or vendor tooling environments. | FDIS-RA does not mandate modeling formalisms, [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] languages, rule engines, databases, artificial intelligence platforms, integration technologies, transport mechanisms, or vendor tooling environments. |
| |
| These exclusions do not prevent an implementation, profile, acquisition programme, or downstream [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Model (PSM)]] from selecting such technologies. They establish that those selections do not form part of the platform-independent architectural specification and do not, by themselves, demonstrate conformance with FDIS-RA. | These exclusions do not prevent an implementation, profile, acquisition programme, or downstream [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform-Specific Model (PSM)]] from selecting such technologies. They establish that those selections do not form part of the platform-independent architectural specification and do not, by themselves, demonstrate conformance with FDIS-RA. |