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

I’m OK with John’s changes, except for the MAY variation in section 9.  The
second half, with all the instances of lower-case “may”, is talking about
implementation behavior.  I had read it as advice for the reader as for
what implementations might do.  So turning those into MAY means that they
normatively describe behavior of conforming implementations.  Are we really
OK with that?  My instinct is that, since this spec has held together
pretty well all these years, why don’t we leave this alone?  -T

On Thu, Oct 10, 2013 at 6:41 PM, John Levine <johnl@taugh.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This draft is ready to publish.  I have a few editorial comments,
> none of which I think would be contentious.
>
> Section 1.2 says:
>
>    Object; thus, for example, "Hello world!", "42", and "true" would all
>    be valid JSON texts in the ECMAScript 5.1 context.
>
> My guess is that the quotes are intended to be part of "Hello world!"
> but not part of 42 or true.  Dunno how to fix that other than perhaps
> to display them, e.g.
>
>    Object; thus, for example, these would all
>    be valid JSON texts in the ECMAScript 5.1 context:
>
>         "Hello world!"
>         42
>         true
>
> Please move section 1.4, the list of changes, to the end.  I think
> that most people will be more interested in the JSON spec rather
> than the minutiae of what's changed.
>
> Section 9 has some upper case MAY and some lower case.  It should
> probably be consistent one way or the other.  I realize this is
> currently unchanged from 4627.
>
> In section 11, the Published specification should be this document,
> not RFC 4627.  Since this is standards track, shouldn't the change
> controller now be the IETF?
>
> R's,
> John
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (FreeBSD)
>
> iEYEARECAAYFAlJXV2oACgkQkEiFRdeC/kVapgCeIERm3QfwTBxFq5AxTmUpPKQT
> 85gAniYwpILyl3iYeppy1KW9VhmxINJR
> =8rQb
> -----END PGP SIGNATURE-----
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>