| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:01-fdis-ra:start [2026/07/10 11:54] – nick_dido | dido:01-fdis-ra:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| The Federated Data Interpretation Systems Reference Architecture (FDIS-RA) is a proposed response to the [[dido:00-sip-ra:start|Structured Information Processing Reference Architecture (SIP-RA) Request for Proposal]]. | The Federated Data Interpretation Systems Reference Architecture (FDIS-RA) is a proposed response to the [[dido:00-sip-ra:start|Structured Information Processing Reference Architecture (SIP-RA) Request for Proposal]]. |
| |
| FDIS-RA defines a platform-independent Reference Architecture for the governed interpretation, validation, comparison, and analysis of structured information artifacts in regulated and mission-critical environments. The architecture applies the separation of data, structure, semantics, and interpretation required by SIP-RA to federated systems that process reported information across organisational, jurisdictional, and technological boundaries. | FDIS-RA defines a platform-independent Reference Architecture for the governed interpretation, validation, comparison, and analysis of structured information artifacts in regulated and mission-critical environments. The architecture applies the separation of data, structure, semantics, and interpretation required by SIP-RA to federated systems that process reported information across organizational, jurisdictional, and technological boundaries. |
| |
| The proposed architecture defines governed processing flows, explicit architectural boundaries, version-controlled interfaces, semantic and interpretive lifecycle controls, and traceability mechanisms that preserve evidentiary integrity and support reproducible interpretation. FDIS-RA provides the architectural response through which the SIP-RA requirements are realised for federated data interpretation systems without prescribing specific implementation technologies, products, transport mechanisms, or deployment topologies. | The proposed architecture defines governed processing flows, explicit architectural boundaries, version-controlled interfaces, semantic and interpretive lifecycle controls, and traceability mechanisms that preserve evidentiary integrity and support reproducible interpretation. FDIS-RA provides the architectural response through which the SIP-RA requirements are realized for federated data interpretation systems without prescribing specific implementation technologies, products, transport mechanisms, or deployment topologies. |
| |
| ===== Table of Contents ===== | ===== Table of Contents ===== |
| * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-4-semantic-representations:start|2.4.4 Semantic Representations]] | * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-4-semantic-representations:start|2.4.4 Semantic Representations]] |
| * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-5-rules-and-validation:start|2.4.5 Rules and Validation]] | * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-5-rules-and-validation:start|2.4.5 Rules and Validation]] |
| * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-6-the-architectural-gap:start|2.4.6 The Architectural Gap]] | * [[dido:01-fdis-ra:02-background-and-motivation:02-4-existing-functional-capabilities-in-reporting-systems:02-4-5-rules-and-validation:start|2.4.6 The Architectural Gap]] |
| * [[dido:01-fdis-ra:02-background-and-motivation:02-5-why-a-reference-architecture-is-needed:start|2.5 Why a Reference Architecture Is Needed]] | * [[dido:01-fdis-ra:02-background-and-motivation:02-5-why-a-reference-architecture-is-needed:start|2.5 Why a Reference Architecture Is Needed]] |
| * [[dido:01-fdis-ra:02-background-and-motivation:02-5-why-a-reference-architecture-is-needed:02-5-1-semantic-drift-over-time:start|2.5.1 Semantic Drift over Time]] | * [[dido:01-fdis-ra:02-background-and-motivation:02-5-why-a-reference-architecture-is-needed:02-5-1-semantic-drift-over-time:start|2.5.1 Semantic Drift over Time]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-3-relationship-to-omg-architectures-and-standards:03-3-2-alignment-with-omg-model-driven-architecture:start|3.3.2 Alignment with OMG Model-Driven Architecture (MDA)]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-3-relationship-to-omg-architectures-and-standards:03-3-2-alignment-with-omg-model-driven-architecture:start|3.3.2 Alignment with OMG Model-Driven Architecture (MDA)]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-3-relationship-to-omg-architectures-and-standards:03-3-3-non-overlap-with-product-platform-or-implementation-architectures:start|3.3.3 Non-Overlap with Product, Platform, or Implementation Architectures]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-3-relationship-to-omg-architectures-and-standards:03-3-3-non-overlap-with-product-platform-or-implementation-architectures:start|3.3.3 Non-Overlap with Product, Platform, or Implementation Architectures]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:start|3.4 Normative Artefact Types]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:start|3.4 Normative Artifact Types]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:03-4-1-guidance-statements:start|3.4.1 Guidance Statements (G)]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:03-4-1-guidance-statements:start|3.4.1 Guidance Statements (G)]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:03-4-2-interface-definitions:start|3.4.2 Interface Definitions (I)]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:03-4-2-interface-definitions:start|3.4.2 Interface Definitions (I)]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:03-4-3-distinguishing-obligation-from-structure:start|3.4.3 Distinguishing Obligation from Structure]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:03-4-3-distinguishing-obligation-from-structure:start|3.4.3 Distinguishing Obligation from Structure]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:03-4-4-illustrative-examples:start|3.4.4 Illustrative Examples]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:03-4-4-illustrative-examples:start|3.4.4 Illustrative Examples]] |
| * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artefact-types:03-4-5-section-scoped-normative-artefacts:start|3.4.5 Section-Scoped Normative Artefacts]] | * [[dido:01-fdis-ra:03-fdis-reference-architecture:03-4-normative-artifact-types:03-4-5-section-scoped-normative-artifacts:start|3.4.5 Section-Scoped Normative Artifacts]] |
| * [[dido:01-fdis-ra:04-architectural-overview:start|4. Architectural Overview]] | * [[dido:01-fdis-ra:04-architectural-overview:start|4. Architectural Overview]] |
| * [[dido:01-fdis-ra:04-architectural-overview:04-1-architectural-flow-and-boundary-model:start|4.1 Architectural Flow and Boundary Model]] | * [[dido:01-fdis-ra:04-architectural-overview:04-1-architectural-flow-and-boundary-model:start|4.1 Architectural Flow and Boundary Model]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-1-data-plane-components:05-1-6-validation-conformance-and-assessment:start|5.1.6 Validation, Conformance, and Assessment]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-1-data-plane-components:05-1-6-validation-conformance-and-assessment:start|5.1.6 Validation, Conformance, and Assessment]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-1-data-plane-components:05-1-7-analysis-reporting-and-user-interaction:start|5.1.7 Analysis, Reporting, and User Interaction]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-1-data-plane-components:05-1-7-analysis-reporting-and-user-interaction:start|5.1.7 Analysis, Reporting, and User Interaction]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realisation-components:start|5.2 Boundary Realisation Components]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realization-components:start|5.2 Boundary Realization Components]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realisation-components:05-2-1-ports:start|5.2.1 Ports]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realization-components:05-2-1-ports:start|5.2.1 Ports]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realisation-components:05-2-2-port-interfaces:start|5.2.2 Port Interfaces]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realization-components:05-2-2-port-interfaces:start|5.2.2 Port Interfaces]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realisation-components:05-2-3-adapters:start|5.2.3 Adapters]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realization-components:05-2-3-adapters:start|5.2.3 Adapters]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realisation-components:05-2-4-adapter-realisation-pattern:start|5.2.4 Adapter Realisation Pattern]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-2-boundary-realization-components:05-2-4-adapter-realization-pattern:start|5.2.4 Adapter Realization Pattern]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-3-control-plane-components:start|5.3 Control Plane Components]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-3-control-plane-components:start|5.3 Control Plane Components]] |
| * [[dido:01-fdis-ra:05-core-architectural-components:05-3-control-plane-components:05-3-1-semantic-governance-and-version-context-management:start|5.3.1 Semantic Governance and Version Context Management]] | * [[dido:01-fdis-ra:05-core-architectural-components:05-3-control-plane-components:05-3-1-semantic-governance-and-version-context-management:start|5.3.1 Semantic Governance and Version Context Management]] |
| * [[dido:01-fdis-ra:09-benefits-and-expected-outcomes:09-4-ai-use-with-bounded-authority:start|9.4 AI Use with Bounded Authority]] | * [[dido:01-fdis-ra:09-benefits-and-expected-outcomes:09-4-ai-use-with-bounded-authority:start|9.4 AI Use with Bounded Authority]] |
| * [[dido:01-fdis-ra:09-benefits-and-expected-outcomes:09-5-long-term-semantic-stability:start|9.5 Long-Term Semantic Stability]] | * [[dido:01-fdis-ra:09-benefits-and-expected-outcomes:09-5-long-term-semantic-stability:start|9.5 Long-Term Semantic Stability]] |
| * [[dido:01-fdis-ra:10-summary-and-next-steps:start|10. Summary and Next Steps]] | * [[dido:01-fdis-ra:10-summary-and-next-steps:start|10. Summary and Next Steps]] |
| * [[dido:01-fdis-ra:11-references:start|11. References]] | * [[dido:99_annexes:annex-c-references:start|11. References]] |
| |
| --- | ---- |
| | ===== Table of Contents ===== |
| | |
| | {{indexmenu>dido:01-fdis-ra#1|js navbar nocookie maxjs#3 id#fdis_ra_toc_nav}} |
| | |
| | ---- |
| |
| <WRAP centeralign> | <WRAP centeralign> |