| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:05-semantics:01-kinds-of-semantics:start [2026/07/08 03:02] – ↷ 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, [[fxdemo:99_part_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 [[fxdemo:99_part_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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] into [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:rdf|RDF]], or [[fxdemo:99_part_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 [[fxdemo:99_part_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: |
| |
| * A terminology record expresses terminological semantics and supports vocabulary semantics | * A terminology record expresses terminological semantics and supports vocabulary semantics |
| * A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]] expresses conceptual semantics and provides [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] for ontological semantics | * A [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]] expresses conceptual semantics and provides [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] for ontological semantics |
| * An [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:rdf_graph|RDF graph]] expresses graph semantics and represents selected ontological semantics | * An [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf_graph|RDF graph]] expresses graph semantics and represents selected ontological semantics |
| * An [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:owl|OWL]] [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] expresses OWL semantics and selected ontological semantics | * An [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]] [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]] expresses OWL semantics and selected ontological semantics |
| * A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:schema|schema]] expresses schema semantics, datatype semantics, and selected type semantics | * A [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]] expresses schema semantics, datatype semantics, and selected type semantics |
| * A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:report|report]] expresses report semantics and includes schema, datatype, rule, and policy semantics | * A [[dido:99_annexes:annex-b-terms-and-definitions:r:report|report]] expresses report semantics and includes schema, datatype, rule, and policy semantics |
| * A conformance test expresses conformance semantics and validates rule, lifecycle, schema, or report semantics | * A conformance test expresses conformance semantics and validates rule, lifecycle, schema, or report semantics |
| * Implementation logic expresses implementation semantics when it preserves [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to governed semantic sources | * Implementation logic expresses implementation semantics when it preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to governed semantic sources |
| |
| A project selects the semantic concerns that matter for its scope, risk, stakeholders, and implementation context. A small demonstration often uses terminology, conceptual semantics, schema semantics, and implementation semantics. A governed financial reporting system often uses report semantics, policy semantics, rule semantics, conformance semantics, lifecycle semantics, type semantics, datatype semantics, and traceability to [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:f:fibo|FIBO]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:sbrm|SBRM]], or other authoritative sources. | A project selects the semantic concerns that matter for its scope, risk, stakeholders, and implementation context. A small demonstration often uses terminology, conceptual semantics, schema semantics, and implementation semantics. A governed financial reporting system often uses report semantics, policy semantics, rule semantics, conformance semantics, lifecycle semantics, type semantics, datatype semantics, and traceability to [[dido:99_annexes:annex-b-terms-and-definitions:f:fibo|FIBO]], [[dido:99_annexes:annex-b-terms-and-definitions:s:sbrm|SBRM]], or other authoritative sources. |
| |
| The taxonomy, therefore, provides a map of semantic concerns, not a required work breakdown structure. | The taxonomy, therefore, provides a map of semantic concerns, not a required work breakdown structure. |