From Wikipedia, the free encyclopedia
Jump to navigation Jump to search


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.”

How do you reach Mr Crockford...[edit] tell him that his website is broken? Diagrams are super large now, links to sub pages (eg /examples.html) are missing. (talk) 08:18, 5 November 2019 (UTC)

Examples - added note highlighting that metadata is included in XML examples[edit]

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) (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). (talk) 01:17, 24 November 2019 (UTC)

JSON Schema[edit]

There are appear to be two competing standards for JSON Schema currently under consideration by the IETF: vs

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 (talkcontribs) 14:29, 19 November 2019 (UTC)

Proposed merge of JSON-WSP into JSON[edit]

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)