View source for JSON

{{short description|Open standard file format and data interchange}}
{{Infobox file format
| name          = JavaScript Object Notation
| icon          = [[File:JSON vector logo.svg|121px]]
| mime          = application/json
| type_code     = TEXT
| extension     = .json
| uniform_type  = public.json
| developer     = 
| genre         = Data interchange
| extended_from = [[JavaScript]]
| standard      = [https://tools.ietf.org/html/std90 STD 90] ({{IETF RFC|8259}}), [https://ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf ECMA-404] (PDF), [https://www.iso.org/standard/71616.html ISO/IEC 21778:2017]
| open          = Yes
| url           = {{URL|https://json.org/}}
}}

'''JSON''' ('''JavaScript Object Notation''', pronounced {{IPAc-en|ˈ|dʒ|eɪ|s|ən}}; also {{IPAc-en|ˈ|dʒ|eɪ|ˌ|s|ɒ|n}}) is an [[Engineering:Open standard|open standard]] file format and [[Electronic data interchange|data interchange]] format that uses [[Human-readable medium|human-readable]] text to store and transmit data objects consisting of [[Attribute–value pair|attribute–value pair]]s and [[Array data type|array]]s (or other [[Serialization|serializable]] values). It is a common data format with diverse  uses in [[Electronic data interchange|electronic data interchange]], including that of [[Web application|web application]]s with [[Server (computing)|server]]s.

JSON is a [[Language-independent specification|language-independent]] data format. It was derived from [[JavaScript]], but many modern [[Programming language|programming language]]s include code to generate and [[Parsing|parse]] JSON-format data. JSON filenames use the extension <code>.json</code>.

Douglas Crockford originally specified the JSON format in the early 2000s.<ref>{{cite web|url=https://www.youtube.com/watch?v=-C-JoyNuQJs |title=Douglas Crockford: The JSON Saga |publisher=YouTube |date=2011-08-28 |access-date=2022-02-21}}</ref> He and Chip Morningstar sent the first JSON message in April 2001.

== Naming and pronunciation ==
The 2017 [[International standard|international standard]] (ECMA-404 and ISO/IEC 21778:2017) specifies that "JSON" is "pronounced {{IPAc-en|ˈ|dʒ|eɪ|·|s|ə|n}}, as in 'Jason and The Argonauts{{'"}}.<ref name=":0"/><ref>{{cite web | url=https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf | title=Standard ECMA-404 – The JSON Data Interchange Syntax | publisher=Ecma International | date=December 2017 | access-date=27 October 2019 |page=1, footnote }}</ref> The first (2013) edition of ECMA-404 did not address the pronunciation.<ref>{{cite book |title=ECMA-404: The JSON Data Interchange Format |date=December 2017 |publisher=ECMA International |location=Geneva |edition=2nd |url=https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf }}</ref> The ''UNIX and Linux System Administration Handbook'' states that "Douglas Crockford, who named and promoted the JSON format, says it's pronounced like the name Jason. But somehow, "JAY-sawn" seems to have become more common in the technical community."<ref>{{cite book |last1=Nemeth |first1=Evi |last2=Snyder |first2=Garth |last3=Hein |first3=Trent R. |last4=Whaley |first4=Ben |last5=Mackin |first5=Dan |title=UNIX and Linux System Administration Handbook |date=2017 |publisher=Addison-Wesley Professional |isbn=9780134278292 |edition=5th |chapter-url=https://books.google.com/books?id=f7M1DwAAQBAJ&pg=PT1125 |access-date=29 October 2019 |language=en |chapter=19: Web Hosting}}</ref> Crockford said in 2011, "There's a lot of argument about how you pronounce that, but I strictly don't care."<ref>{{cite web |title=Douglas Crockford: The JSON Saga – Transcript Vids |url=http://transcriptvids.com/v/-C-JoyNuQJs.html |website=transcriptvids.com |access-date=29 October 2019}}</ref>

== Standards ==
After {{IETF RFC|4627}} had been available as its "informational" specification since 2006, JSON was first standardized in 2013, as ECMA-404.<ref name="ecma2013" /> {{IETF RFC|8259}}, published in 2017, is the current version of the [[Internet Standard]] [https://tools.ietf.org/html/std90 STD 90], and it remains consistent with ECMA-404.<ref name="rfc8259" /> That same year, JSON was also standardized as ISO/[[Organization:International Electrotechnical Commission|IEC]] 21778:2017.<ref name=":0">{{cite web|url=http://www.iso.org/cms/render/live/en/sites/isoorg/contents/data/standard/07/16/71616.html|title=ISO/IEC 21778:2017|website=ISO|access-date=29 July 2019|url-access=subscription}}</ref> The ECMA and [[Organization:International Organization for Standardization|ISO]]/[[Organization:International Electrotechnical Commission|IEC]] standards describe only the allowed syntax, whereas the RFC covers some security and interoperability considerations.<ref>{{cite web|last= Bray|first= Tim|title= JSON Redux AKA RFC7159|url= https://www.tbray.org/ongoing/When/201x/2014/03/05/RFC7159-JSON|work= Ongoing|access-date= 16 March 2014}}</ref>

==History==
[[File:Douglas Crockford.jpg|thumb|Douglas Crockford at the Yahoo Building (2007)]]
JSON grew out of a need for a real-time server-to-browser session communication protocol without using browser plugins such as [[Software:Adobe Flash|Flash]] or [[Java (programming language)|Java]] applets, the dominant methods used in the early 2000s.<ref name = "Edu4java, 2014" >{{cite web | url = http://www.edu4java.com/en/java/unofficial-java-history.html | title = Unofficial Java History | access-date = 2019-08-30 | date = 2014-05-26 | website = Edu4Java | quote = In 1996, Macromedia launches Flash technology which occupies the space left by Java and ActiveX, becoming the de facto standard for animation on the client side. | archive-url = https://web.archive.org/web/20140526235903/http://www.edu4java.com/en/java/unofficial-java-history.html | archive-date = 2014-05-26 | df = dmy-all}}</ref>

Crockford first specified and popularized the JSON format.<ref>{{cite web | url= https://www.youtube.com/watch?v=-C-JoyNuQJs | title= Douglas Crockford — The JSON Saga | publisher= YouTube | date= 28 August 2011 | access-date= 23 September 2016}}</ref> The acronym originated at State Software, a company co-founded by Crockford and others in March 2001. The co-founders agreed to build a system that used standard browser capabilities and provided an [[Abstraction layer|abstraction layer]] for Web developers to create stateful Web applications that had a persistent duplex connection to a Web server by holding two [[Hypertext Transfer Protocol]] (HTTP) connections open and recycling them before standard browser time-outs if no further data were exchanged. The co-founders had a round-table discussion and voted whether to call the data format JSML (JavaScript Markup Language) or JSON (JavaScript Object Notation), as well as under what [[Software license|license]] type to make it available. The JSON.org<ref>{{cite web|url=http://json.org/|title=JSON|website=json.org}}</ref> website was launched in 2001. In December 2005, [[Company:Yahoo!|Yahoo!]] began offering some of its Web services in JSON.<ref name="yahoo">{{cite web |url= http://developer.yahoo.com/common/json.html |title= Using JSON with Yahoo! Web services |author= Yahoo! |access-date= July 3, 2009 | archive-url = https://web.archive.org/web/20071011085815/http://developer.yahoo.com/common/json.html |archive-date= October 11, 2007 }}</ref>

A precursor to the JSON libraries was used in a children's digital asset trading game project named Cartoon Orbit at Communities.com {{Citation needed|date=November 2022}} (the State co-founders had all worked at this company previously) for Cartoon Network {{Citation needed|date=November 2022}}, which used a browser side plug-in with a proprietary messaging format to manipulate [[Dynamic HTML|DHTML]] elements (this system is also owned by 3DO {{Citation needed|date=November 2022}}). Upon discovery of early [[Ajax (programming)|Ajax]] capabilities, digiGroups, Noosh, and others used frames to pass information into the user browsers' visual field without refreshing a Web application's visual context, realizing real-time rich Web applications using only the standard HTTP, HTML and JavaScript capabilities of Netscape 4.0.5+ and IE 5+. Crockford then found that JavaScript could be used as an object-based messaging format for such a system. The system was sold to [[Company:Sun Microsystems|Sun Microsystems]], Amazon.com and EDS.

JSON was based on a [[Subset|subset]] of the [[JavaScript]] scripting language (specifically, Standard ECMA-262 3rd Edition—December 1999<ref>{{cite web | url = http://json.org | title = Introducing JSON | publisher = json.org |first=Douglas |last=Crockford |date=May 28, 2009 |access-date=July 3, 2009 |quote=It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999.}}</ref>) and is commonly used with JavaScript, but it is a [[Language-independent specification|language-independent]] data format. Code for [[Parsing|parsing]] and generating JSON data is readily available in many programming languages. JSON's website lists JSON [[Language binding|libraries]] by language.

In October 2013, Ecma International published the first edition of its JSON standard ECMA-404.<ref name="ecma2013">{{cite web |date=October 2013 |title=The JSON Data Interchange Format |url=https://ecma-international.org/wp-content/uploads/ECMA-404_1st_edition_october_2013.pdf |access-date=20 November 2023 |publisher=ECMA International}}</ref> That same year, {{IETF RFC|7158}} used ECMA-404 as a reference. In 2014, {{IETF RFC|7159}} became the main reference for JSON's Internet uses, superseding {{IETF RFC|4627}} and {{IETF RFC|7158}} (but preserving ECMA-262 and ECMA-404 as main references). In November 2017, ISO/IEC JTC 1/SC 22 published ISO/IEC 21778:2017<ref name=":0" /> as an international standard. On 13 December 2017, the [[Organization:Internet Engineering Task Force|Internet Engineering Task Force]] obsoleted {{IETF RFC|7159}} when it published {{IETF RFC|8259}}, which is the current version of the [[Internet Standard]] STD 90.<ref>{{cite journal |url=https://datatracker.ietf.org/doc/rfc8259/history/ |title=History for draft-ietf-jsonbis-rfc7159bis-04 |website=IETF Datatracker |date=December 2017 |publisher=Internet Engineering Task Force |access-date=2019-10-24 |quote=2017-12-13 [...] RFC published |last1=Bray |first1=Tim }}</ref><ref>{{cite journal | url = https://datatracker.ietf.org/doc/rfc8259/ |title=RFC 8259 - The JavaScript Object Notation (JSON) Data Interchange Format |website=IETF Datatracker |date=December 13, 2017 |publisher=Internet Engineering Task Force |access-date=2019-10-24 |quote=Type: RFC - Internet Standard (December 2017; Errata); Obsoletes RFC 7159; Also known as STD 90 |last1=Bray |first1=Tim }}</ref>

Crockford added a clause to the JSON license stating that "The Software shall be used for Good, not Evil", in order to [[Open-source model|open-source]] the JSON libraries while mocking corporate lawyers and those who are overly pedantic. On the other hand, this clause led to [[License compatibility|license compatibility]] problems of the JSON license with other [[Open-source license|open-source license]]s, as [[Open-source software|open-source software]] and [[Free software|free software]] usually imply no restrictions on the purpose of use.<ref>"[https://lwn.net/Articles/707510/ Apache and the JSON license]" on LWN.net by Jake Edge (November 30, 2016).</ref>

== Syntax ==
The following example shows a possible JSON representation describing a person.

<source lang="json">
{
  "first_name": "John",
  "last_name": "Smith",
  "is_alive": true,
  "age": 27,
  "address": {
    "street_address": "21 2nd Street",
    "city": "New York",
    "state": "NY",
    "postal_code": "10021-3100"
  },
  "phone_numbers": [
    {
      "type": "home",
      "number": "212 555-1234"
    },
    {
      "type": "office",
      "number": "646 555-4567"
    }
  ],
  "children": [
    "Catherine",
    "Thomas",
    "Trevor"
  ],
  "spouse": null
}
</source>

=== Character encoding ===
Although Crockford originally asserted that JSON is a strict subset of JavaScript and ECMAScript,<ref>{{cite web|url=http://www.json.org/js.html |title=JSON in JavaScript |date=2016-07-10 |access-date=2016-08-13 |author=Douglas Crockford |url-status=dead |archive-url=https://web.archive.org/web/20160710230817/http://www.json.org/js.html |archive-date=2016-07-10 |quote=JSON is a subset of the object literal notation of JavaScript. }}</ref> his specification actually allows valid JSON documents that are not valid JavaScript; JSON allows the [[Unicode#Newlines|Unicode line terminators]] {{unichar|2028|LINE SEPARATOR}} and {{unichar|2029|PARAGRAPH SEPARATOR}} to appear unescaped in quoted strings, while ECMAScript 2018 and older do not.<ref name="json-2028">{{cite web|url=http://timelessrepo.com/json-isnt-a-javascript-subset|title=JSON: The JavaScript subset that isn't|author=Holm, Magnus|date=15 May 2011|publisher=The timeless repository|access-date=23 September 2016|archive-date=May 13, 2012|archive-url=https://web.archive.org/web/20120513012409/http://timelessrepo.com/json-isnt-a-javascript-subset|url-status=dead}}</ref><ref name=ECMATC39/> This is a consequence of JSON disallowing only "control characters". For maximum portability, these characters should be backslash-escaped.

JSON exchange in an open ecosystem must be encoded in [[UTF-8]].<ref name="rfc8259">{{cite journal | url=https://tools.ietf.org/html/rfc8259 | title= The JavaScript Object Notation (JSON) Data Interchange Format | publisher=IETF | date= December 2017 | doi= 10.17487/RFC8259 | access-date=16 February 2018| editor-last1= Bray | editor-first1= T | last1= Bray | first1= T. | s2cid= 263868313 }}</ref> The encoding supports the full Unicode character set, including those characters outside the Basic Multilingual Plane (U+0000 to U+FFFF). However, if escaped, those characters must be written using [[UTF-16#Code points from U+010000 to U+10FFFF|UTF-16 surrogate pairs]]. For example, to include the [[Emoji]] character {{unichar|1F610|NEUTRAL FACE}} in JSON:

<source lang="javascript">
{ "face": "😐" }
// or
{ "face": "\uD83D\uDE10" }
</source>

JSON became a strict subset of ECMAScript as of the language's 2019 revision.<ref name=ECMATC39/><ref name=ECMATC39Stage4/>

=== Data types ===
JSON's basic data types are:

* Number: a signed decimal number that may contain a fractional part and may use exponential E notation, but cannot include non-numbers such as [[NaN]]. The format makes no distinction between integer and floating-point. JavaScript uses [[IEEE 754|IEEE-754]] [[Double-precision floating-point format|double-precision floating-point format]] for all its numeric values (later also supporting [[Arbitrary-precision arithmetic|BigInt]]<ref>{{cite web |title=BigInt - MDN Web doc glossary |url=https://developer.mozilla.org/en-US/docs/Glossary/BigInt |website=Mozilla |access-date=18 October 2020}}</ref>), but other languages implementing JSON may encode numbers differently.
* [[String (computer science)|String]]: a sequence of zero or more [[Unicode]] characters. Strings are delimited with double quotation marks and support a backslash [[Escape character|escaping]] syntax.
* Boolean: either of the values <code>true</code> or <code>false</code>
* [[Array data structure|Array]]: an [[List (abstract data type)|ordered list]] of zero or more elements, each of which may be of any type. Arrays use square bracket notation with comma-separated elements.
* [[Object (computer science)|Object]]: a collection of [[Attribute–value pair|name–value pairs]] where the names (also called keys) are strings. The current ECMA standard states: "The JSON syntax does not impose any restrictions on the strings used as names, does not require that name strings be unique, and does not assign any significance to the ordering of name/value pairs."<ref>{{Cite book|url=https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf#page=11|title=The JSON Data Interchange Syntax|date=December 2017|publisher=Ecma International|edition=2nd|page=3|quote=The JSON syntax does not impose any restrictions on the strings used as names, does not require that name strings be unique, and does not assign any significance to the ordering of name/value pairs.}}</ref>  Objects are delimited with curly brackets and use commas to separate each pair, while within each pair the colon ':' character separates the key or name from its value.
* <code>[[Nullable type|null]]</code>: an empty value, using the word <code>null</code>

[[Whitespace character|Whitespace]] is allowed and ignored around or between syntactic elements (values and punctuation, but not within a string value). Four specific characters are considered whitespace for this purpose: space, horizontal tab, line feed, and carriage return. In particular, the byte order mark must not be generated by a conforming implementation (though it may be accepted when parsing JSON). JSON does not provide syntax for [[Comment (computer programming)|comments]].<ref name=DouglasCrockfordComments/>

Early versions of JSON (such as specified by {{IETF RFC|4627}}) required that a valid JSON text must consist of only an object or an array type, which could contain other types within them. This restriction was dropped in {{IETF RFC|7158}}, where a JSON text was redefined as any serialized value.

Numbers in JSON are agnostic with regard to their representation within programming languages. While this allows for numbers of [[Arbitrary-precision arithmetic|arbitrary precision]] to be serialized, it may lead to portability issues. For example, since no differentiation is made between integer and floating-point values, some implementations may treat <code>42</code>, <code>42.0</code>, and <code>4.2E+1</code> as the same number, while others may not. The JSON standard makes no requirements regarding implementation details such as [[Arithmetic overflow|overflow]], [[Arithmetic underflow|underflow]], loss of precision, rounding, or signed zeros, but it does recommend expecting no more than [[IEEE 754]] [[Double-precision floating-point format|binary64]] precision for "good interoperability". There is no inherent precision loss in serializing a machine-level binary representation of a floating-point number (like binary64) into a human-readable decimal representation (like numbers in JSON), and back, since there exist published algorithms to do this exactly and optimally.<ref>{{cite web | url=https://cseweb.ucsd.edu/~mandrysc/pub/dtoa.pdf | title=Printing Floating-Point Numbers - An Always Correct Method | last1=Andrysco | first1=Marc | last2=Jhala | first2=Ranjit | last3=Lerner | first3=Sorin |access-date=2019-07-27}}</ref>

Comments were intentionally excluded from JSON. In 2012, Douglas Crockford described his design decision thus: "I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability."<ref name=DouglasCrockfordComments>{{cite web |last=Crockford |first=Douglas |title=Comments in JSON |date=2012-04-30 |url=https://plus.google.com/+DouglasCrockfordEsq/posts/RK8qyGVaGSr |archive-url=https://archive.today/2015.07.04-102718/https://plus.google.com/+DouglasCrockfordEsq/posts/RK8qyGVaGSr |archive-date=2015-07-04 |url-status=dead |quote=I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn't. Suppose you are using JSON to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through [[Minification (programming)#History|JSMin]] before handing it to your JSON parser. |access-date=2019-08-30 }}</ref>

JSON disallows "trailing commas", a comma after the last value inside a data structure.<ref>{{Cite web |date=2023-09-12 |title=Trailing commas - JavaScript {{!}} MDN |url=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas |access-date=2023-12-16 |website=developer.mozilla.org |language=en-US}}</ref> Trailing commas are a common feature of JSON derivatives to improve ease of use.<ref name="json5">{{cite web |title=JSON5 |url=https://json5.org/ |publisher=json5 |archive-url=https://web.archive.org/web/20201129113821/https://json5.org/ |access-date=16 December 2020|archive-date=2020-11-29 }}</ref>

=== 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>

== Interoperability ==

[https://www.rfc-editor.org/rfc/rfc8259.html RFC 8259] describes certain aspects of JSON syntax which, while legal per the specifications, can cause interoperability problems.

* Certain JSON implementations only accept JSON texts which represent an object or an array. For interoperability, applications interchanging JSON should transmit messages which are objects or arrays.
* The specifications allow JSON objects which contain multiple members with the same name. The behavior of implementations processing objects with duplicate names is unpredictable. For interoperability, applications should avoid duplicate names when transmitting JSON objects.
* The specifications specifically say that the order of members in JSON objects is not significant. For interoperability, applications should avoid assigning meaning to member ordering even if the parsing software makes that ordering visible.
* While the specifications place no limits on the magnitude or precisions of JSON number literals, the widely-used JavaScript implementation stores them as IEEE754 "binary64" quantities. For interoperability, applications should avoid transmitting numbers which cannot be represented in this way, for example 1E400 or 3.141592653589793238462643383279.
* While the specifications do not constrain the character encoding of the Unicode characters in a JSON text, the vast majority of implementations assume [[UTF-8]] encoding; for interoperability, applications should always and only encode JSON messages in UTF-8.
* The specifications do not forbid transmitting byte sequences that do not correctly represent Unicode characters. For interoperability, applications should transmit messages containing no such byte sequences.
* The specification does not constrain how applications go about comparing Unicode strings. For interoperability, applications should always perform such comparisons code unit by code unit.

In 2015, the IETF published [https://www.rfc-editor.org/rfc/rfc7493.html RFC7493], describing the "I-JSON Message Format", a restricted profile of JSON which constrains the syntax and processing of JSON to avoid, as much as possible, these interoperability issues.

== Metadata and schema ==
The official MIME type for JSON text is "<code>application/json</code>",<ref>{{cite web|url=https://www.iana.org/assignments/media-types/application/index.html|title=Media Types|work=iana.org|access-date=13 September 2015}}</ref> and most modern implementations have adopted this. The unofficial MIME type "<code>text/json</code>" or the content-type "<code>text/javascript</code>" are also supported for legacy reasons by many service providers, browsers, servers, web applications, libraries, frameworks, and APIs. Notable examples include the Google Search API,<ref name="faraday-stack-pull-2">{{cite web|url=https://github.com/mislav/faraday-stack/pull/2|title=Handle application/json & text/json by benschwarz · Pull Request #2 · mislav/faraday-stack|work=GitHub|access-date=13 September 2015}}</ref> Yahoo!,<ref name="faraday-stack-pull-2" /><ref>{{cite web|url=http://blog.programmableweb.com/2005/12/16/yahoo-javascript-and-json/|title=Yahoo!, JavaScript, and JSON|work=ProgrammableWeb|access-date=13 September 2015|date=2005-12-16}}</ref> Flickr,<ref name="faraday-stack-pull-2" /> Facebook API,<ref>{{cite web|url=https://github.com/AFNetworking/AFNetworking/pull/148|title=Make JSON requests allow text/javascript content by jakeboxer · Pull Request #148 · AFNetworking/AFNetworking|work=GitHub|access-date=13 September 2015}}</ref> [[Software:Lift (web framework)|Lift framework]],<ref>{{cite web|url=https://github.com/lift/lift/blob/master/framework/lift-base/lift-webkit/src/main/scala/net/liftweb/http/Req.scala|title=lift/Req.scala at master · lift/lift · GitHub|work=GitHub|access-date=13 September 2015}}</ref> and Dojo Toolkit 0.4.<ref>{{cite web|url=https://bugs.dojotoolkit.org/browser/legacy/branches/0.4/src/io/BrowserIO.js|title=BrowserIO.js in legacy/branches/0.4/src/io – Dojo Toolkit|work=dojotoolkit.org|access-date=13 September 2015|archive-url=https://web.archive.org/web/20160110132551/https://bugs.dojotoolkit.org/browser/legacy/branches/0.4/src/io/BrowserIO.js|archive-date=10 January 2016|url-status=dead}}</ref>

''JSON Schema'' specifies a JSON-based format to define the structure of JSON data for validation, documentation, and interaction control. It provides a contract for the JSON data required by a given application, and how that data can be modified.<ref>{{cite web|url=https://json-schema.org//|title=JSON Schema and Hyper-Schema|work=json-schema.org|access-date=8 June 2021}}</ref> JSON Schema is based on the concepts from [[XML Schema (W3C)|XML Schema]] (XSD) but is JSON-based. As in XSD, the same serialization/deserialization tools can be used both for the schema and data, and it is self-describing. It is specified in an [[Internet Draft]] at the IETF, currently in 2020-12 draft, which was released on January 28, 2021.<ref>{{cite web|url=https://json-schema.org/latest/json-schema-core.html|title=draft-handrews-json-schema-00 - JSON Schema: A Media Type for Describing JSON Documents|work=json-schema.org/|access-date=8 June 2021|date=2021-01-28}}</ref> There are several validators available for different programming languages,<ref>{{cite web|url=https://json-schema.org/implementations.html|title=JSON Schema Implementations|work=json-schema.org|access-date=8 June 2021}}</ref> each with varying levels of conformance. The standard filename extension is .json.<ref>{{cite journal |url=https://datatracker.ietf.org/doc/html/rfc8259#section-11 |title=11. IANA Considerations |journal=RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format |date=December 2017 |publisher=[[IETF]] |last1=Bray |first1=Tim |editor-first1=T. |editor-last1=Bray |doi=10.17487/RFC8259 |s2cid=263868313 }}</ref>

The JSON standard does not support object [[Reference (computer science)|references]], but an [[IETF]] draft standard for JSON-based object references exists.<ref>{{cite journal |last=Zyp |first=Kris |editor-last=Bryan |editor-first=Paul C. |title=JSON Reference: draft-pbryan-zyp-json-ref-03 |website=Internet Engineering Task Force |date=September 16, 2012|url=https://datatracker.ietf.org/doc/html/draft-pbryan-zyp-json-ref-03 }}</ref>

== Uses ==

[[JSON-RPC]] is a [[Remote procedure call|remote procedure call]] (RPC) protocol built on JSON, as a replacement for [[XML-RPC]] or [[SOAP]]. It is a simple protocol that defines only a handful of data types and commands. JSON-RPC lets a system send notifications (information to the server that does not require a response) and multiple calls to the server that can be answered out of order.

Asynchronous JavaScript and JSON (or AJAJ) refers to the same [[Dynamic web page|dynamic web page]] methodology as [[Ajax (programming)|Ajax]], but instead of [[XML]], JSON is the data format. AJAJ is a web development technique that provides for the ability of a webpage to request new data after it has loaded into the [[Software:Web browser|web browser]]. Typically it renders new data from the server in response to user actions on that webpage. For example, what the user types into a [[Text box|search box]], client-side code then sends to the server, which immediately responds with a [[Drop-down list|drop-down list]] of matching [[Database|database]] items.

JSON has seen ad hoc usage as a [[Configuration file|configuration language]]. However, it does not support [[Comment (computer programming)|comments]].
In 2012, Douglas Crockford, JSON creator, had this to say about comments in JSON when used as a configuration language: "I know that the lack of comments makes some people sad, but it shouldn't. Suppose you are using JSON to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin<ref>{{cite web|url=https://www.crockford.com/jsmin.html|title=JSMin|last=Crockford|first=Douglas|date=2019-05-16|access-date=2020-08-12|quote=JSMin [2001] is a minification tool that removes comments and unnecessary whitespace from JavaScript files.}}</ref> before handing it to your JSON parser."<ref name=DouglasCrockfordComments/>

[[Software:MongoDB|MongoDB]] uses JSON-like data for its [[Document-oriented database|document-oriented database]].

Some relational databases, such as PostgreSQL and MySQL, have added support for native JSON data types. This allows developers to store JSON data directly in a relational database without having to convert it to another data format.

==Safety==
JSON being a subset of JavaScript can lead to the misconception that it is safe to pass JSON texts to the JavaScript <code>[[Eval|eval]]()</code> function. This is not safe, due to certain valid JSON texts, specifically those containing {{unichar|2028|LINE SEPARATOR}} or {{unichar|2029|PARAGRAPH SEPARATOR}}, not being valid JavaScript code until JavaScript specifications were updated in 2019, and so older engines may not support it.<ref name="Magnus Holm">{{cite web|title=JSON: The JavaScript subset that isn't|url=http://timelessrepo.com/json-isnt-a-javascript-subset|publisher=Magnus Holm|access-date=16 May 2011|archive-date=May 13, 2012|archive-url=https://web.archive.org/web/20120513012409/http://timelessrepo.com/json-isnt-a-javascript-subset|url-status=dead}}</ref> To avoid the many pitfalls caused by executing arbitrary code from the Internet, a new function, {{code|lang=javascript|code=JSON.parse()}} was first added to the fifth edition of ECMAScript,<ref>{{cite web|url=http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf|title=ECMAScript Fifth Edition|access-date=March 18, 2011|archive-url=https://web.archive.org/web/20110414214458/http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf|archive-date=April 14, 2011|url-status=dead|df=mdy-all}}</ref> which as of 2017 is supported by all major browsers. For non-supported browsers, an API-compatible JavaScript library is provided by Douglas Crockford.<ref>{{cite web|url=https://github.com/douglascrockford/JSON-js/blob/master/json2.js|title=douglascrockford/JSON-js|website=GitHub|date=2019-08-13}}</ref> In addition, the TC39 proposal [https://github.com/tc39/proposal-json-superset "Subsume JSON"] made [[ECMAScript]] a strict JSON superset as of the language's 2019 revision.<ref name=ECMATC39>{{cite web |title=Subsume JSON: Proposal to make all JSON text valid ECMA-262 |url=https://tc39.es/proposal-json-superset/ |publisher=Ecma TC39 |access-date=27 August 2019 |date=23 August 2019}}</ref><ref name=ECMATC39Stage4>{{cite web |title=Advance to Stage 4 - tc39/proposal-json-superset |url=https://github.com/tc39/proposal-json-superset/commit/0604b6083e18fe033a1520388b8c6146bcd79e23|website=GitHub|date=May 22, 2018}}</ref>
Various JSON parser implementations have suffered from [[Denial-of-service attack|denial-of-service attack]] and [[Mass assignment vulnerability|mass assignment vulnerability]].<ref>{{cite web | url=https://www.ruby-lang.org/en/news/2013/02/22/json-dos-cve-2013-0269/ | title=Denial of Service and Unsafe Object Creation Vulnerability in JSON (CVE-2013-0269) | access-date=January 5, 2016}}</ref><ref>{{cite web | url=http://tools.cisco.com/security/center/viewAlert.x?alertId=31048 | title=Microsoft .NET Framework JSON Content Processing Denial of Service Vulnerability | archive-url=https://web.archive.org/web/20181106233952/http://tools.cisco.com/security/center/viewAlert.x?alertId=31048 | access-date=January 5, 2016| archive-date=November 6, 2018 }}</ref>

== Alternatives ==

JSON is promoted as a low-overhead alternative to XML as both of these formats have widespread support for creation, reading, and decoding in the real-world situations where they are commonly used.<ref>{{cite web|title=JSON: The Fat-Free Alternative to XML|url=http://www.json.org/xml.html|publisher=json.org|access-date=14 March 2011}}</ref> Apart from XML, examples could include [[Comma-separated values|CSV]] and supersets of JSON. [[Software:Protocol Buffers|Google Protocol Buffers]] can fill this role, although it is not a data interchange language. [[CBOR]] has a superset of the JSON data types, but it is not text-based.

=== XML ===
{{Main|XML}}

[[XML]] has been used to describe structured data and to serialize objects. Various XML-based protocols exist to represent the same kind of data structures as JSON for the same kind of data interchange purposes. Data can be encoded in XML in several ways. The most expansive form using tag pairs results in a much larger (in character count) representation than JSON, but if data is stored in attributes and 'short tag' form where the closing tag is replaced with {{code|/>}}, the representation is often about the same size as JSON or just a little larger. However, an XML attribute can only have a single value and each attribute can appear at most once on each element.

XML separates "data" from "metadata" (via the use of elements and attributes), while JSON does not have such a concept.

Another key difference is the addressing of values. JSON has objects with a simple "key" to "value" mapping, whereas in XML addressing happens on "nodes", which all receive a unique ID via the XML processor. Additionally, the XML standard defines a common attribute {{code|xml:id}}, that can be used by the user, to set an ID explicitly.

XML tag names cannot contain any of the characters <code>!"#$%&amp;'()*+,/;&lt;=&gt;?@[\]^`{|}~</code>, nor a space character, and cannot begin with {{code|-}}, {{code|.}}, or a numeric digit, whereas JSON keys can (even if quotation mark and backslash must be escaped).<ref name="XML 1.1">{{cite web |url=https://www.w3.org/TR/xml11/ |title=XML 1.1 Specification |publisher=World Wide Web Consortium |access-date=2019-08-26}}</ref>

XML values are strings of ''characters'', with no built-in [[Type safety|type safety]]. XML has the concept of [[XML schema|schema]], that permits strong typing, user-defined types, predefined tags, and formal structure, allowing for formal validation of an XML stream. JSON has several types built-in and has a similar schema concept in JSON Schema.

XML supports comments, while JSON does not.<ref name=Saternos45>{{cite book|last1=Saternos|first1=Casimir|title=Client-server web apps with Javascript and Java|date=2014|isbn=9781449369316|page=45|publisher="O'Reilly Media, Inc." }}</ref><ref name=DouglasCrockfordComments/>

==Supersets==

Support for [[Comment (computer programming)|comments]] and other features have been deemed useful, which has led to several nonstandard JSON supersets being created. Among them are HJSON,<ref>{{cite book|last1=Edelman|first1=Jason|last2=Lowe|first2=Scott|last3=Oswalt|first3=Matt|title=Network Programmability and Automation|publisher=O'Reilly Media|quote=for data representation you can pick one of the following: YAML, YAMLEX, JSON, JSON5, HJSON, or even pure Python}}</ref> [[HOCON]], and JSON5 (which despite its name, is not the fifth version of JSON).<ref name=lucidchart/><ref>{{cite web | url=https://github.com/lightbend/config/blob/master/HOCON.md |title=HOCON (Human-Optimized Config Object Notation) |date=2019-01-28 |website=GitHub |access-date=2019-08-28 |quote=The primary goal is: keep the semantics (tree structure; set of types; encoding/escaping) from JSON, but make it more convenient as a human-editable config file format.}}</ref> 

=== YAML ===

[[YAML]] version 1.2 is a superset of JSON; prior versions were not strictly compatible. For example, escaping a slash {{code|/}} with a backslash {{code|\}} is valid in JSON, but was not valid in YAML.<ref name="YAML Version 1.2">{{cite web|url=http://www.yaml.org/spec/1.2/spec.html|title=YAML Ain't Markup Language (YAML™) Version 1.2|work=yaml.org|access-date=13 September 2015}}</ref> YAML supports comments, while JSON does not.<ref name="YAML Version 1.2"/><ref name=lucidchart>{{cite web |last1=McCombs |first1=Thayne |title=Why JSON isn't a good configuration language |date=July 16, 2018 |url=https://www.lucidchart.com/techblog/2018/07/16/why-json-isnt-a-good-configuration-language/ |publisher=Lucid Chart |access-date=15 June 2019}}</ref><ref name=DouglasCrockfordComments/>

=== CSON ===
'''CSON''' ("cursive script object notation"), is defined as tiny grammar additions to JSONs ABNF grammar specified by RFC 4627. Like YAML, it is a strict superset of JSON. Contrary to YAML, every CSON data can be translated to JSON back and forth, so one can continue to use a library which only understands JSON, and one does not have to translate existing JSON. Besides such JSON equivalence, design considerations were:<ref>[https://github.com/lifthrasiir/cson CSON], specification and README, last updated: 2021-07-01.</ref>
* Ease of writing, it supports comments, single + double quoted strings, strings in multiple lines, redundant commas.
* Ease of parsing, it is [[LL grammar|LL(1)]] and explicitly avoids context sensitivity.
* Incompatibility to JavaScript is not strict, therefore avoid CSON over HTTP.
* Whitespaces are not significant.
* Like YAML, strict string, no data types, unlike e.g., [[TOML]]. Additional data types should not be a data format job, and would make every implementation difficult.
Libraries for C, JavaScript, Python, and Rust exist.

=== HOCON ===
'''HOCON''' ("Human-Optimized Config Object Notation" is a format for human-readable data, and a superset of JSON.<ref>{{Cite web|title=config/HOCON.md at master · lightbend/config|url=https://github.com/lightbend/config|access-date=2021-08-05|website=GitHub|language=en}}</ref>
The uses of HOCON are:
* It is primarily used in conjunction with the Play framework,<ref>{{Cite web|title=Config File - 2.5.x|url=https://www.playframework.com/documentation/2.5.x/ConfigFile|access-date=2021-08-05|website=www.playframework.com}}</ref> and is developed by Lightbend. 
* It is also supported as a configuration format for .NET projects via Akka.NET<ref>[https://getakka.net/articles/hocon/index.html Akka.NET HOCON Docs]</ref><ref>{{Cite web|title=Akka.NET Documentation &#124; Akka.NET Documentation|url=https://getakka.net/|access-date=2021-08-05|website=getakka.net}}</ref> and [[Software:Puppet|Puppet]].<ref>[https://puppet.com/blog/managing-hocon-configuration-files-puppet Managing HOCON configuration files with Puppet]</ref>
* TIBCO Streaming:<ref>{{Cite web|title=StreamBase Documentation|url=https://docs.streambase.com/latest/index.jsp|access-date=2021-08-05|website=docs.streambase.com}}</ref> HOCON is the primary configuration file format for the TIBCO Streaming<ref>{{Cite web|title=Configuration Guide|url=https://docs.streambase.com/latest/topic/com.streambase.sb.ide.help/data/html/hocon/index.html|access-date=2021-08-05|website=docs.streambase.com}}</ref> family of products (StreamBase, LiveView, and Artifact Management Server) as of TIBCO Streaming Release 10.<ref>{{Cite web|title=StreamBase New and Noteworthy Archive|url=https://docs.streambase.com/latest/topic/com.streambase.sb.ide.help/data/html/dochome/xarchive-sb-noteworthy.html|access-date=2021-08-05|website=docs.streambase.com}}</ref>
* It is also the primary configuration file format for several subsystems of Exabeam Advanced Analytics.<ref>[https://docs.exabeam.com/en/advanced-analytics/i48/release-notes/109536-what-s-new.html Exabeam Advanced Analytics Release Notes]</ref>
* [[Software:Jitsi|Jitsi]] uses it as the "new" config system and .properties-Files as fallback<ref>{{cite web |url=https://github.com/jitsi/jitsi-videobridge/commit/676fb3df696c4737ac086fb856af1f85c6ded90e|title=Config phase 1|author=JITSI Project|website=[[GitHub]] |access-date=2021-02-16}}</ref><ref>{{ cite web| url=https://github.com/jitsi/jicofo/blob/master/src/main/resources/reference.conf| title=reference.conf| author=JITSI Project| website=[[GitHub]]| access-date=2021-02-16}}</ref>

=== JSON5 ===
'''JSON5''' ("JSON5 Data Interchange Format") is an extension of JSON syntax that just like JSON is also valid JavaScript syntax. The specification was started in 2012 and finished in 2018 with version 1.0.0.<ref>{{cite web|url=https://spec.json5.org/|title=The JSON5 Data Interchange Format|access-date=2022-06-25}}</ref> The main differences to JSON syntax are:

* Optional trailing commas
* Unquoted object keys
* Single quoted and multiline strings
* Additional number formats
* Comments

JSON5 syntax is supported in some software as extension of JSON syntax, for instance in [[Software:SQLite|SQLite]].<ref>{{cite web|url=https://www.sqlite.org/json1.html#json5_extensions|author=SQLite|access-date=2023-06-25|title=JSON Functions And Operators}}</ref>

=== JSONC ===
JSONC (JSON with comments) is a subset of JSON5 and primarily used by Microsoft:
* supports single line comments (<code>//</code>) and block comments (<code>/* */</code>)
* accepts trailing commas, but they are discouraged and the editor will display a warning<ref>{{Cite web |title=JSON with Comments - JSON editing in Visual Studio Code |url=https://code.visualstudio.com/docs/languages/json#_json-with-comments |access-date=2023-10-02 |website=code.visualstudio.com |language=en}}</ref>

== Derivatives ==
Several serialization formats have been built on or from the JSON specification. Examples include 

* [[GeoJSON]], a format designed for representing simple geographical features<ref>{{Cite journal |date=August 2016 |title=RFC 7946 - The GeoJSON Format |url=https://datatracker.ietf.org/doc/html/rfc7946 |access-date=2022-06-17 |website=[[Organization:Internet Engineering Task Force|IETF]] Datatracker |last1=Butler |first1=H. |last2=Daly |first2=M. |last3=Doyle |first3=A. |last4=Gillies |first4=Sean |last5=Schaub |first5=T. |last6=Hagen |first6=Stefan }}</ref><ref>{{Cite web |title=GeoJSON |url=https://geojson.org/ |access-date=2022-08-07 |website=geojson.org}}</ref>
* [[JSON→URL]], a language-independent data interchange format for the JSON data model<ref name="jsonurl-spec">{{cite web
|title=JSON→URL Specification
|url=https://jsonurl.github.io/specification/|work=Ongoing|accessdate=9 April 2021}}</ref><ref>{{Cite web |title=JSON inside a URL |url=https://www.jsonurl.org/ |access-date=2022-08-07 |website=jsonurl |language=en}}</ref>
* [[JSON-LD]], a method of encoding [[Linked data|linked data]] using JSON<ref>{{Cite web |date=2020-07-16 |title=JSON-LD 1.1 |url=https://www.w3.org/TR/json-ld/ |access-date=2022-06-17 |website=[[Organization:World Wide Web Consortium|World Wide Web Consortium]]}}</ref><ref>{{Cite web |title=JSON-LD - JSON for Linking Data |url=https://json-ld.org/ |access-date=2022-08-07 |website=json-ld.org}}</ref>
* [[JSON-RPC]], a remote procedure call protocol encoded in JSON<ref>{{Cite web |title=JSON-RPC |url=https://www.jsonrpc.org/ |access-date=2022-06-17 |website=jsonrpc.org}}</ref>
* [[JsonML]], a lightweight markup language used to map between [[XML]] and JSON<ref>{{Cite web |title=JsonML (JSON Markup Language) |url=http://www.jsonml.org/ |access-date=2022-06-17 |website=JsonML.org}}</ref><ref>{{Citation |last=McKamey |first=Stephen |title=JsonML |date=2022-06-14 |url=https://github.com/mckamey/jsonml |access-date=2022-08-07}}</ref>
* [[Smile (data interchange format)]]<ref>{{Cite web |title=FasterXML/smile-format-specification: New home for Smile format |url=https://github.com/FasterXML/smile-format-specification |access-date=2022-06-17 |website=GitHub}}</ref><ref>{{Cite web |last=Gupta |first=Ayush |date=2019-02-10 |title=Understanding Smile — A data format based on JSON |url=https://medium.com/code-with-ayush/understanding-smile-a-data-format-based-on-json-29972a37d376 |access-date=2022-08-07 |website=Code with Ayush |language=en}}</ref>
* [[Software:UBJSON|UBJSON]], a binary computer data interchange format imitating JSON, but requiring fewer bytes of data<ref>{{Cite web |title=Universal Binary JSON Specification – The universally compatible format specification for Binary JSON |url=https://ubjson.org/ |access-date=2022-06-17 |website=ubjson.org}}</ref><ref>{{Cite web |title=UBJSON - JSON for Modern C++ |url=https://json.nlohmann.me/features/binary_formats/ubjson/ |access-date=2022-08-07 |website=json.nlohmann.me}}</ref>

== See also ==
* [[BSON]]
* [[Comparison of data serialization formats]]
* Amazon [[Ion (serialization format)|Ion]]{{snd}} a superset of JSON
* [[Software:Jackson (API)|Jackson (API)]]
* [[Jaql|jaql]] - a functional data processing and query language most commonly used for JSON query processing
* [[Jq (programming language)|jq]] - a "JSON query language" and high-level programming language
* [[JSONiq]] - a JSON-oriented query and processing language based on [[XQuery]]
* [[JSON streaming]]
* [[S-expression]]
* Wikipedia TNT Module

== References ==
{{reflist}}

== External links ==


{{Data exchange}}
{{Ecma International Standards}}
{{ISO standards}}


[[Category:JSON| ]]
[[Category:Ajax (programming)]]
[[Category:Ecma standards]]
[[Category:ISO standards]]
[[Category:Markup languages]]
[[Category:Open formats]]

{{Sourceattribution|JSON}}