Description-of-JSON
Description::
JSON is a data-representation computer-language.
[HmnSgm.2017-11-03]
===
JSON (JavaScript Object Notation) is a lightweight data-interchange format.
It is easy for humans to read and write.
It is easy for machines to parse and generate.
It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999.
JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others.
These properties make JSON an ideal data-interchange language.
[http://www.json.org/]
Name::
* cpt.JavaScript-Object-Nonation-(JSON),
* cpt.JSON,
* cpt.JSON--data-format,
* cpt.JSON--data-representation--computer-language,
* cpt.JSON-format,
* cpt.JSON-language,
Archetype-of-JSON
Description::
JSON-archetype is any information|data (human or computer) we want to represent in JSON-language.
The-JSON-language most is-used to represent data of different computer-languages for inter-language communication.
Name::
* cpt.JSON'archetype,
Document-of-JSON (model, JSON-doc)
Description::
JSON-document is a-document written in JSON-language that represents a-JSON-archetype.
Name::
* cpt.JSON'doc,
* cpt.JSON'document,
* cpt.JSON'model,
* cpt.JSON-doc,
JSON-doc'Semantic-unit
Description::
Semantic-units are unit constructs that REPRESENT something in archetype.
Name::
* cpt.JSON'semantic-unit,
* cpt.JSON-doc'semantic-unit,
* cpt.JSON-sut,
* cpt.semantic-unit.JSON,
Specific::
There-are only 6 semantic-units.
1) null--semantic-unit,
2) Boolean--semantic-unit,
3) String--semantic-unit,
4) Number--semantic-unit,
5) Array--semantic-unit,
6) Object--semantic-unit,
JSON-sut.null
Description::
null is a-genericNo semantic-unit that represents 'zero'-information.
Name::
* cpt.JSON'null,
* cpt.JSON-sut.null,
JSON-sut.Boolean
Description::
Boolean is a-generic semantic-unit with specifics true and false.
Name::
* cpt.JSON'boolean,
* cpt.JSON'false,
* cpt.JSON'true,
* cpt.JSON-sut.boolean,
* cpt.JSON-sut.false,
* cpt.JSON-sut.true,
JSON-sut.String
Description::
A-string is a-generic semantic-unit that represents human-text enclosed in double-quotes.
Example: "some text"
"some \"text\" with escapes"
[HmnSgm.2017-11-03]
===
A string is a sequence of zero or more Unicode characters, wrapped in double quotes, using backslash escapes.
A character is represented as a single character string.
A string is very much like a C or Java string.
[http://www.json.org/]
Name::
* cpt.JSON'string,
* cpt.JSON-sut.string,
JSON-string'grammar
string
string
""
" chars "
chars
char
char chars
char
any-Unicode-character-except-"-or-\-or-control-character
\"
\\
\/
\b
\f
\n
\r
\t
\u four-hex-digits
JSON-sut.Number
Description::
A-number is a-generic semantic-unit that represents numbers.
Example: 123 1.2
123e3 1.2e3
[HmnSgm.2017-11-03]
===
A number is very much like a C or Java number, except that the octal and hexadecimal formats are not used.
[http://www.json.org/]
Name::
* cpt.JSON'number,
* cpt.JSON-sut.number,
JSON-sut.Array
Description::
Array is a-generic semantic-unit which contains an-ordered-set of other semantic-units.
Example: ["string", 5, [1, 2], true]
[HmnSgm.2017-11-03]
===
An array is an ordered collection of values.
An array begins with [ (left bracket) and ends with ] (right bracket).
Values are separated by , (comma).
[http://www.json.org/]
Name::
* cpt.JSON'array,
* cpt.JSON-array,
* cpt.JSON-sut.array,
JSON-array'grammar
Name::
* cpt.JSON-array'grammar,
array
[]
[ elements ]
elements
value
value , elements
JSON-sut.Object
Description::
Object is a-generic semantic-unit which contains an-unordered-set of named semantic-units.
Example:
{
"string": "some text",
"number": 123,
"array": [1, 2, 3],
"boolean": true,
"object": {"name": "a name", "phone": 1234567890}
}
[HmnSgm.2017-11-03]
===
A collection of name/value pairs.
In various languages, this is realized as an object, record, struct, dictionary, hash table, keyed list, or associative array.
...
An object is an unordered set of name/value pairs.
An object begins with { (left brace) and ends with } (right brace).
Each name is followed by : (colon) and the name/value pairs are separated by , (comma).
[http://www.json.org/]
Name::
* cpt.JSON'object,
* cpt.JSON-object,
* cpt.JSON-sut.object,
JSON-doc'Syntax-tree
Description::
The-syntax-tree of a-document is a-whole-part-tree with the components of a-document.
The outer most construct of a-JSON-doc is an-object or an-array.
Name::
* cpt.JSON'syntax-tree,
Relation-to-javascript--of-JSON
Description::
Javascript is a-programing-language.
JSON is a-data-representation-language with no data-processing functionality.
Name::
* cpt.JSON'relation-to-javascript,
Relation-to-YAML--of-JSON
Description::
Both JSON and YAML aim to be human readable data interchange formats.
However, JSON and YAML have different priorities.
JSON’s foremost design goal is simplicity and universality.
Thus, JSON is trivial to generate and parse, at the cost of reduced human readability.
It also uses a lowest common denominator information model, ensuring any JSON data can be easily processed by every modern programming environment.
In contrast, YAML’s foremost design goals are human readability and support for serializing arbitrary native data structures.
Thus, YAML allows for extremely readable files, but is more complex to generate and parse.
In addition, YAML ventures beyond the lowest common denominator data types, requiring more complex processing when crossing between different programming environments.
[http://www.yaml.org/spec/1.2/spec.html]
Name::
* cpt.JSON'relation-to-YAML,
Relation-to-XML--of-JSON
Description::
The XML specification does not MATCH the data model for most programming languages which makes it slow and tedious for programmers to parse. Compared to JSON, XML has a low data-to-markup ratio which results in it being more difficult for humans to read and write.
[http://www.json.com/]
Name::
* cpt.JSON'relation-to-XML,
GENERIC-of-JSON
Generic::
* data-representation--computer-language,
JSON.EVOLUTING
Name::
* cpt.JSON.evoluting,
{time.2002}::
A number of people independently discovered that JavaScript's object literals were an ideal format for transmitting object-oriented data across the network.
I made my own discovery in April of 2001 when I was CTO of State Software.
In 2002 I acquired the json.org domain and put up a page describing the format.
With no other effort on my part, JSON has been widely adopted by people who found that it made it a lot easier to produce distributed applications and services.
The original page has been translated into Chinese, French, German, Italian, Japanese, Korean, and Spanish.
JSON has been formalized in RFC 4627.
The MIME Media Type is application/json.
[http://www.json.org/fatfree.html]
