| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:05-semantics:01-kinds-of-semantics:12-schema-semantics [2026/07/08 03:02] – ↷ Page moved from dido:01-semantics:01-kinds-of-semantics:12-schema-semantics to dido:05-semantics:01-kinds-of-semantics:12-schema-semantics nick_dido | dido:05-semantics:01-kinds-of-semantics:12-schema-semantics [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Schema Semantics ====== | ====== Schema 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 ===== |
| Schema Semantics defines meaning through information elements, structures, permitted values, relationships, cardinalities, constraints, validation rules, and representation contexts. | Schema Semantics defines meaning through information elements, structures, permitted values, relationships, cardinalities, constraints, validation rules, and representation contexts. |
| |
| A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:schema]] expresses semantic content when its element names, datatypes, constraints, relationships, and documentation preserve [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to defined domain meaning. The schema constrains representation. The associated vocabulary, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], rule set, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], report model, or other authoritative semantic source establishes the intended meaning. | A [[dido:99_annexes:annex-b-terms-and-definitions:s:schema]] expresses semantic content when its element names, datatypes, constraints, relationships, and documentation preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to defined domain meaning. The schema constrains representation. The associated vocabulary, [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], rule set, [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], report model, or other authoritative semantic source establishes the intended meaning. |
| |
| Schema Semantics differs from schema syntax. Schema syntax defines how the schema appears in a selected language or technology. Schema Semantics defines what the schema elements, constraints, and relationships mean in the domain. | Schema Semantics differs from schema syntax. Schema syntax defines how the schema appears in a selected language or technology. Schema Semantics defines what the schema elements, constraints, and relationships mean in the domain. |
| |
| Schema Semantics also differs from [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:datatype|datatype]] semantics. Datatype semantics constrains value space, representation, and permitted operations. Schema Semantics constrains how information elements, datatypes, relationships, and rules combine within a defined representation context. | Schema Semantics also differs from [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype|datatype]] semantics. Datatype semantics constrains value space, representation, and permitted operations. Schema Semantics constrains how information elements, datatypes, relationships, and rules combine within a defined representation context. |
| |
| Schemas appear in many forms, including XML Schema, JSON Schema, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:rdf_schema|RDF Schema]], SQL DDL, OpenAPI schemas, Avro schemas, Protobuf schemas, DDS IDL, and message specifications. | Schemas appear in many forms, including XML Schema, JSON Schema, [[dido:99_annexes:annex-b-terms-and-definitions:r:rdf_schema|RDF Schema]], SQL DDL, OpenAPI schemas, Avro schemas, Protobuf schemas, DDS IDL, and message specifications. |
| |
| Schema semantic content includes: | Schema semantic content includes: |
| * Validation rules | * Validation rules |
| * Representation contexts | * Representation contexts |
| * Traceability to the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:domain]] meaning | * Traceability to the [[dido:99_annexes:annex-b-terms-and-definitions:d:domain]] meaning |
| |
| A governed architecture preserves traceability from schema Semantics to the conceptual model, vocabulary, type system, report model, ontology, rule set, policy source, implementation artefact, or conformance test that establishes or validates the intended meaning. | A governed architecture preserves traceability from schema Semantics to the conceptual model, vocabulary, type system, report model, ontology, rule set, policy source, implementation artifact, or conformance test that establishes or validates the intended meaning. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| DIDO Solutions usage is informed by schema-language practice, data modelling, information modelling, software architecture, semantic modelling practice, and model-driven architecture principles. | DIDO Solutions usage is informed by schema-language practice, data modeling, information modeling, software architecture, semantic modeling practice, and model-driven architecture principles. |
| |
| ===== Note ===== | ===== Note ===== |