On Sun, Jun 9, 2013 at 7:19 PM, Paul Hoffman <[email protected]> wrote:
> >At two TC39 meetings, members of TC39 expressed deep concern about the > prospect of incompatible changes to JSON by the IETF. > > Those concerns have not been expressed directly to the IETF's JSON Working > Group. I say this as one of the two co-chairs of the JSON WG. If TC39 wants > to express "deep concern", they certainly know where to do so. Them doing > so sooner rather than later would be helpful all around. > > I would note that some of the possibly-incompatible changes to RFC 4627 > that are being discussed relate to places where the RFC is > self-contradictory or blatantly unclear. In such cases, leaving the RFC > alone might just as easily lead to incompatible implementations as > clarifications would. That is going to have be determined by the IETF's > consensus process. > > No one can force anyone here to follow the official WG discussion for the > successor to RFC 4627, of course. However, given that some people on this > list are JSON experts, if you don't want to participate in the evolution of > the RFC, I would be interested in hearing (possibly off-list) why that is. > Part of the job of the chairs is to make sure experts feel welcome in the > IETF process. > Paul, Here are the notes from the first TC39 meeting that this topic was discussed https://github.com/rwldrn/tc39-notes/blob/master/es6/2013-03/mar-12.md#49-json-ietf-changes Rick
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
