| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:s:schema [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:s:schema [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| | ====== Schema ====== |
| |
| | [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| | |
| | ===== Discussion ===== |
| | |
| | A schema defines the structure, permitted content, relationships, values, and constraints for information in a defined representation context. Schemas organize information so that systems, tools, and people interpret information consistently. |
| | |
| | Schemas support [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic]] when their elements, names, value types, relationships, constraints, and documentation preserve traceability to defined domain meaning. A schema constrains representation, but domain meaning comes from the associated vocabulary, [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model]], [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology]], rules, or other authoritative semantic source. |
| | |
| | A schema differs from an ontology. A schema focuses on representation structure, permitted content, and validation constraints. An ontology focuses on concepts, relationships, distinctions, and semantic commitments within a defined domain. |
| | |
| | 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. |
| | |
| | ===== Definition ===== |
| | |
| | //structured specification of information elements, permitted values, relationships, and constraints for a defined representation context// |
| | |
| | ===== Source ===== |
| | |
| | Generalised from data modeling, schema language, software architecture, and information modeling usage; specialized for use in the FX Demo Reference Architecture. |
| | |
| | ===== Note ===== |
| | |
| | A schema expresses selected semantic commitments when its information elements, constraints, values, relationships, and documentation preserve traceability to defined domain meaning. A schema does not by itself establish the full meaning of a domain. |
| | |
| | ===== Example ===== |
| | |
| | An FX trade schema defines information elements such as ''tradeIdentifier'', ''counterpartyLEI'', ''currencyPair'', ''notionalAmount'', ''tradeDate'', and ''settlementDate''. The schema constrains representation, while the associated conceptual model and vocabulary define the business meaning of those information elements. |
| | |
| | ---- |
| | |
| | <WRAP centeralign> |
| | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| | </WRAP> |