[Json] Proposed Wording for New WG Charter

[Matt Miller <[e-mail]>]

Greetings again.  We earlier asked a couple of questions to gauge what
the new proposed WG charter ought to contain.  That feedback has been
valuable, but has drilled into implementation specifics before a new
charter was actually agreed on!  We have been chastised by our AD about
this, and for good reason.  We think we already have enough input from
the London meeting and the list over the past few days to make the
following proposal for a new charter:

==========================

Javascript Object Notation (JSON) is a lightweight, text-based,
language-independent data interchange format. It was derived from the
ECMAScript Programming Language Standard, and was later published in RFC
7159.

The WG will work on an restricted profile of JSON designed to maximize
interoperability. The work will start from draft-bray-i-json-01.

The WG will work on a format for a streamable sequence of JSON texts.
The work will start from draft-williams-json-text-sequence-00.

Milestones:

IETF Last Call for restricted profile:  June 2014
IETF Last Call for text sequences:      June 2014

==========================

We note that there is no noticeable consensus around adding work on a
single nomenclature / schema. There appears to be some interest in the
WG coming up with some wording that says "the WG is not going to pick
one yet, and we think that ABNF is certainly the wrong one". If someone
wants to write up a draft with this kind of wording, we don't need to
have it as a charter item: it could just be a message from the WG to the
IESG, and they can ask us more if they want.


--Paul Hoffman and Matt Miller