It's late again tonight !! Hey, continue with the summary of JOSN !!!! Is it necessary to write such a simple statement ??? I think it would be better to go over ten times in my eyes "!! Correct the error !! Learn together !!!! If you don't talk about it, go to the question tonight: <2> JSON format and Syntax: Javascript can easily create and access JSON objects. The syntax is as follows: 1 var jsonObject = 2 {3 propertyName (attribute name): value (value), // attribute syntax in the object (attribute name and attribute value appear in pairs) 4 functionName (function name): fucntion (){.......;} // function syntax in the object (the function name and function content appear in pairs) 5}; for the above syntax, Here analysis: 1), jsonObject: JSON object name 2), propertyName: attribute name 3), functionName: function name 4), a pair of braces, JSON, a set of multiple "name/value", is represented by a set of "name/value" or "key/value" pairs. It can also be understood as an array, the attribute name or function name can be any string (but must be meaningful and identifiable) or even a null string.. Commas (,) are used to separate the "name/value" pairs of each pair. In the simplest form, they can be expressed in the following JSON: 1 {"fistName": "Aju"}, which is very basic for an instance, in addition, it actually occupies more space than the equivalent plain text name/value pair (firstName = Aju). However, when multiple "name/value" pairs are grouped together, the value of JSON is also reflected. Below is a record containing multiple "name/value" pairs: 1 {"firstName": "zhang", "lastName ": & quot; Aju & quot;, & quot; email & quot;: & quot; 1022560838@qq.com & quot;}; syntactically, this does not have much advantage over the "name/value" pair, but in this case, JSON is easier to use and more readable. For example, it explicitly indicates that the above three values are all parts of the same record; curly braces make these values correlated. To represent a group of values, JOSN not only improves readability, but also reduces complexity. For example, if you want to represent a list of individual names, in XML, many start and end tags are required. If you use a typical name/value pair, you must create a proprietary data format. If JSON is used, you only need to group multiple records with curly braces: 1 {2 "people": [3 {"firstName": "Zhao", "lastName ": "Liang", "email": "1111@qq.com"}, 4 {"firstName": "zhang", "lastName": "Liang", "email": "2222@qq.com "}, 5 {"firstName": "Li", "lastName": "Si", "email": "3333@qq.com"} 6]} This should be hard to understand, in this instance, there is only one variable named "people". The value contains three arrays, each of which is a person's record, including name, last name, and email, the example above demonstrates how to combine a record into a value by using a quote. Of course, you can use the same syntax to represent multiple values (each value contains multiple records ): copy code copy code 1 {2 "programmers": [3 {"firstName": "zhang", "lsatName": "San"}, 4 {"firstName ": "Li", "lsatName": "Si"} 5], 6 "authors": [7 {"firstName": "wang", "lsatName": "wu "}, 8 {"firstName": "Lu", "lsatName": "liu"} 9], 10 "musicians": [11 {"firstName": "qi ", "lsatName": "qiang"}, 12 {"firstName": "huang", "lsatName ": "San"} 13] 14} copy the code to copy the code. It is worth noting that it can represent multiple values. Each value contains multiple values, in different arrays ("programmenrs", "authors", and "musicians"), the actual name/value pairs in the record can be different, JSON is completely dynamic (you can write anything as long as it complies with its syntax specifications). When processing JSON format data, there is no need to comply with predefined constraints. Therefore, in the same data structure, you can change the data representation mode;