IETF Logo Mail Archive

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

John Cowan <cowan@mercury.ccil.org> Tue, 11 June 2013 02:11 UTC

Return-Path: <cowan@ccil.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 460B421F9954 for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 19:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.415
X-Spam-Level:
X-Spam-Status: No, score=-3.415 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 47o+GOTUI7KW for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 19:11:16 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id CABDF21F9953 for <json@ietf.org>; Mon, 10 Jun 2013 19:11:16 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UmE3A-0001tl-M1; Mon, 10 Jun 2013 22:11:08 -0400
Date: Mon, 10 Jun 2013 22:11:08 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20130611021108.GE1057@mercury.ccil.org>
References: <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> <CAK3OfOjLQv9eGA6TB62JuFRZLMQsDsdKMHJkWmb7zZgLYdY9Pg@mail.gmail.com> <29C7B970-C97D-47E2-9C91-272B2C18E3D1@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <29C7B970-C97D-47E2-9C91-272B2C18E3D1@vpnc.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Nico Williams <nico@cryptonector.com>, 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 02:11:21 -0000

Paul Hoffman scripsit:

> Why add any recommendation for parsers for that case? The current doc
> already has:
> 
>    A JSON parser MAY accept non-JSON forms or extensions.

That combined with the lack of a data model, or any requirements on
parsers to report anything, means that `cat` counts as a JSON parser
currently: it will not reject any legal JSON, it accepts non-JSON
forms (to wit, anything), and it reports its input exactly.

Is it in scope to fix that?  That would mean some kind of data model
and reporting requirements in section 4.

-- 
Babies are born as a result of the              John Cowan
mating between men and women, and most          http://www.ccil.org/~cowan
men and women enjoy mating.                     cowan@ccil.org
    --Isaac Asimov in Earth: Our Crowded Spaceship

v2.23.0 | Report a Bug | By Email