Re: [Json] Minimal edit proposal, second round

-1
Too minimal to provide any value (and certainly not enough value to overcome the pain of introducing a second RFC number for referring to JSON).

P.S. Surely we don't need to explicitly mention that an update fixes editorial errata (#607).

--
James Manger

> -----Original Message-----
> From: json-bounces@ietf.org [mailto:json-bounces@ietf.org] On Behalf Of
> Paul Hoffman
> Sent: Thursday, 27 June 2013 1:47 AM
...
> 
> Begin with http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-02.
> 
> Change Section 1.2, "Changes from RFC 4627", to read:
> 
>  This section lists all changes between this document and the text in
> RFC 4627.
> 
>  - Applied erratum #607 from RFC 4627 to correctly align the artwork
> for the definition of
>    "object".
> 
>  - Applied erratum #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".
> 
>  - Updated the [ECMA] reference, and changed the [UNICODE] references
> to be
>    non-version-specific.
> 
> Add Section 1.3, "Differences Between This Document 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 all code points
> in JSON strings, while there
>    is disagreement about whether this document prohibits some specific
> code points in JSON strings.
> 
>  - 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 to the
> latest version with JSON:
> 
>  [ECMA]    Ecma International, "ECMAScript Language Specification, 5.1
> Edition / June 2011",
>            <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/>.
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json