| Both sides previous revision Previous revision | |
| dido:05-semantics:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:05-semantics:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ===== Purpose ===== | ===== Purpose ===== |
| |
| This section introduces [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] as a general DIDO Solutions topic. It explains why semantics matters, how semantics differs from structure and interpretation, and how different semantic artefacts express meaning across DIDO Solutions efforts. | This section introduces [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] as a general DIDO Solutions topic. It explains why semantics matters, how semantics differs from structure and interpretation, and how different semantic artifacts express meaning across DIDO Solutions efforts. |
| |
| The section also identifies several kinds of semantics that occur in architecture, modelling, reporting, governance, and implementation work. | The section also identifies several kinds of semantics that occur in architecture, modeling, reporting, governance, and implementation work. |
| |
| ===== Overview ===== | ===== Overview ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] addresses meaning within a defined context. In architecture, semantics applies to designations, expressions, model elements, data items, rules, statements, events, messages, reports, schemas, types, ontologies, and implementation artefacts. | [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] addresses meaning within a defined context. In architecture, semantics applies to designations, expressions, model elements, data items, rules, statements, events, messages, reports, schemas, types, ontologies, and implementation artifacts. |
| |
| Semantics provides the basis for shared interpretation across organisations, systems, technologies, jurisdictions, and governance processes. Without semantic discipline, systems exchange data successfully while participants still disagree about what the data means. | Semantics provides the basis for shared interpretation across organizations, systems, technologies, jurisdictions, and governance processes. Without semantic discipline, systems exchange data successfully while participants still disagree about what the data means. |
| |
| DIDO Solutions treats semantics as meaning first, structured domain commitment second, and implementation technology third. [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|Ontologies]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf|RDF]], [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]], schemas, type systems, vocabularies, business rules, reports, and executable logic all express semantic content in different ways. No single artefact or technology defines the full scope of semantics. | DIDO Solutions treats semantics as meaning first, structured domain commitment second, and implementation technology third. [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|Ontologies]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf|RDF]], [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]], schemas, type systems, vocabularies, business rules, reports, and executable logic all express semantic content in different ways. No single artifact or technology defines the full scope of semantics. |
| |
| ===== Semantics, Structure, and Interpretation ===== | ===== Semantics, Structure, and Interpretation ===== |
| ===== Why Semantics Matters ===== | ===== Why Semantics Matters ===== |
| |
| Semantics matters because DIDO Solutions' work spans distributed organisations, financial-domain concepts, standards activities, regulatory contexts, implementation technologies, and governance responsibilities. | Semantics matters because DIDO Solutions' work spans distributed organizations, financial-domain concepts, standards activities, regulatory contexts, implementation technologies, and governance responsibilities. |
| |
| Semantic discipline supports: | Semantic discipline supports: |
| |
| * Shared understanding across organisations | * Shared understanding across organizations |
| * Consistent use of terms and definitions | * Consistent use of terms and definitions |
| * Traceability from concepts to implementation artefacts | * Traceability from concepts to implementation artifacts |
| * Alignment between conceptual models, schemas, reports, and code | * Alignment between conceptual models, schemas, reports, and code |
| * Validation of messages, events, reports, and lifecycle states | * Validation of messages, events, reports, and lifecycle states |