Talk:JSON

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

Uneval[edit]

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

"JSON originated at company founded in 2013"[edit]

The acronym originated at State Software, a company co-founded by Douglas Crockford and others in March 2013.

This is severely misleading since there is usage of the term before that: https://web.archive.org/web/20060226161009/http://www.json.org/js.html

So I removed this.

--189.217.88.26 (talk) 20:35, 7 December 2022 (UTC)[reply]


rewrite intro to appropriate level[edit]

like many if not most STEM articles on wiki, the intro is not written for the general reader, but for someone who is already rather knowledgable thank you — Preceding unsigned comment added by 50.245.17.105 (talk) 17:21, 2 February 2023 (UTC)[reply]

Two kinds of derivative formats[edit]

Currently the Derivatives section lists together formats that I could put into two distinct categories:

  • ones that use JSON for their underlying structure and focus on a generally narrower domain, like JSON-LD or GeoJSON
  • ones that share a similar goal, but different representation from JSON, like SMILE or UBJSON

I think the article should have some kind of explicit distinction between the two kinds, however I'm not sure how to best approach implementing that.

Penta1ynx (talk) 17:21, 25 May 2023 (UTC)[reply]

broken link[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]