| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:05-semantics:01-kinds-of-semantics:03-datatype-semantics [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido | dido:05-semantics:01-kinds-of-semantics:03-datatype-semantics [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Datatype Semantics ====== | ====== Datatype Semantics ====== |
| |
| [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| Datatype semantics defines meaning through the value space, permitted representation, and permitted operations associated with a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:d:datatype|datatype]]. | Datatype semantics defines meaning through the value space, permitted representation, and permitted operations associated with a [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype|datatype]]. |
| |
| A datatype constrains how a data value appears and how systems process that value. Datatype semantics applies to primitive datatypes such as ''string'', ''integer'', ''decimal'', ''boolean'', and ''date'', and to constrained datatypes such as currency codes, jurisdiction codes, identifiers, date formats, numeric ranges, and enumerated values. | A datatype constrains how a data value appears and how systems process that value. Datatype semantics applies to primitive datatypes such as ''string'', ''integer'', ''decimal'', ''boolean'', and ''date'', and to constrained datatypes such as currency codes, jurisdiction codes, identifiers, date formats, numeric ranges, and enumerated values. |
| |
| Datatype semantics differs from [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:type|type]] semantics. A datatype constrains representation. A type identifies the semantic category of the thing represented. For example, ''tradeDate'', ''settlementDate'', ''effectiveDate'', and ''terminationDate'' use the same date datatype, but each term has a different domain meaning. | Datatype semantics differs from [[dido:99_annexes:annex-b-terms-and-definitions:t:type|type]] semantics. A datatype constrains representation. A type identifies the semantic category of the thing represented. For example, ''tradeDate'', ''settlementDate'', ''effectiveDate'', and ''terminationDate'' use the same date datatype, but each term has a different domain meaning. |
| |
| Datatype semantics also differs from [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] as a whole. A datatype contributes to meaning by constraining values and operations, but a datatype does not establish the full domain meaning of a data item. Domain meaning comes from the associated term, schema, type system, conceptual model, rule, report, ontology, or other authoritative semantic source. | Datatype semantics also differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]] as a whole. A datatype contributes to meaning by constraining values and operations, but a datatype does not establish the full domain meaning of a data item. Domain meaning comes from the associated term, schema, type system, conceptual model, rule, report, ontology, or other authoritative semantic source. |
| |
| Datatype semantic content includes: | Datatype semantic content includes: |
| * Traceability to the domain meaning | * Traceability to the domain meaning |
| |
| A governed architecture preserves [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from datatype semantics to the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:s:schema|schema]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:type_system|type system]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], business rule, or other semantic source that establishes the intended interpretation of the data value. | A governed architecture preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from datatype semantics to the [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]], [[dido:99_annexes:annex-b-terms-and-definitions:t:type_system|type system]], [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], business rule, or other semantic source that establishes the intended interpretation of the data value. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| DIDO Solutions usage, informed by datatype, schema-language, database, modelling, and type-system practice. | DIDO Solutions usage, informed by datatype, schema-language, database, modeling, and type-system practice. |
| |
| ===== Note ===== | ===== Note ===== |