| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:01-fdis-ra:02-background-and-motivation:02-3-the-role-of-sbrm:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:01-fdis-ra:02-background-and-motivation:02-3-the-role-of-sbrm:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[dido:01-fdis-ra:02-background-and-motivation:start|Return to 2. Background and Motivation]] | [[dido:01-fdis-ra:02-background-and-motivation:start|Return to 2. Background and Motivation]] |
| |
| The challenges identified in [[dido:01-fdis-ra:02-background-and-motivation:02-1-international-context-and-applicability:start|Section 2.1]] and [[dido:01-fdis-ra:02-background-and-motivation:02-2-the-fdta-context:start|Section 2.2]] are not primarily problems of data availability or syntactic standardisation. They are problems of interpretive authority: determining what reported information means, which definitions apply, when those definitions apply, and which analytical, supervisory, or regulatory purpose governs the interpretation. | The challenges identified in [[dido:01-fdis-ra:02-background-and-motivation:02-1-international-context-and-applicability:start|Section 2.1]] and [[dido:01-fdis-ra:02-background-and-motivation:02-2-the-fdta-context:start|Section 2.2]] are not primarily problems of data availability or syntactic standardization. They are problems of interpretive authority: determining what reported information means, which definitions apply, when those definitions apply, and which analytical, supervisory, or regulatory purpose governs the interpretation. |
| |
| The Standard Business Report Model (SBRM), developed within the Object Management Group (OMG), directly addresses this problem space. SBRM does not define how systems transmit, store, or transport data. It addresses how systems characterise, distinguish, and govern reported information [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantically]] across systems and over time [R10, R11]. | The [[dido:99_annexes:annex-b-terms-and-definitions:s:sbrm|Standard Business Report Model (SBRM)]], developed within the [[dido:99_annexes:annex-b-terms-and-definitions:o:omg|Object Management Group (OMG)]], directly addresses this problem space. SBRM does not define how systems transmit, store, or transport data. It addresses how systems characterize, distinguish, and govern reported information [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantically]] across systems and over time [[dido:99_annexes:annex-c-references:r10-reference-architecture-description|[R10]]], [[dido:99_annexes:annex-c-references:r11-standard-business-report-model-specification|[R11]]]. |
| |
| Reporting formats, schemas, and exchange standards define structural and syntactic arrangements. SBRM defines semantic distinctions that implementations might otherwise leave implicit, apply inconsistently, or embed within software, configuration, analytical procedures, or tool-specific logic. | Reporting formats, schemas, and exchange standards define structural and syntactic arrangements. SBRM defines semantic distinctions that implementations might otherwise leave implicit, apply inconsistently, or embed within software, configuration, analytical procedures, or tool-specific logic. |
| |
| * How a reporting party makes an assertion | * How a reporting party makes an assertion |
| * How a system derives an observation from a source artefact | * How a system derives an observation from a source artifact |
| * How an interpretation applies governed definitions, rules, and contextual assumptions | * How an interpretation applies governed definitions, rules, and contextual assumptions |
| * How a system distinguishes reported, observed, and interpreted information | * How a system distinguishes reported, observed, and interpreted information |
| * How an organisation evaluates interpretive results within a governed semantic context | * How an organization evaluates interpretive results within a governed semantic context |
| |
| These distinctions support the separation of evidence, observation, and interpretation required by FDIS-RA. They also provide a semantic foundation for traceability, auditability, reinterpretation, comparison, and controlled evolution across reporting periods and independently developed systems. | These distinctions support the separation of evidence, observation, and interpretation required by the [[dido:99_annexes:annex-b-terms-and-definitions:f:fdis-ra|Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]. They also provide a semantic foundation for traceability, auditability, reinterpretation, comparison, and controlled evolution across reporting periods and independently developed systems. |
| |
| SBRM does not, by itself, define the complete architecture through which organisations operationalise these distinctions. FDIS-RA places SBRM within a broader [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] that defines architectural responsibilities, interfaces, governance boundaries, version controls, and lifecycle mechanisms for regulated data interpretation. | SBRM does not, by itself, define the complete architecture through which organizations operationalise these distinctions. FDIS-RA places SBRM within a broader [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] that defines architectural responsibilities, interfaces, governance boundaries, version controls, and lifecycle mechanisms for regulated data interpretation. |
| |
| ===== Contents ===== | ===== Contents ===== |
| {{indexmenu>dido:01-fdis-ra:02-background-and-motivation:02-3-the-role-of-sbrm#1|js navbar nocookie maxjs#1 id#fdis_ra_02_3_role_of_sbrm_nav}} | {{indexmenu>dido:01-fdis-ra:02-background-and-motivation:02-3-the-role-of-sbrm#1|js navbar nocookie maxjs#1 id#fdis_ra_02_3_role_of_sbrm_nav}} |
| |
| ---- | --- |
| |
| <WRAP centeralign> | <WRAP centeralign> |