IETF Logo Mail Archive

Re: [Json] Allow any JSON value at the top level

Nico Williams <nico@cryptonector.com> Tue, 11 June 2013 00:30 UTC

Return-Path: <nico@cryptonector.com>
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 CC73811E80AE for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 17:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.962
X-Spam-Level:
X-Spam-Status: No, score=-1.962 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 hwI08vTssnA4 for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 17:30:17 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id CC5DB11E80A5 for <json@ietf.org>; Mon, 10 Jun 2013 17:30:17 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTP id 500D52AC005 for <json@ietf.org>; Mon, 10 Jun 2013 17:30:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=50D6QRiX3BTML5wlKqz1skPOTxM=; b=SyMxBn3vJ+x 6k8qdR3HZ/mgT8Nmrymbyr5z9QomSM8X3NmYj/3kgBL0jDQ9D0hKkW+U3M+HzJxF BsVxqVC5NYiSKLR5DUqoGXLC/tAumBRRgIcY8zwq8+KKd8emeqUuRcLBah+U3bSF mNL7oFKji7gElUuimzstJ0nhzKYEhybs=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTPSA id 026302AC023 for <json@ietf.org>; Mon, 10 Jun 2013 17:30:16 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so5350409wes.17 for <json@ietf.org>; Mon, 10 Jun 2013 17:30:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ZMprh2FyNDY5kAq9Dmm/ZtfDZTjr7ZGc3CBGFYfHy3I=; b=EqVC4mwPUIvYw/hCmw/chrWwKid6hq3/S3IIRLAXTOu/xMM+LkVNq4KpOiS/jqFULO abd4yW5R8mibz9DWLF23Pf4brtwCxqEmWw3DNSJOtOm9bF1I2nXhqWK39ZgeixC2Orau QJxvajhtX1aSxdQW3ncMcdyOw0+lhS02YkjHdyMUeWh4uYucs5U5/QVC1SNFsMLCA1KM P7tbOEDWoiP4epZtS8SaG0WLHd3nQfPNmE2osRNgGGGV9Ii0gJLVl/N4JorXOiWtpO9h 6mCLtsTSplIapi5w5f0V7/ZdV4qBGPayA2Ib9j52OmxMm5XA4idwWMfKb5KLN+4fRNM1 Wecw==
MIME-Version: 1.0
X-Received: by 10.194.158.69 with SMTP id ws5mr5812402wjb.84.1370910615647; Mon, 10 Jun 2013 17:30:15 -0700 (PDT)
Received: by 10.216.63.136 with HTTP; Mon, 10 Jun 2013 17:30:15 -0700 (PDT)
In-Reply-To: <B14769F1-5C71-4F1D-8E20-513271876620@vpnc.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC33B5B@xmb-rcd-x10.cisco.com> <51b23e6d.6196420a.0b15.4245SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SwrveU=fesF8VidDYWzeYMu2c1+=38+__BqHArxTiW5mg@mail.gmail.com> <51b4dbbe.64da440a.1fc2.6dd2SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6Sx_obmG+=sY100ySBLmevN0VJ_0Z9TjYGxcXKOx+UtnJA@mail.gmail.com> <51b4ec44.ea05420a.7c73.ffffa487SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxiZ2Yz6SiozQZpuYoGKSzWnUux6PukyWDkcvKsVyyRbQ@mail.gmail.com> <51b507b1.c686e00a.3a7e.ffffa0adSMTPIN_ADDED_BROKEN@mx.google.com> <CAO1wJ5R2H27qh-DWG5B8CzutkTFWxn-h+Qi1jiet23axxmvLyA@mail.gmail.com> <20130610201746.GC1057@mercury.ccil.org> <CAO1wJ5Q9mhspheU3h4NRx9x5LOz9yOgJBXhwPWBOVw-w71ncTQ@mail.gmail.com> <3CE20E15-8F9E-4727-BBE7-FBB06F7CAC24@jorgechamorro.com> <CAGrxA24T8m9oHmuVE8n+YG6ATr3sTTByet7Te8VyAmypD11p6w@mail.gmail.com> <B14769F1-5C71-4F1D-8E20-513271876620@vpnc.org>
Date: Mon, 10 Jun 2013 19:30:15 -0500
Message-ID: <CAK3OfOjLQv9eGA6TB62JuFRZLMQsDsdKMHJkWmb7zZgLYdY9Pg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: json@ietf.org
Subject: Re: [Json] Allow any JSON value at the top level
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 00:30:22 -0000

On Mon, Jun 10, 2013 at 6:56 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> <no hat>
>
> Although I earlier supported the idea of any JSON value at the top level, a bunch of recent posts show that this is probably a significant revision to the RFC because it would take a lot of extra requirements as well. I now support leaving the requirement in the -bis document as it is now.
>
> If we want to add a new MIME type for "any JSON item", that is clearly a significant addition to the RFC. It can wait until the WG recharters.

I see no reason [yet... the way these threads have been going...] why
we couldn't recommend that parsers be able to parse any top-level
value, with the only interesting note being that end-of-message
termination of numeric top-level values must not be accidentally
confused with premature EOF.  Also, we could just allow any
non-numeric top-level value.  With a similar recommendation for
encoders.

Nico
--

v2.23.0 | Report a Bug | By Email