JSON - Wikipedia JSON `` Json '' redirects here. For people with similar names, see J Son. JSON Filename extension. json Internet media type application / json Type code TEXT Uniform Type Identifier ( UTI ) public. json Type of format Data interchange Extended from JavaScript Standard RFC 7159, ECMA - 404 Website json.org In computing, JavaScript Object Notation or JSON ( / ˈdʒeɪsən / JAY - sən ), is an open - standard file format that uses human - readable text to transmit data objects consisting of attribute -- value pairs and array data types ( or any other serializable value ). It is a very common data format used for asynchronous browser / server communication, including as a replacement for XML in some AJAX - style systems. JSON is a language - independent data format. It was derived from JavaScript, but as of 2017 many programming languages include code to generate and parse JSON - format data. The official Internet media type for JSON is application / json. JSON filenames use the extension. json. Douglas Crockford originally specified the JSON format in the early 2000s ; two competing standards, RFC 7159 and ECMA - 404, defined it in 2013. The ECMA standard describes only the allowed syntax, whereas the RFC covers some security and interoperability considerations. A restricted profile of JSON, known as I - JSON ( short for `` Internet JSON '' ), seeks to overcome some of the interoperability problems with JSON. It is defined in RFC 7493.. Contents 1 History 2 Data types, syntax and example 2.1 Example 2.2 Data portability issues 2.3 Using JSON in JavaScript 2.4 Unsupported native data types 3 Schema and metadata 3.1 JSON Schema 4 MIME type 5 Applications 5.1 JSON - RPC 5.2 AJAJ 6 Security considerations 7 Vulnerabilities in specific JSON parsers 8 Object references 9 Comparison with other formats 9.1 YAML 9.2 XML 9.3 Samples 9.3. 1 JSON sample 9.3. 2 YAML sample 9.3. 3 XML samples 10 See also 11 Notes 12 References 13 External links History Douglas Crockford first specified JSON. Image from 2007. JSON grew out of a need for stateful, real - time server - to - browser communication protocol without using browser plugins such as Flash or Java applets, the dominant methods used in the early 2000s. Douglas Crockford first specified and popularized the JSON format. The acronym originated at State Software ( originally named Veil Networks, Inc. ), a company co-founded by Crockford, Randy Farmer ( left to work at 3DO ), Greg Macdonald, Chip Morningstar, Robert F. Napiltonia and Dominik Zynis in March 2001. State Software was funded by Tesla Ventures with $1.8 Million in October 2011, and tried to trademark the word `` State ''. The co-founders agreed to build a system that used standard browser capabilities and provided an abstraction layer for Web developers to create stateful Web applications that had a persistent duplex connection to a Web server by holding two 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 or JSON, as well as under what license type to make it available. Crockford, being inspired by the words of then President Bush, should also be credited with coming up with the `` evil - doers '' JSON license ( `` The Software shall be used for Good, not Evil. '' ) in order to open - source the JSON libraries, but force ( troll ) corporate lawyers, or those who are overly pedantic, to seek to pay for a license from State. Morningstar developed the idea for the State Application Framework at State Software. On the other hand, this clause led to license compatibility problems of the JSON license with other open - source licenses. A precursor to the JSON libraries was used in a children 's digital asset trading game project named Cartoon Orbit at Communities.com ( the State co-founders had all worked at this company previously ) for Cartoon Network, which used a browser side plug - in with a proprietary messaging format to manipulate DHTML elements ( this system is also owned by 3DO ). Upon discovery of early 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 Sun Microsystems, Amazon.com and EDS. The JSON.org Web site was launched in 2002. In December 2005, Yahoo ! began offering some of its Web services in JSON. JSON was originally intended to be a subset of the JavaScript scripting language ( specifically, Standard ECMA - 262 3rd Edition -- December 1999 ) and is commonly used with Javascript, but it is a language - independent data format. Code for parsing and generating JSON data is readily available in many programming languages. JSON 's Web site lists JSON libraries by language. Though JSON was originally advertised and believed to be a strict subset of JavaScript and ECMAScript, it inadvertently allows some unescaped characters in strings that are illegal in JavaScript and ECMAScript strings. See Data portability issues below. JSON itself became an ECMA international standard in 2013 as the ECMA - 404 standard. In the same year RFC 7158 used ECMA - 404 as reference. In 2014 RFC 7159 became the main reference for JSON 's internet uses ( ex. MIME application / json ), and obsoletes RFC 4627 and RFC 7158 ( but preserving ECMA - 262 and ECMA - 404 as main references ). Data types, syntax and example JSON 's basic data types are : Number : a signed decimal number that may contain a fractional part and may use exponential E notation, but can not include non-numbers like NaN. The format makes no distinction between integer and floating - point. JavaScript uses a double - precision floating - point format for all its numeric values, but other languages implementing JSON may encode numbers differently. String : a sequence of zero or more Unicode characters. Strings are delimited with double - quotation marks and support a backslash escaping syntax. Boolean : either of the values true or false Array : an ordered list of zero or more values, each of which may be of any type. Arrays use square bracket notation with elements being comma - separated. Object : an unordered collection of name / value pairs where the names ( also called keys ) are strings. Since objects are intended to represent associative arrays, it is recommended, though not required, that each key is unique within an object. 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. null : An empty value, using the word null Limited whitespace is allowed and ignored around or between syntactic elements ( values and punctuation, but not within a string value ). Only 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 any syntax for comments. Early versions of JSON ( such as specified by RFC 4627 ) required that a valid JSON `` document '' must consist of only an object or an array type, which could contain other types within them. Example The following example shows a possible JSON representation describing a person. ( `` firstName '' : `` John '', `` lastName '' : `` Smith '', `` isAlive '' : true, `` age '' : 25, `` address '' : ( `` streetAddress '' : `` 21 2nd Street '', `` city '' : `` New York '', `` state '' : `` NY '', `` postalCode '' : `` 10021 - 3100 '' ), `` phoneNumbers '' : ( ( `` type '' : `` home '', `` number '' : `` 212 555 - 1234 '' ), ( `` type '' : `` office '', `` number '' : `` 646 555 - 4567 '' ), ( `` type '' : `` mobile '', `` number '' : `` 123 456 - 7890 '' ) ), `` children '' : ( ), `` spouse '' : null ) Data portability issues Although Douglas Crockford originally claimed that JSON is a strict subset of JavaScript, his specification actually allows valid JSON documents that are invalid JavaScript. Specifically, JSON allows the Unicode line terminators U + 2028 LINE SEPARATOR and U + 2029 PARAGRAPH SEPARATOR to appear unescaped in quoted strings, while JavaScript does not. This is a consequence of JSON disallowing only `` control characters ''. For maximum portability, these characters should be backslash - escaped. This subtlety is important when generating JSONP. JSON documents can be encoded in UTF - 8, UTF - 16 or UTF - 32, the default encoding being UTF - 8 ( I - JSON only supports UTF - 8 ). These encodings support the full Unicode character set, including those characters outside the Basic Multilingual Plane ( U + 10000 to U + 10FFFF ). However, if escaped, those characters must be written using UTF - 16 surrogate pairs, a detail missed by some JSON parsers. For example, to include the Emoji character U + 1F602 😂 FACE WITH TEARS OF JOY in JSON : ( `` face '' : `` 😂 '' ) / / or ( `` face '' : `` \uD83D \uDE02 '' ) Numbers in JSON are agnostic with regard to their representation within programming languages. No differentiation is made between an integer and floating - point value : some implementations may treat 42, 42.0, and 4.2 E + 1 as the same number while others may not. Furthermore, no requirements are made regarding implementation issues such as overflow, underflow, loss of precision, or rounding. Additionally, JSON says nothing about the treatment of signed zeros : whether 0.0 is distinct from - 0.0. Most implementations that use the IEEE 754 floating - point standard, including JavaScript, preserve signed zeros ; but not all JSON implementations may do so. Using JSON in JavaScript As of 2017, all major browsers support at least the fifth edition ECMAScript which provides a safe and fast method of decoding JSON : var p = JSON. parse ( json_string ) ; Unsupported native data types JavaScript syntax defines several native data types that are not included in the JSON standard : Map, Set, Date, Error, Regular Expression, Function, Promise, and undefined. These JavaScript data types must be represented by some other data format, with the programs on both ends agreeing on how to convert between the types. As of 2011, there are some de facto standards, e.g., converting from Date to String, but none universally recognized. Other languages may have a different set of native types that must be serialized carefully to deal with this type of conversion. Schema and metadata JSON Schema 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. JSON Schema is based on the concepts from 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 is self - describing. It is described in an Internet Draft currently in its 6th draft, which was released on April 15, 2017. Draft 4 expired on August 4, 2013, but continued to be used in the lapse of more than 3 years between its expiration and the release of Draft 5. There are several validators available for different programming languages, each with varying levels of conformance. There is no standard file extension, but some have suggested. schema. json. Example JSON Schema ( draft 4 ) : ( `` $ schema '' : `` http://json-schema.org/schema# '', `` title '' : `` Product '', `` type '' : `` object '', `` required '' : ( `` id '', `` name '', `` price '' ), `` properties '' : ( `` id '' : ( `` type '' : `` number '', `` description '' : `` Product identifier '' ), `` name '' : ( `` type '' : `` string '', `` description '' : `` Name of the product '' ), `` price '' : ( `` type '' : `` number '', `` minimum '' : 0 ), `` tags '' : ( `` type '' : `` array '', `` items '' : ( `` type '' : `` string '' ) ), `` stock '' : ( `` type '' : `` object '', `` properties '' : ( `` warehouse '' : ( `` type '' : `` number '' ), `` retail '' : ( `` type '' : `` number '' ) ) ) ) ) The JSON Schema above can be used to test the validity of the JSON code below : ( `` id '' : 1, `` name '' : `` Foo '', `` price '' : 123, `` tags '' : ( `` Bar '', `` Eek '' ), `` stock '' : ( `` warehouse '' : 300, `` retail '' : 20 ) ) MIME type The official MIME type for JSON text is `` application / json ``, and most modern implementations have adopted this. The ( unofficial ) MIME type `` text / json '' or the content - type `` text / javascript '' also get legacy support by many service providers, browsers, servers, web applications, libraries, frameworks, and APIs. Notable examples include the Google Search API, Yahoo !, Flickr, Facebook API, Lift framework, Dojo Toolkit 0.4, etc. Applications JSON - RPC JSON - RPC is a 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. Example of a JSON - RPC 2.0 request and response using positional parameters. -- > ( `` jsonrpc '' : `` 2.0 '', `` method '' : `` subtract '', `` params '' : ( 42, 23 ), `` id '' : 1 ) < -- ( `` jsonrpc '' : `` 2.0 '', `` result '' : 19, `` id '' : 1 ) AJAJ Asynchronous JavaScript and JSON ( or AJAJ ) refers to the same dynamic web page methodology as 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 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 search box, client - side code then sends to the server, which immediately responds with a drop - down list of matching database items. The following JavaScript code is an example of a client using XMLHttpRequest to request data in JSON format from a server. ( The server - side programming is omitted ; it must be set up to service requests to the url containing a JSON - formatted string. ) var my_JSON_object ; var http_request = new XMLHttpRequest ( ) ; http_request. open ( `` GET '', url, true ) ; http_request. responseType = `` json '' ; http_request. onreadystatechange = function ( ) ( var done = 4, ok = 200 ; if ( http_request. readyState = = = done && http_request. status = = = ok ) ( my_JSON_object = http_request. response ; ) ) ; http_request. send ( null ) ; Security considerations JSON is intended as a data serialization format. However, its design as a non-strict subset of JavaScript can lead to the misconception that it is safe to pass JSON strings to the JavaScript eval ( ) function. This is not safe, due to the fact that certain valid JSON strings are actually not valid JavaScript code. To avoid the many pitfalls caused by executing arbitrary code from the internet, a new function, JSON. parse ( ) was first added to the fifth edition of ECMAScript, which as of 2017 is supported by all major browsers. For non-supported browsers, an API - compatible JavaScript library is provided by Douglas Crockford. Vulnerabilities in specific JSON parsers Various JSON parser implementations have suffered from denial - of - service attack and mass assignment vulnerability. Object references The JSON standard does not support object references, but an IETF draft standard for JSON - based object references exists. The Dojo Toolkit supports object references using standard JSON ; specifically, the dojox. json. ref module provides support for several forms of referencing including circular, multiple, inter-message, and lazy referencing. Alternatively, non-standard solutions exist such as the use of Mozilla JavaScript Sharp Variables. However this functionality became obsolete with JavaScript 1.8. 5 and was removed in Firefox version 12. Comparison with other formats See also : Comparison of data serialization formats 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. Apart from XML, examples could include OGDL, YAML and CSV. Also, Google Protocol Buffers can fill this role, although it is not a data interchange language. YAML YAML version 1.2 is a superset of JSON ; prior versions were `` not strictly compatible ''. For example, escaping a slash ( / ) with a backslash ( ) is valid in JSON, but was not valid in YAML. ( This is common practice when injecting JSON into HTML to protect against cross-site scripting attacks. ) Nonetheless, many YAML parsers can natively parse the output from many JSON encoders. 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 several ways. The most expansive form using tag pairs results in a much larger representation than JSON, but if data is stored in attributes and ' short tag ' form where the closing tag is replaced with ' / > ', the representation is often about the same size as JSON or just a little larger. If the data is compressed using an algorithm like gzip, there is little difference because compression is good at saving space when a pattern is repeated. XML also has the concept of schema. This permits strong typing, user - defined types, predefined tags, and formal structure, allowing for formal validation of an XML stream in a portable way. There is, however, an IETF draft proposal for a schema system for JSON. XML supports comments, but JSON does not. Samples JSON sample ( `` firstName '' : `` John '', `` lastName '' : `` Smith '', `` age '' : 25, `` address '' : ( `` streetAddress '' : `` 21 2nd Street '', `` city '' : `` New York '', `` state '' : `` NY '', `` postalCode '' : `` 10021 '' ), `` phoneNumber '' : ( ( `` type '' : `` home '', `` number '' : `` 212 555 - 1234 '' ), ( `` type '' : `` fax '', `` number '' : `` 646 555 - 4567 '' ) ), `` gender '' : ( `` type '' : `` male '' ) ) Both of the following examples carry the same kind of information as the JSON example above in different ways. YAML sample The JSON code above is also entirely valid YAML. YAML also offers an alternative syntax intended to be more human - accessible by replacing nested delimiters like ( ), ( ), and `` marks with off - side indentation. -- - firstName : John lastName : Smith age : 25 address : streetAddress : 21 2nd Street city : New York state : NY postalCode : ' 10021 ' phoneNumber : - type : home number : 212 555 - 1234 - type : fax number : 646 555 - 4567 gender : type : male XML samples < person > < firstName > John < / firstName > < lastName > Smith < / lastName > < age > 25 < / age > < address > < streetAddress > 21 2nd Street < / streetAddress > < city > New York < / city > < state > NY < / state > < postalCode > 10021 < / postalCode > < / address > < phoneNumber > < type > home < / type > < number > 212 555 - 1234 < / number > < / phoneNumber > < phoneNumber > < type > fax < / type > < number > 646 555 - 4567 < / number > < / phoneNumber > < gender > < type > male < / type > < / gender > < / person > The properties can also be serialized using attributes instead of tags : < person firstName = `` John '' lastName = `` Smith '' age = `` 25 '' > < address streetAddress = `` 21 2nd Street '' city = `` New York '' state = `` NY '' postalCode = `` 10021 '' / > < phoneNumber type = `` home '' number = `` 212 555 - 1234 '' / > < phoneNumber type = `` fax '' number = `` 646 555 - 4567 '' / > < gender type = `` male '' / > < / person > The XML encoding may therefore be comparable in length to the equivalent JSON encoding. A wide range of XML processing technologies exist, from the Document Object Model to XPath and XSLT. XML can also be styled for immediate display using CSS. XHTML is a form of XML so that elements can be passed in this form ready for direct insertion into webpages using client - side scripting. See also JSON Streaming Other formats HOCON -- Human - Optimized Config Object Notation, a superset of JSON YAML -- Another datastorage format that is a superset of JSON S - expression -- the comparable LISP format for trees as text. JSONP -- JSON with Padding, a pattern of usage commonly employed when retrieving JSON across domains GeoJSON -- an open format for encoding a variety of geographic data structures JSON - LD -- JavaScript Object Notation for Linked Data, currently a W3C Recommendation JSON - RPC SOAPjr -- a hybrid of SOAP and JR ( JSON - RPC ) JsonML Binary encodings for JSON BSON MessagePack Smile UBJSON EXI4JSON ( EXI for JSON ) -- representation by means of the Efficient XML Interchange ( EXI ) standard Implementations : Jayrock -- an open source implementation of JSON for the. NET Framework. Ember data server implementations for PHP, Node. js, Ruby, Python, Go,. NET and Java. Jackson_ ( API ) for Java. Other Comparison of data serialization formats Jq ( programming language ) Notes Jump up ^ The undefined type was left out of the JSON standard, and one finds suggestions that null be used instead. In fact, the current standard says that for a sparse array such as : var v = ( 0 ) ; v ( 3 ) = 3 ; which behaves in JavaScript as if it were : var vx = ( 0, undefined, undefined, 3 ) ; with the undefined entries being only implicit rather than explicit, should translate to JSON as if it were : var vx = ( 0, null, null, 3 ) ; with explicit null fillers for the undefined entries. Furthermore, in JavaScript ( a : undefined ) often behaves the same as ( ). Both translate as `` ( ) '' in JSON. However undefined as an explicit property value does have use in JavaScript inheritance situations such as : var x = ( a : 1 ) ; var xi = Object. create ( x ) ; xi. a = undefined ; where the inheritance of x ' s property a is overridden in xi and makes it pretty much behave as if nothing was inherited. JSON. stringify itself ignores inherited values - it only translates the enumerable own properties as given by Object. keys ( y ). The default stringification, while not encoding inheritance, can ( except for undefined values ) encode enough of an object to reconstruct it in an environment that knows what inheritance it should have. To encode JavaScript objects that contain explicit undefined values a convention for representing undefined must be established, such as mapping it to the string `` UNDEFINED ''. One can then pass JSON. stringify the optional replacer argument to translate with this convention : var y = ( a : undefined ) ; var ys = JSON. stringify ( y, function ( k, v ) ( return ( v = = = undefined ) ? `` UNDEFINED '' : v ) ) ; Converting this JSON back into JavaScript is not as straightforward. While JSON. parse can take an optional reviver argument that is, essentially, the inverse of a replacer, it ca n't be used in this situation. If that function returns undefined, the JSON. parse logic interprets this to mean to not define a property rather than define one with a undefined value. Instead one has to explicitly post process the result from JSON. parse replacing each `` UNDEFINED '' with undefined. References Jump up ^ `` Doug Crockford `` Google Tech Talks : JavaScript : The Good Parts '' ``. 7 February 2009. Jump up ^ `` A Modern Reintroduction To AJAX ''. Retrieved 12 April 2017. Jump up ^ Bray, Tim. `` JSON Redux AKA RFC7159 ''. Ongoing. Retrieved 16 March 2014. Jump up ^ Bray, Tim ( ed. ), The I - JSON Message Format, Internet Engineering Task Force ( IETF ), RFC 7493 Jump up ^ `` Douglas Crockford -- The JSON Saga ''. YouTube. 28 August 2011. Retrieved 23 September 2016. Jump up ^ `` Chip Morningstar Biography ''. n.d. Jump up ^ `` State Software Breaks Through Web App Development Barrier With State Application Framework : Software Lets Developers Create Truly Interactive Applications ; Reduces Costs, Development Time and Improves User Experience ''. PR Newswire. February 12, 2002. Jump up ^ Apache and the JSON license on LWN.net by Jake Edge ( November 30, 2016 ) Jump up ^ Yahoo !. `` Using JSON with Yahoo ! Web services ''. Archived from the original on October 11, 2007. Retrieved July 3, 2009. Jump up ^ Crockford, Douglas ( May 28, 2009 ). `` Introducing JSON ''. json.org. Retrieved July 3, 2009. Jump up ^ Douglas Crockford ( 2016 - 07 - 10 ). `` JSON in JavaScript ''. Archived from the original on 2016 - 07 - 10. Retrieved 2016 - 08 - 13. CS1 maint : BOT : original - url status unknown ( link ) ^ Jump up to : `` The JSON Data Interchange Format '' ( PDF ). ECMA International. October 2013. Retrieved 23 September 2016. ^ Jump up to : `` JSON Web Token ( JWT ) ''. IETF. May 2015. Retrieved 23 September 2016. Jump up ^ Holm, Magnus ( 15 May 2011 ). `` JSON : The JavaScript subset that is n't ''. The timeless repository. Retrieved 23 September 2016. Jump up ^ `` Standard ECMA - 262 ''. ecma-international.org. Retrieved 13 September 2015. Jump up ^ `` jquery - Format a Microsoft JSON date ? - Stack Overflow ''. stackoverflow.com. Retrieved 13 September 2015. Jump up ^ `` Tales from the Evil Empire - Dates and JSON ''. asp.net. Retrieved 13 September 2015. Jump up ^ `` JSON Schema and Hyper - Schema ''. json-schema.org. Retrieved 13 September 2015. Jump up ^ `` draft - wright - json - schema - 01 - JSON Schema : A Media Type for Describing JSON Documents ''. json-schema.org/. Retrieved 23 July 2017. Jump up ^ `` draft - zyp - json - schema - 04 - JSON Schema : core definitions and terminology ''. ietf.org. Retrieved 17 March 2016. Jump up ^ `` JSON Schema Software ''. json-schema.org. Retrieved 13 September 2015. Jump up ^ http://stackoverflow.com/a/10507586/287948 Jump up ^ `` Media Types ''. iana.org. Retrieved 13 September 2015. ^ Jump up to : `` Handle application / json & text / json by benschwarz Pull Request # 2 mislav / faraday - stack ''. GitHub. Retrieved 13 September 2015. Jump up ^ `` Yahoo !, JavaScript, and JSON ''. ProgrammableWeb. Retrieved 13 September 2015. Jump up ^ `` Make JSON requests allow text / javascript content by jakeboxer Pull Request # 148 AFNetworking / AFNetworking ''. GitHub. Retrieved 13 September 2015. Jump up ^ `` lift / Req. scala at master lift / lift GitHub ''. GitHub. Retrieved 13 September 2015. Jump up ^ `` BrowserIO. js in legacy / branches / 0.4 / src / io -- Dojo Toolkit ''. dojotoolkit.org. Retrieved 13 September 2015. Jump up ^ `` JSON : The JavaScript subset that is n't ''. Magnus Holm. Retrieved 16 May 2011. Jump up ^ `` ECMAScript Fifth Edition '' ( PDF ). Retrieved March 18, 2011. Jump up ^ `` Denial of Service and Unsafe Object Creation Vulnerability in JSON ( CVE - 2013 - 0269 ) ''. Retrieved January 5, 2016. Jump up ^ `` Microsoft. NET Framework JSON Content Processing Denial of Service Vulnerability ''. Retrieved January 5, 2016. Jump up ^ Zyp, Kris ( September 16, 2012 ). Bryan, Paul C., ed. `` JSON Reference : draft - pbryan - zyp - json - ref - 03 ''. Internet Engineering Task Force. Jump up ^ Zyp, Kris. `` dojox. json. ref ''. Dojo. Jump up ^ Zyp, Kris ( June 17, 2008 ). `` JSON referencing in Dojo ''. SitePen. Retrieved July 3, 2009. Jump up ^ von Gaza, Tys ( Dec 7, 2010 ). `` JSON referencing in jQuery ''. NUBUNTU. Archived from the original on May 7, 2015. Retrieved Dec 7, 2010. Jump up ^ `` Sharp variables in JavaScript ''. Mozilla Developer Network. April 4, 2015. Retrieved 21 April 2012. Jump up ^ `` JSON : The Fat - Free Alternative to XML ''. json.org. Retrieved 14 March 2011. ^ Jump up to : `` YAML Ai n't Markup Language ( YAML TM ) Version 1.2 ''. yaml.org. Retrieved 13 September 2015. Jump up ^ `` JSON Schema ''. json-schema.org. Retrieved 2017 - 04 - 10. Jump up ^ Saternos, Casimir ( 2014 ). Client - server web apps with Javascript and Java. p. 45. ISBN 9781449369316. Jump up ^ Oren Ben - Kiki ; Clark Evans ; Ingy döt Net. `` YAML Ai n't Markup Language ( YAML TM ) Version 1.2 ''. Retrieved 29 August 2015. External links Find more aboutJSONat Wikipedia 's sister projects Definitions from Wiktionary Media from Commons Textbooks from Wikibooks Official website `` ECMA - 404 JSON Data Interchange Format '' ( pdf ). ECMA Int'l. RFC 7159, JSON Data Interchange Format RFC 7049, Concise Binary Object Representation ( CBOR ) for JSON `` JSON Validator ''. JSON lint. `` JSON Formatter ''. Dev Gadget. Online tools. Data exchange formats Human readable formats Atom XML YAML JSON RDF Rebol RSS OWL Binary formats AMF ASN. 1 BSON CBOR MessagePack Protocol Buffers LCCN : sh2014000515 GND : 1105592812 Retrieved from `` https://en.wikipedia.org/w/index.php?title=JSON&oldid=802530299 '' Categories : Computer - related introductions in 2001 Ajax ( programming ) Data serialization formats JSON Markup languages Configuration files Open formats Hidden categories : CS1 maint : BOT : original - url status unknown Pages using deprecated image syntax Articles containing potentially dated statements from 2017 All articles containing potentially dated statements All articles with unsourced statements Articles with unsourced statements from December 2016 Wikipedia articles needing factual verification from January 2017 All articles with failed verification Articles with failed verification from January 2017 Articles containing potentially dated statements from 2011 Official website different in Wikidata and Wikipedia Wikipedia articles with LCCN identifiers Wikipedia articles with GND identifiers Talk Contents About Wikipedia Wikibooks Azərbaycanca Български Català Čeština Deutsch Eesti Español Euskara فارسی Français Galego 한국어 Հայերեն हिन्दी Bahasa Indonesia Italiano עברית Кыргызча Latviešu Lietuvių Magyar മലയാളം Bahasa Melayu Nederlands 日本 語 Norsk Polski Português Română Русский Shqip Simple English Српски / srpski Suomi Svenska தமிழ் ไทย Türkçe Українська Tiếng Việt 中文 Edit links This page was last edited on 26 September 2017, at 19 : 09. Text is available under the Creative Commons Attribution - ShareAlike License ; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia ® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. About Wikipedia

Question: who is credited with getting the json movement started
Answer: Douglas Crockford