Is there any practical reason to use quoted strings for JSON keys?

by

The real reason about why JSON keys should be in quotes, relies in the semantics of Identifiers of ECMAScript 3.

Reserved words cannot be used as property names in Object Literals without quotes, for example:

({function: 0}) // SyntaxError
({if: 0}) // SyntaxError
({true: 0}) // SyntaxError
// etc...

While if you use quotes the property names are valid:

({"function": 0}) // Ok
({"if": 0}) // Ok
({"true": 0}) // Ok

The own Crockford explains it in this talk, they wanted to keep the JSON standard simple, and they wouldn’t like to have all those semantic restrictions on it:

….

That was when we discovered the
unquoted name problem. It turns out
ECMA Script 3 has a whack reserved
word policy. Reserved words must be
quoted in the key position, which is
really a nuisance. When I got around
to formulizing this into a standard, I
didn’t want to have to put all of the
reserved words in the standard,
because it would look really stupid.

At the time, I was trying to convince
people: yeah, you can write
applications in JavaScript, it’s
actually going to work and it’s a good
language. I didn’t want to say, then,
at the same time: and look at this
really stupid thing they did! So I
decided, instead, let’s just quote the
keys.
That way, we don’t have to tell
anybody about how whack it is.

That’s why, to this day, keys are quoted in
JSON.

…

The ECMAScript 5th Edition Standard fixes this, now in an ES5 implementation, even reserved words can be used without quotes, in both, Object literals and member access (obj.function Ok in ES5).

Just for the record, this standard is being implemented these days by software vendors, you can see what browsers include this feature on this compatibility table (see Reserved words as property names)

More Related Contents:

  1. Javascript comparison behaving differently in different browsers [closed]
  2. Browser-native JSON support (window.JSON)
  3. Is JSON Hijacking still an issue in modern browsers?
  4. XML parser for JavaScript [closed]
  5. Unable to access JSON property with “-” dash
  6. JavaScript, browsers, window close – send an AJAX request or run a script on window closing
  7. How to check if a string is a valid JSON string?
  8. How to parse JSON using Node.js? [closed]
  9. What is the minimum valid JSON?
  10. Calling a JSON API with Node.js
  11. How do you put an image file in a json object?
  12. How to convert CSV to JSON in Node.js
  13. Refused to execute script, strict MIME type checking is enabled?
  14. Check if a key exists inside a JSON object
  15. When to prefer JSON over XML?
  16. How can I use JSON data to populate the options of a select box?
  17. jQuery JSON looping through nested objects
  18. Does extension messaging like chrome.runtime.sendMessage internally use JSON.stringify?
  19. Is there any possibility to have JSON.stringify preserve functions?
  20. How to use a JSON file in javascript
  21. How to check if css value is supported by the browser?
  22. Javascript: How to generate formatted easy-to-read JSON straight from an object? [duplicate]
  23. Why the open quote and bracket for eval(‘(‘ + jsonString+ ‘)’) when parsing json string
  24. how to read json result in jquery?
  25. Uncaught TypeError: data.push is not a function
  26. how to process fetch response from an ‘opaque’ type?
  27. Is there a limit on the size of a string in JSON with Node.js?
  28. Annoying javascript timezone adjustment issue
  29. Breaking JavaScript execution when cookie is set
  30. How to focus an input field on Android browser through javascript or jquery

Leave a Comment