From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject JavaScript  
This article is within the scope of WikiProject JavaScript, a collaborative effort to improve the coverage of articles related to JavaScript, and to the development of user scripts for use on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the quality scale.
 ???  This article has not yet received a rating on the importance scale.


Uneval() partialy produces JSON, I believe what ti produces is subset of JSON (don't have proof). See . This should be mentioned with problems and what to avoid and such. ...

Removing paragraph about zip codes[edit]

I am removing the paragraph which discusses the pitfalls of representing zip codes as either numbers or as strings. This really has little to do with JSON and does not belong here.Dmeranda (talk)

“One potential pitfall of the free-form nature of JSON comes from the ability to write numbers as either numeric literals or quoted strings. For example, ZIP Codes in the northeastern U.S. begin with zeroes (for example, 06511 for New Haven, Connecticut). If written with quotes by one programmer but not by another, the leading zero could be dropped when exchanged between systems, when searched for within the same system, or when printed. In addition, postal codes in the U.S. are numbers but other countries use letters as well. The use of a JSON Schema (see below) should reduce this as a type of problem.”

Comparison with other formats[edit]

This is to suggest adding a comparison to the BER (Basic Encoding Rules) of ASN.1.

--Jack Waugh (talk) 18:23, 19 August 2018 (UTC)

First paragraph incorrect[edit]

The value 7 is a valid JSON document, which evaluates to the number 7. This is neither an array nor a data object consistent of attribute-value pairs. Such conflicts with the opening sentence:

> In computing, JavaScript Object Notation (JSON) (/ˈdʒeɪsən/ "Jason",[1] /dʒeɪˈ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.[2]

Full Decent (talk) 01:24, 20 May 2019 (UTC)

JSON Path[edit]

There is no mention of JSON Paths in the article, which would be handy perhaps. So far the closest to a specification I could find is and it's licensed under Creative Commons, could be a start? PatMartinez (talk) 16:06, 7 June 2019 (UTC)