|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 automatically 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.”
How do you reach Mr Crockford...
Examples - added note highlighting that metadata is included in XML examples
I added the point of metadata supported in the XML format. I am not a proponent of XML, preferring json, but it is an important difference that IMO should be highlighted in the samples section, and not just in the comparison discussion section. (//mawi) 18.104.22.168 (talk) 12:42, 5 November 2019 (UTC)
- Did you write: "Note that the XML examples encode metadata (naming of person, address, etc.), which the JSON example above does not."? It's not clear what you mean. There's nothing in the XML example that isn't in the JSON example. You make it sound like there IS metadata in the XML example, not that the option is there (unused). 22.214.171.124 (talk) 01:17, 24 November 2019 (UTC)
There are appear to be two competing standards for JSON Schema currently under consideration by the IETF:
The JSON schema section does not mention this nor indicate which of these drafts should be taken more seriously. — Preceding unsigned comment added by Greatrsg (talk • contribs) 14:29, 19 November 2019 (UTC)
As it stands, a single paragraph in JSON should be enough to cover this topic. Keeping the page history of JSON-WSP and redirecting it to JSON is far better than deletion. davidwr/(talk)/(contribs) 19:25, 19 August 2020 (UTC)