Re: [Json] REMINDER - WGLC Ends 2013-10-11

I have one unanswered technical question from earlier, when I wrote:
> What I would suggest is that at the very least we understand the
> differences, so that we know what we're getting into. 
I think John Cowan answered this question in part in his mail of October
8th (Re: [Json] FYI ECMA, W3C, IETF coordination on JSON) by stating
that  ECMA 404 is pretty much RFC 4627.  Therefore, so long as we have
in the draft an accurate and up-to-date list of changes, then at least
we know if we are introducing interoperability problems.  Section 1.3
sort of does this, but should be cleaned up to be succinct and limited
to TECHNICAL changes ONLY.  Other changes should be moved to the back.

The key differences, therefore, are as follows:

  * No specific version of unicode.
  * Specific language on duplicate members
  * Discussion of character model
  * IEEE numbers and number  ABNF

Are those all the technical differences?

Eliot

On 10/9/13 11:21 PM, Matt Miller (mamille2) wrote:
> A reminder that the current Working Group Last Call for draft-ietf-json-rfc4627bis officially ends on Friday, October 11.  Please provide any feedback as soon as you can, even if it's "the draft is good enough".
>
>
> Thanks!
>
> - Paul Hoffman and Matt Miller
>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json