[Json] Proposed Wording for New WG Charter

Matt Miller <mamille2@cisco.com> Mon, 17 March 2014 22:18 UTC

Return-Path: <mamille2@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 0D9871A063D for <json@ietfa.amsl.com>; Mon, 17 Mar 2014 15:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yaTwFZjMbhj3 for <json@ietfa.amsl.com>; Mon, 17 Mar 2014 15:18:00 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 996B61A0642 for <json@ietf.org>; Mon, 17 Mar 2014 15:18:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1656; q=dns/txt; s=iport; t=1395094673; x=1396304273; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=e0BJqe/L7+RgYxs/pjpj++v4kJPxik24JwvaWsuvNRE=; b=NuoOUBjLaPClyJ4BtEbcnPpSRNIhYTFrRdAAOH7R0p0kBXQ8f/ovsi9Q ZdyF58Nsc0oRlucmb7oiad0L8F/14XIdBOmzChtsYokkvpfPvOPQ8M/0M R/ItH6R7cPBd3hYEHIGjLlqEqELl/9BIb7DIIkBny0IedfpaFA8GR+H7Z s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKNzJ1OtJXG+/2dsb2JhbABagwaBEsM+FnSCSYEYNAJMDQgBAYd1oWeyBReOFIUTBIkaOI50kjCDTIIM
X-IronPort-AV: E=Sophos;i="4.97,673,1389744000"; d="scan'208";a="310929890"
Received: from rcdn-core2-3.cisco.com ([]) by rcdn-iport-5.cisco.com with ESMTP; 17 Mar 2014 22:17:52 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com []) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s2HMHqQp013143 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Mon, 17 Mar 2014 22:17:52 GMT
Received: from che-vpn-cluster-2-161.cisco.com ( by xhc-rcd-x05.cisco.com ( with Microsoft SMTP Server (TLS) id; Mon, 17 Mar 2014 17:17:51 -0500
Message-ID: <53277484.70305@cisco.com>
Date: Mon, 17 Mar 2014 16:17:40 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: IETF JSON WG <json@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: []
Archived-At: http://mailarchive.ietf.org/arch/msg/json/KCN6KBTkUzmp793rNM8KS1tYOTo
Subject: [Json] Proposed Wording for New WG Charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Mar 2014 22:18:02 -0000

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

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.


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