| Both sides previous revision Previous revision | |
| dido:05-semantics:01-kinds-of-semantics:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:05-semantics:01-kinds-of-semantics:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ===== Overview ===== | ===== Overview ===== |
| |
| The taxonomy of semantics identifies where meaning appears in DIDO Solutions work. The taxonomy supports analysis, discussion, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]], and governance. It does not require every project to create a separate artefact for every kind of [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]]. | The taxonomy of semantics identifies where meaning appears in DIDO Solutions work. The taxonomy supports analysis, discussion, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]], and governance. It does not require every project to create a separate artifact for every kind of [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]]. |
| |
| The taxonomy helps architects identify which semantic concerns apply to a given project, which artefacts express those concerns, and which source governs the intended meaning. | The taxonomy helps architects identify which semantic concerns apply to a given project, which artifacts express those concerns, and which source governs the intended meaning. |
| |
| DIDO Solutions uses this taxonomy to prevent the common collapse of [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] into [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf|RDF]], or [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]]. Those artefacts and technologies play important roles, but they represent only some forms of semantic content. | DIDO Solutions uses this taxonomy to prevent the common collapse of [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] into [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf|RDF]], or [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]]. Those artifacts and technologies play important roles, but they represent only some forms of semantic content. |
| |
| The taxonomy provides a classification scheme for discussing, tracing, governing, and implementing meaning across DIDO Solutions efforts. It does not define separate project phases or mandatory deliverables. | The taxonomy provides a classification scheme for discussing, tracing, governing, and implementing meaning across DIDO Solutions efforts. It does not define separate project phases or mandatory deliverables. |
| ===== Semantic Overlap ===== | ===== Semantic Overlap ===== |
| |
| Semantic concerns often overlap. A single artefact expresses several kinds of semantics at the same time. For example, a [[dido:99_annexes:annex-b-terms-and-definitions:j:json_schema|JSON Schema]] for an FX trade message expresses schema semantics through field structure, datatype semantics through date and decimal constraints, type semantics through domain-specific identifiers, and rule semantics through validation constraints. | Semantic concerns often overlap. A single artifact expresses several kinds of semantics at the same time. For example, a [[dido:99_annexes:annex-b-terms-and-definitions:j:json_schema|JSON Schema]] for an FX trade message expresses schema semantics through field structure, datatype semantics through date and decimal constraints, type semantics through domain-specific identifiers, and rule semantics through validation constraints. |
| |
| Examples of overlap include: | Examples of overlap include: |