JSON: Difference between revisions
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | =External= | ||
* https://www.ietf.org/rfc/rfc7159.txt | |||
* The application/json Media Type for JavaScript Object Notation (JSON) https://www.ietf.org/rfc/rfc4627.txt RFC 4627 | * The application/json Media Type for JavaScript Object Notation (JSON) https://www.ietf.org/rfc/rfc4627.txt RFC 4627 | ||
* http://json.org | * http://json.org | ||
=Internal= | |||
* [[Serialization]] | |||
=Overview= | =Overview= | ||
JSON stands for JavaScript Object Notation. It is a standardized text format for serialization of structured data. It is described by [https://www.ietf.org/rfc/rfc4627.txt RFC 4627]. It defines a small set of formatting rules for portable representation of simple data structures such as key-value pair collections, lists, etc. JSON is also an ''internet media type'', a text based content type that can be directly interpreted by JavaScript. It is the preferred exchange format for JavaScript-based web applications. The MIME media type for JSON is "application/json". | JSON stands for JavaScript Object Notation. It is a standardized text format for serialization of structured data. It is described by [https://www.ietf.org/rfc/rfc4627.txt RFC 4627] <font color=darkkhaki>and RFC 7159. What is the relationship?</font>. | ||
It defines a small set of formatting rules for portable representation of simple data structures such as key-value pair collections, lists, etc. JSON is also an '''internet media type''', a text based content type that can be directly interpreted by JavaScript. It is the preferred exchange format for JavaScript-based web applications. The MIME media type for JSON is "application/json". | |||
JSON uses attribute-value pairs. | |||
JSON has a few advantages as a serialization format: there are serialization-deserialization libraries in most programming languages, all modern browsers support it, and it is human-readable. There are disadvantages as well: JSON is not size-efficient, and the serialization-deserialization speed is not among the best. Other serialization protocols are faster. | |||
=Example= | =Example= | ||
| Line 15: | Line 23: | ||
* [[JSON Concepts|Concepts]] | * [[JSON Concepts|Concepts]] | ||
* [[JSONPath]] | |||
* [[JSON_processing_in_Python|JSON in Python]] | |||
* [[JSON in Go]] | |||
=Frameworks= | =Frameworks= | ||
| Line 20: | Line 31: | ||
* [[Jackson]] | * [[Jackson]] | ||
* [[gson]] | * [[gson]] | ||
Latest revision as of 20:04, 4 October 2023
External
- https://www.ietf.org/rfc/rfc7159.txt
- The application/json Media Type for JavaScript Object Notation (JSON) https://www.ietf.org/rfc/rfc4627.txt RFC 4627
- http://json.org
Internal
Overview
JSON stands for JavaScript Object Notation. It is a standardized text format for serialization of structured data. It is described by RFC 4627 and RFC 7159. What is the relationship?.
It defines a small set of formatting rules for portable representation of simple data structures such as key-value pair collections, lists, etc. JSON is also an internet media type, a text based content type that can be directly interpreted by JavaScript. It is the preferred exchange format for JavaScript-based web applications. The MIME media type for JSON is "application/json".
JSON uses attribute-value pairs.
JSON has a few advantages as a serialization format: there are serialization-deserialization libraries in most programming languages, all modern browsers support it, and it is human-readable. There are disadvantages as well: JSON is not size-efficient, and the serialization-deserialization speed is not among the best. Other serialization protocols are faster.