| Both sides previous revision Previous revision | |
| dido:01-fdis-ra:02-background-and-motivation:02-3-the-role-of-sbrm:02-3-1-reporting-semantics-as-a-governed-architectural-concern: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:02-3-1-reporting-semantics-as-a-governed-architectural-concern:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| In existing reporting environments, [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] governance is typically fragmented. Definitions may reside in narrative guidance, spreadsheets, regulatory text, taxonomies, or policy documents. Interpretive rules may be embedded in application code, configuration, or analytical procedures. Validation logic may evolve independently across agencies, vendors, tools, and reporting systems. | In existing reporting environments, [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] governance is typically fragmented. Definitions may reside in narrative guidance, spreadsheets, regulatory text, taxonomies, or policy documents. Interpretive rules may be embedded in application code, configuration, or analytical procedures. Validation logic may evolve independently across agencies, vendors, tools, and reporting systems. |
| |
| Even where organisations share syntactic standards, this fragmentation produces semantic drift, inconsistent interpretation, and erosion of comparability over time. Systems may process structurally similar information while applying different definitions, assumptions, rules, versions, or interpretive contexts. | Even where organizations share syntactic standards, this fragmentation produces semantic drift, inconsistent interpretation, and erosion of comparability over time. Systems may process structurally similar information while applying different definitions, assumptions, rules, versions, or interpretive contexts. |
| |
| The Standard Business Report Model (SBRM) addresses this failure mode by treating reporting semantics as first-class, governable artefacts. Rather than allowing systems to infer meaning indirectly from formats, software, taxonomies, or analytical conventions, SBRM makes semantic distinctions explicit and subject to identification, versioning, traceability, and governance. | The Standard Business Report Model (SBRM) addresses this failure mode by treating reporting semantics as first-class, governable artifacts. Rather than allowing systems to infer meaning indirectly from formats, software, taxonomies, or analytical conventions, SBRM makes semantic distinctions explicit and subject to identification, versioning, traceability, and governance. |
| |
| This treatment allows organisations to identify: | This treatment allows organizations to identify: |
| |
| * Which semantic definitions apply | * Which semantic definitions apply |