| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:05-semantics:01-kinds-of-semantics:14-type-semantics [2026/07/08 03:02] – ↷ Page moved from dido:01-semantics:01-kinds-of-semantics:14-type-semantics to dido:05-semantics:01-kinds-of-semantics:14-type-semantics nick_dido | dido:05-semantics:01-kinds-of-semantics:14-type-semantics [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Type Semantics ====== | ====== Type Semantics ====== |
| |
| [[fxdemo:99_part_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 ===== |
| |
| Type Semantics defines meaning through [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:type|types]], type names, type membership, type compatibility, type constraints, permitted operations, and type-system rules. | Type Semantics defines meaning through [[dido:99_annexes:annex-b-terms-and-definitions:t:type|types]], type names, type membership, type compatibility, type constraints, permitted operations, and type-system rules. |
| |
| A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:type|type]] identifies a semantic category of values, objects, model elements, messages, events, or expressions. A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:type_system|type system]] defines the set of types and the rules that govern classification, use, compatibility, and interpretation. | A [[dido:99_annexes:annex-b-terms-and-definitions:t:type|type]] identifies a semantic category of values, objects, model elements, messages, events, or expressions. A [[dido:99_annexes:annex-b-terms-and-definitions:t:type_system|type system]] defines the set of types and the rules that govern classification, use, compatibility, and interpretation. |
| |
| Type Semantics differs from [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:datatype|datatype]] semantics. Datatype Semantics constrains value space, representation, and permitted operations for data values. Type Semantics constrains domain interpretation by identifying what kind of thing a value, object, message, event, or model element represents. | Type Semantics differs from [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype|datatype]] semantics. Datatype Semantics constrains value space, representation, and permitted operations for data values. Type Semantics constrains domain interpretation by identifying what kind of thing a value, object, message, event, or model element represents. |
| |
| Type Semantics also differs from [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:schema|schema]] semantics. Schema semantics constrains information elements, structures, relationships, permitted values, and validation rules within a representation context. Type Semantics establishes semantic categories and compatibility rules that schemas, models, APIs, databases, messages, and implementation artefacts express or enforce. | Type Semantics also differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]] semantics. Schema semantics constrains information elements, structures, relationships, permitted values, and validation rules within a representation context. Type Semantics establishes semantic categories and compatibility rules that schemas, models, APIs, databases, messages, and implementation artifacts express or enforce. |
| |
| Type Semantic content includes: | Type Semantic content includes: |
| * Interface type contracts | * Interface type contracts |
| * Message type contracts | * Message type contracts |
| * Traceability to [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:domain]] meaning | * Traceability to [[dido:99_annexes:annex-b-terms-and-definitions:d:domain]] meaning |
| |
| A governed architecture preserves [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from Type Semantics to the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, schema, ontology, rule set, report model, API contract, implementation artefact, or conformance test that establishes or validates the intended meaning. | A governed architecture preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from Type Semantics to the [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, schema, ontology, rule set, report model, API contract, implementation artifact, or conformance test that establishes or validates the intended meaning. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| DIDO Solutions usage is informed by type-system practice, software architecture, schema-language practice, modelling practice, semantic modelling practice, and model-driven architecture principles. | DIDO Solutions usage is informed by type-system practice, software architecture, schema-language practice, modeling practice, semantic modeling practice, and model-driven architecture principles. |
| |
| ===== Note ===== | ===== Note ===== |