Re: [Json] Last call: JSON charter

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 31 March 2013 15:05 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E5E21F86E8 for <json@ietfa.amsl.com>; Sun, 31 Mar 2013 08:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.326
X-Spam-Level:
X-Spam-Status: No, score=-102.326 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLrurv-19eu5 for <json@ietfa.amsl.com>; Sun, 31 Mar 2013 08:05:37 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8E52721F85D7 for <json@ietf.org>; Sun, 31 Mar 2013 08:05:37 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r2VF5UeX023131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 31 Mar 2013 08:05:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CADnb78hee3zBfCOv-Y-tUYp3ssY02uaG8mRwagEZQ_3W6vHuZA@mail.gmail.com>
Date: Sun, 31 Mar 2013 08:05:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BFD5E35-615C-481E-9E6D-63A889E37DE0@vpnc.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70F8FD11E@xmb-rcd-x10.cisco.com> <B196B7A7-2090-4D53-8920-EB131E2D7E11@vpnc.org> <C68CB012D9182D408CED7B884F441D4D1E885D8AAD@nambxv01a.corp.adobe.com> <BDEACF13-A37F-403F-A31D-8C085B9FBCB3@vpnc.org> <CAChr6SyUmk4yO=aSAw+F2N_MWLv=gtkcUTRGPqWiWFsx=3J89A@mail.gmail.com> <CADnb78iu9jKJPV6ichtQxZgbXqBA42r-sLqZ50DHAkLi-yeiAw@mail.gmail.com> <96C52206-9F7D-40D8-A94A-7BDB462AD115@vpnc.org> <CADnb78hee3zBfCOv-Y-tUYp3ssY02uaG8mRwagEZQ_3W6vHuZA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
X-Mailer: Apple Mail (2.1503)
Cc: json@ietf.org
Subject: Re: [Json] Last call: JSON charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Sun, 31 Mar 2013 15:05:38 -0000

On Mar 31, 2013, at 7:47 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Sun, Mar 31, 2013 at 3:40 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> The parser has *two* arguments, not just one.
> 
> The parser *API* has a second optional argument. The JSON grammar is
> still simply a grammar.

Quite true, but you had said:

On Mar 31, 2013, at 6:47 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> Maybe the RFC should cover resource encapsulation and TC39 should
> remain in charge of parsing the resource. 

Do you want to just use ECMAScript for the JSON *grammar*, and the IETF gets to specify the *parsing rules*? Or something else?

FWIW, the ECMAScript grammar and the RFC 4627 grammar are identical (as far as anyone has said), other than it's harder to figure out the ECMAScript grammar because you have to jump around the ECMAScript document.

--Paul Hoffman