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

R S <sayrer@gmail.com> Tue, 11 June 2013 04:27 UTC

Return-Path: <sayrer@gmail.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 5E13D21F998B for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 21:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 f9EA6PFXMgaf for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 21:27:43 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 42C5B21F9974 for <json@ietf.org>; Mon, 10 Jun 2013 21:27:42 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id w56so5528425wes.11 for <json@ietf.org>; Mon, 10 Jun 2013 21:27:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GRb4vzVgLuEFnKn4LPllTOiM6Xes5s8lD1uhWJ94SRI=; b=Y7QXjUTJlEHDX8AAgiUEPHpIH53KPZU+qKltnTAImfZ3N3PM8BlUIG+gJHcINJ99YT /8h/5KbP09zwYwYkP50J9rNv/PWLORJdRJtguiAV5YP7oAJNcZqNxztBHuQ4MvT682q4 bx/DgXmNaJNt5NxN9LRm9BOxH/ixfPPVECd4Qx1HGyxA+fF7h7+XGXMRRhzSSnUUWW7P dQyW094Q+Oudylf5bftMiePPj/Yu8d4g6f9EYCIVpRMaTxaHmL8AEhSBHxQm2dxd8rrB 4WzM9lQvYONH+CzAWhuEcEEZ8HoQjXwxkGN08BtaTJ/qX7ehPu/Z4t30Odh1hSJGrxIe 8d8w==
MIME-Version: 1.0
X-Received: by 10.180.185.84 with SMTP id fa20mr46131wic.49.1370924862353; Mon, 10 Jun 2013 21:27:42 -0700 (PDT)
Received: by 10.194.83.35 with HTTP; Mon, 10 Jun 2013 21:27:42 -0700 (PDT)
In-Reply-To: <B4ABD0ED-1F4E-4B2E-A0B1-B93A1C28B21A@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> <CAChr6SzXUNTA+bMtFAwWh+Z2APoiSuAt7DQzx+RK57+vznN1-w@mail.gmail.com> <CAChr6SyYUJEHBP2qq=FpyMAQ=+3sAV8mcvBwoSYBfUdh9_Xa3Q@mail.gmail.com> <B4ABD0ED-1F4E-4B2E-A0B1-B93A1C28B21A@vpnc.org>
Date: Mon, 10 Jun 2013 21:27:42 -0700
Message-ID: <CAChr6SzmdGQnX8qNqPQYoZZj+oHTR93bGYGCkXF1MxS6Cxcbgg@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a11c2404c6f372804ded9516b"
Cc: "<json@ietf.org>" <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 04:27:44 -0000

On Mon, Jun 10, 2013 at 7:57 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

>
> ...I certainly hope the WG find that defining "browser" and "most" and
> "popular" is out of scope.


That is not a very charitable interpretation of what I wrote. For my part,
I certainly hope the WG doesn't stick its head in the sand and say "only
objects and arrays are JSON, because we say so".



> > Many endpoints only accept specific root elements. For example,
> json-patch only accepts arrays. In other words, no one will notice if your
> JSON parser only accepts objects and arrays.
> >
> > What is the benefit of preserving RFC 4627 requirements? I don't
> understand the rationale accompanying your opinion. The charter mandates
> that the WG document top-level primitive parsing, no matter what.
>
> Fully agree on the last part. But "document" does not mean "change the
> requirements". We can say "the requirement is X" and "X differs from 4627
> and/or ECMAScript", at least in my reading of the charter.


I agree with that. But ECMAScript is the better JSON parsing document, and
RFC 4627 is a now-obsolete Informational RFC.

- Rob