JSON

More documents

Recommendations

Info

Versionless • JSON has no version number. • No revisions to the JSON grammar are anticipated. • JSON is very stable.
Rules • A JSON decoder must accept all well-formed JSON text. • A JSON decoder may also accept non-JSON text. • A JSON encoder must only produce well-formed JSON text. • Be conservative in what you do, be liberal in what you accept from others.
Page 1 and 2: JSON The x in Ajax Douglas Crockfor
Page 3 and 4: Data Interchange • The key idea i
Page 5 and 6: JSON • JavaScript Object Notation
Page 7 and 8: JSON Is Not... • JSON is not a do
Page 9 and 10: Languages • Chinese • English
Page 11 and 12: Object Quasi-Literals • JavaScrip
Page 13 and 14: Value
Page 15 and 16: String
Page 17 and 18: Number
Page 19 and 20: null • A value that isn't anythin
Page 21 and 22: Object
Page 23 and 24: Object { } "name": "Jack B. Nimble"
Page 25 and 26: Array
Page 27 and 28: Arrays vs Objects • Use objects w
Page 29: Character Encoding • Strictly UNI
Page 33 and 34: JSON is the X in Ajax
Page 35 and 36: JSON in Ajax • XMLHttpRequest Obt
Page 37 and 38: JSON in Ajax • Secret • Reques
Page 39 and 40: JSONRequest • A new facility. •
Page 41 and 42: JSONRequest • Requests are transm
Page 43 and 44: ECMAScript Fourth Ed. • New Metho
Page 45 and 46: supplant String.prototype.supplant
Page 47 and 48: http://goessner.net/articles/jsont/
Page 49 and 50: JSON Looks Like Data • JSON's sim
Page 51 and 52: JSON Doesn't Have Namespaces • Ev
Page 53 and 54: Namespace {"section": "title": "Boo
Page 55 and 56: JSON is Not Extensible • It does
Page 57 and 58: Data Interchange • JSON is a simp
Page 59 and 60: Going Meta • By adding one level
Page 61 and 62: Going Meta • Possible meta-types:
Page 63 and 64: The Mashup Security Problem • Mas
Page 65 and 66: The Mashup Security Solution • A
Page 67 and 68: The Mashup Security Solution • I
Page 69 and 70: The Mashup Security Solution • C
Page 71: www.JSON.org

JSON

Create successful ePaper yourself

Delete template?

Save as template?