| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:r:report [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:r:report [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| A report communicates structured information about a subject, event, condition, activity, obligation, result, or state of affairs. In business and regulatory contexts, a report does more than present information to a human reader. A report also provides facts that another person, organisation, system, regulator, auditor, or process can interpret, validate, compare, analyse, or act upon. | A report communicates structured information about a subject, event, condition, activity, obligation, result, or state of affairs. In business and regulatory contexts, a report does more than present information to a human reader. A report also provides facts that another person, organization, system, regulator, auditor, or process can interpret, validate, compare, analyze, or act upon. |
| |
| The Standard Business Report Model (SBRM) treats a report as a structured information artefact. A report contains facts. Dimensions distinguish one fact from another. A report model explains what is in the report and its organisation. | The Standard Business Report Model (SBRM) treats a report as a structured information artifact. A report contains facts. Dimensions distinguish one fact from another. A report model explains what is in the report and its organization. |
| |
| This treatment separates the report from a presentation format. A report may appear as a form, a spreadsheet, a PDF, an XBRL filing, a JSON document, an RDF graph, a database extract, a dashboard, or a message set. The report remains the information artefact. The format provides one realisation of that artefact. | This treatment separates the report from a presentation format. A report may appear as a form, a spreadsheet, a PDF, an XBRL filing, a JSON document, an RDF graph, a database extract, a dashboard, or a message set. The report remains the information artifact. The format provides one realization of that artifact. |
| |
| In DIDO Solutions' work, a report should have traceable semantics, structure, facts, dimensions, rules, constraints, and validation logic when the report supports governance, regulatory interpretation, audit, conformance, or automated processing. | In DIDO Solutions' work, a report should have traceable semantics, structure, facts, dimensions, rules, constraints, and validation logic when the report supports governance, regulatory interpretation, audit, conformance, or automated processing. |
| ===== Definition ===== | ===== Definition ===== |
| |
| //structured information artefact that contains reported facts distinguished by dimensions within a defined reporting context// | //structured information artifact that contains reported facts distinguished by dimensions within a defined reporting context// |
| |
| ===== Source ===== | ===== Source ===== |
| |
| OMG Standard Business Report Model (SBRM), Version 1.0 Beta 1; specialised for use in the FX Demo Reference Architecture. | OMG Standard Business Report Model (SBRM), Version 1.0 Beta 1; specialized for use in the FX Demo Reference Architecture. |
| |
| ===== Note ===== | ===== Note ===== |
| |
| A report is not equivalent to its presentation format. A PDF, spreadsheet, web page, XBRL instance, JSON document, or RDF graph may realise a report, but the report consists of the reported information, its organisation, its facts, its dimensions, and its governing report model. | A report is not equivalent to its presentation format. A PDF, spreadsheet, web page, XBRL instance, JSON document, or RDF graph may realize a report, but the report consists of the reported information, its organization, its facts, its dimensions, and its governing report model. |
| |
| ===== Example ===== | ===== Example ===== |