| [pending revision] | [pending revision] |
Content deleted Content added
Reverting edit(s) by Azrilkun1 (talk) to rev. 1022405684 by 111.94.44.60: test edits (RW 16.1) |
m →Semantics: comma |
||
Line 113:
===Semantics===
While JSON provides a syntactic framework for data interchange, unambiguous data interchange also requires agreement between producer and consumer on the semantics of specific use of the JSON syntax.<ref>{{cite web | url=https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf | title=The JSON Data Interchange Syntax | publisher=Ecma International | date=December 2017 | access-date=27 October 2019 | quote=The JSON syntax is not a specification of a complete data interchange. Meaningful data interchange requires agreement between a producer and consumer on the semantics attached to a particular use of the JSON syntax. What JSON does provide is the syntactic framework to which such semantics can be attached}}</ref> One example of where such an agreement is necessary is the serialization of data types defined by the [[JavaScript syntax]] that are not part of the JSON standard, e.g., Date, Function, Regular Expression, and <code>undefined</code>.<ref>{{cite web | url=http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf | title=ECMAScript 2019 Language Specification | publisher=Ecma International | date=June 2019 | access-date=27 October 2019 | archive-url=https://web.archive.org/web/20150412040502/http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf | archive-date=12 April 2015 | url-status=dead }}</ref>
== Metadata and schema ==
| |||