Re: [Json] Working Group Last Call of draft-ietf-json-rfc4627bis-04

[R S <[e-mail]>]

Charter:
>
> All differences between RFC 4627 or the current ECMAScript specification
> will be documented in the new RFC.

The ECMAScript specification allows primitives at the root level, specifies
exactly how to interpret numbers, and can handle " bit sequences which
cannot encode Unicode characters" just fine.

Other issues:

I don't think we've seen a JSON implementation "suffer fatal runtime
exceptions" in the presence of the aforementioned bit sequences. Carsten
showed the Python 3 print function throwing an exception, but its standard
JSON module parsed and then stringified them without error.

I don't think there is a rationale for the text on -0.0. Is it for
non-IEE754 implementations?

- Rob



On Thu, Sep 26, 2013 at 10:14 AM, Matt Miller (mamille2) <[e-mail]
> wrote:

> Hello All,
>
> This message begins the Working Group Last Call (WGLC) on "The JSON Data
> Interchange Format" < draft-ietf-json-rfc4627bis-04 >.  WGLC will end in
> two weeks, on October 11.
>
> Please review the document and send comments to the Working Group mailing
> list < json at ietf.org > or the co-chairs <json-chairs at tools.ietf.org> before the end of the WGLC.  Note that suggested changes which include
> proposed text will be more strongly considered than those without.
>
>
> Thanks,
>
> - Paul Hoffman and Matt Miller
>
>
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json
>
>