Re: [Json] Working Group Last Call on draft-ietf-i-json-02

[Larry Masinter <[e-mail]>]

> > 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.  Any and all comments
> > on the document are sought in order to asses the strength of
> > consensus. Even if you have read and commented on this or earlier
> > versions of the draft, please feel free to comment again.

I think I originally supported the development of I-JSON as
useful named profile of JSON. However, based on recent discussions
and further examination, my opinion now is that the particular
collection of constraints isn't special, and the document should
instead be recast as a "Best Practices for Internet Use of JSON".
To facilitate using the document as a normative reference, each
constraint/best practice could be named "no-dup-names",
"ieee-numbers", "utf8". If you then want to name the union
of all constraints in the document as "i-json" that would be OK.

Most of the document (including the normative language
associated with each constraint) would remain, but the emphasis
on "i-json" as a unique and complete profile wouldn't, and 
would make it easier for referencing applications to choose
those constraints that are meaningful for them.

Larry
--
http://larry.masinter.net