Re: [Json] Comments on proposed charter for JSON

On Friday, March 1, 2013, Joe Hildebrand (jhildebr) wrote:

> (individual)
> I'm fine with the text as it currently sits.
>
> (chair)
> Does the current text give anyone heartburn?  I'll start another thread
> mid-next week to make sure.
>
>

I agree with Bjoern that the charter isn't specific enough wrt the delta
between ES5 and the RFC. Adopting the changes in ES5 would seem to be the
best way get consistency.

However, it sounds like some folks on this list would rather standardize a
narrow RFC4267-derived update. I do not think that work would be valuable.

- Rob

>
> On 3/1/13 10:31 AM, "Paul Hoffman" <paul.hoffman@vpnc.org <javascript:;>>
> wrote:
>
> >I made two more small changes to the proposed charter; comments are
> >welcome.
> >
> >- Changed the community review sentence to say "There are also a number
> >of other JSON-related proposals for Standards Track that would benefit
> >from review from both the IETF and the larger JSON-using communities
> >created by a working group focused on JSON" to indicate that we would
> >benefit from JSON-using developers who are currently not active in the
> >IETF.
> >
> >- Changed the "breaking compatibility" sentence to say "Any changes that
> >break compatibility with existing implementations will need to have very
> >strong justification and broad support, and will have to be documented in
> >the new RFC" to make it clear that the resulting RFC should make any
> >changes clear.
> >
> >--Paul Hoffman
> >_______________________________________________
> >json mailing list
> >json@ietf.org <javascript:;>
> >https://www.ietf.org/mailman/listinfo/json
> >
>
>
>
> --
> Joe Hildebrand
>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/json
>