|This is the talk page for discussing improvements to the JSON article.
This is not a forum for general discussion of the article's subject.
|This article is of interest to the following WikiProjects:|
Threads older than 150 days may be archived by .
Uneval() partialy produces JSON, I believe what ti produces is subset of JSON (don't have proof). See http://movieos.org/blog/2006/04/uneval-does-not-produce-json/ . This should be mentioned with problems and what to avoid and such. ...
Removing paragraph about zip codes
- “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
This is to suggest adding a comparison to the BER (Basic Encoding Rules) of ASN.1.
First paragraph incorrect
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:
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 https://goessner.net/articles/JsonPath/ and it's licensed under Creative Commons, could be a start? PatMartinez (talk) 16:06, 7 June 2019 (UTC)