Jump to content

Talk:JSON

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Uneval

[edit]

Uneval() partially produces JSON; I believe what it 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. ... — Preceding unsigned comment added by Daemonicky (talkcontribs) 15:50, September 5, 2011 (UTC)

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.

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.

Dmeranda (talk) — Preceding undated comment added 06:46, March 16, 2014 (UTC)

[edit]

link #37 to the schema spec results in a 404 error: https://json-schema.org/latest/json-schema-core.html 173.76.101.158 (talk) 18:59, 21 March 2024 (UTC)[reply]

Should be fixed now. Since that reference was backing up a claim about what the most reason draft name is, I changed the link to the official draft listing page. If you're looking for that specific spec document, I think this is it. StereoFolic (talk) 14:55, 22 March 2024 (UTC)[reply]

JSONPath draft article

[edit]

The community here may be interested in reviewing and/or editing the draft article on JSONPath. Glyn normington (talk) 16:16, 24 March 2024 (UTC)[reply]

Snake case and camel case

[edit]

In JavaScript it is standard to use camel case for identifiers such as properties in objects. In json this not a requirement as there are not identifiers just strings. I wonder if this should be mentioned somewhere as it is important when converting objects in JSON notation to JavaScript objects and vv. Theking2 (talk) 15:11, 29 May 2024 (UTC)[reply]