| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:j:json [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:j:json to dido:99_annexes:annex-b-terms-and-definitions:j:json nick_dido | dido:99_annexes:annex-b-terms-and-definitions:j:json [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== JavaScript Object Notation (JSON) ====== | ====== JavaScript Object Notation (JSON) ====== |
| |
| [[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 ===== |
| JavaScript Object Notation (JSON) provides a lightweight, text-based syntax for structured data interchange. JSON represents data using objects, arrays, names, values, strings, numbers, booleans, and null values. | JavaScript Object Notation (JSON) provides a lightweight, text-based syntax for structured data interchange. JSON represents data using objects, arrays, names, values, strings, numbers, booleans, and null values. |
| |
| JSON supports data exchange across programming languages, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:api|APIs]], message formats, configuration files, event payloads, reports, and implementation artefacts. | JSON supports data exchange across programming languages, [[dido:99_annexes:annex-b-terms-and-definitions:a:api|APIs]], message formats, configuration files, event payloads, reports, and implementation artifacts. |
| |
| JSON differs from [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:s:schema|schema]]. JSON provides a data-interchange syntax. A schema defines structure, permitted values, relationships, and constraints for a defined representation context. JSON Schema, when used, constrains JSON documents. | JSON differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]]. JSON provides a data-interchange syntax. A schema defines structure, permitted values, relationships, and constraints for a defined representation context. JSON Schema, when used, constrains JSON documents. |
| |
| JSON also differs from [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]]. JSON syntax alone does not establish domain meaning. JSON expresses semantic content when names, values, structures, schemas, vocabularies, rules, and traceability preserve defined domain meaning. | JSON also differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]]. JSON syntax alone does not establish domain meaning. JSON expresses semantic content when names, values, structures, schemas, vocabularies, rules, and traceability preserve defined domain meaning. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| ECMA-404 The JSON Data Interchange Syntax; specialised for use in the FX Demo Reference Architecture. | ECMA-404 The JSON Data Interchange Syntax; specialized for use in the FX Demo Reference Architecture. |
| |
| ===== Note ===== | ===== Note ===== |