What is the difference between JSON and Object Lit

Question

Can someone tell me what is the main difference between a JavaScript object defined by using "Object Literal Notation" and JSON object?

According to a JavaScript book it says this is an object defined by using Object Notation:

var anObject = {
    property1 : true,
    showMessage : function (msg) { alert(msg) }
};

Why isn't it a JSON object in this case? Just because it is not defined by using quotation marks?

Answer 1

There is really no such thing as a "JSON Object".

The JSON spec is a syntax for encoding data as a string. What people call a "JSON Object" ( in javascript ) is really just an ordinary javascript object that has (probably) been de-serialized from a valid JSON string, and can be easily re-serialized as a valid JSON string. This generally means that it contains only data ( and not functions ). It also means that there are no dates, because JSON does not have a date type ( probably the most painful thing about JSON ;)

Furthermore, (side-rant...) when people talk about a "JSON Object", they almost always mean data that has the "curly-braces" at the top-level. This corresponds nicely to a javascript object. However, the JSON spec does not require that there be a single "curly-braces" object at the top-level of a JSON string. It is perfectly valid JSON to have a list at the top-level, or even to have just a single value. So, while every "JSON Object" corresponds to valid JSON, not all valid JSON strings correspond to what we would call a "JSON Object"! ( because the string could represent a list or an atomic value )

Answer 2

Lets clarify first what JSON actually is. JSON is a textual, language-indepedent data-exchange format, much like XML, CSV or YAML.

Data can be stored in many ways, but if it should be stored in a text file and be readable by a computer, it needs to follow some structure. JSON is one of the many formats that define such a structure.

Such formats are typically language-independent, meaning they can be processed by Java, Python, JavaScript, PHP, you name it.

In contrast, JavaScript is a programming language. Of course JavaScript also provides a way to define/describe data, but the syntax is very specific to JavaScript.

As a counter example, Python has the concept of tuples, their syntax is (x, y). JavaScript doesn't have something like this.

---

Lets look at the syntactical differences between JSON and JavaScript object literals.

JSON has the following syntactical constraints:

• Object keys must be strings (i.e. a character sequence enclosed in double quotes ").
• The values can be either:
  • a string
  • a number
  • an (JSON) object
  • an array
  • true
  • false
  • null
• Duplicate keys ({"foo":"bar","foo":"baz"}) produce undefined, implementation-specific results; the JSON specification specifically does not define their semantics

In JavaScript, object literals can have

• String literals, number literals or identifier names as keys (since ES6, keys can now also be computed, which introduces yet another syntax).
• The values can be any valid JavaScript expression, including function definitions and undefined.
• Duplicate keys produce defined, specified results (in loose mode, the latter definition replaces the former; in strict mode, it's an error).

---

Knowing that, just be looking at the syntax, your example is not JSON because of two reasons:

1. Your keys are not strings (literals). They are identifier names.
2. You cannot assign a function as a value to a "JSON object" (because JSON doesn't define any syntax for functions).

But most importantly, to repeat my explanation from the beginning: You are in a JavaScript context. You define a JavaScript object. If any, a "JSON object" can only be contained in a string:

 var obj = {foo: 42}; // creates a JavaScript object (this is *not* JSON)
 var json = '{"foo": 452}'; // creates a string containing JSON

That is, if you're writing JavaScript source code, and not dealing with a string, you're not dealing with JSON. Maybe you received the data as JSON (e.g., via ajax or reading from a file), but once you or a library you're using has parsed it, it's not JSON anymore.

---

Only because object literals and JSON look similar, it does not mean that you can name them interchangeably. See also There's no such thing as a "JSON Object".

Answer 3

According to JSON in JavaScript,

JSON is a subset of the object literal notation of JavaScript.

In other words, valid JSON is also valid JavaScript object literal notation but not necessarily the other way around.

In addition to reading the documentation, as @Filix King suggested, I also suggest playing around with the JSONLint online JSON validator. That's how I learned that the keys of JSON objects must be strings.

Answer 4

As far as I understand the main difference is the flexibility.

JSON is a kind of wrapper on "JavaScript Object Notation" which forces users to obey more strict rules for defining the objects. And it does this by limiting the possible object declaration ways provided by JavaScript Object Notation feature.

As a result we have a simpler and more standardized objects which suits better on data-exchange between platforms.

So basically, the newObject in my example above is an object defined by using JavaScript Objeect Notation; but it is not a 'valid' JSON object because it does not follow the rules that JSON standards require.

This link is also quite helpful: http://msdn.microsoft.com/en-us/library/bb299886.aspx

Answer 5

JSON has a much more limited syntax including:

• Key values must be quoted
• Strings must be quoted with " and not '
• You have a more limited range of values (e.g. no functions allowed)

Answer 6

查看更多

0人赞 添加讨论(0) 举报