Re: [Json] Proposal: the minimal edit

[Paul Hoffman <[e-mail]>]

<no hat>

A few people on this thread have said they might support Rob's idea if they knew all the changes, and a few changes were thrown back and forth. I propose the following is a full set of what is needed. Please note the wording at the beginning of the proposed Section 1.3: this is about what ECMAScript actually says about JSON, not what that means to ECMAScript implementations.

Thoughts?

--Paul Hoffman

Add Section 1.2, "Changes from RFC 4627"

   This section lists all changes between this document and the text in
   RFC 4627.

   - Applied errata #607 from RFC 4627 to correctly align the artwork
     for the definition of "object".

   - Applied errata #3607 from RFC 4627 by removing the security
     consideration that begins "A JSON text can be safely passed"
     and the JavaScript code that went with that consideration.

   - Added Section 1.3, "Differences from the JSON Definition in ECMAScript". 

   - Changed the [ECMA] and [UNICODE] references to be non-version-specific.

Add Section 1.3, "Differences from the JSON Definition in ECMAScript"

   The following lists the known major differences between this document and the definition of JSON
   in Section 15.12 of [ECMA].

   - ECMAScript implementations produce and consume primitive JSON values at the root level of JSON
     documents.

   - ECMAScript implementations can generate and consume code points in JSON strings that are not
     Unicode characters.

   - When there are duplicate names within an object, ECMAScript JSON parsers overwrite the value
     corresponding to such names with the value that appears last in the serialization.

In Section 6, remove "A JSON text can be safely passed" and the JavaScript code in the following
paragraph.

In Section 9, change the title in the reference to [ECMA] to be be non-version-specific:

   [ECMA]    European Computer Manufacturers Association, "ECMAScript
             Language Specification",
             <http://www.ecma-international.org/publications/files/
             ecma-st/ECMA-262.pdf>.

In Section 9, change the reference to [UNICODE] to be be non-version-specific:

   [UNICODE]  The Unicode Consortium, "The Unicode Standard",
              <http://www.unicode.org/versions/latest/>.