IETF Logo Mail Archive

Re: [Json] I-JSON Tpic #2: Top-Level

Mark Nottingham <mnot@mnot.net> Mon, 28 April 2014 22:10 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF9A11A6FCE for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 15:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulM7uPArhKbd for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 15:10:17 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id D90BA1A7035 for <json@ietf.org>; Mon, 28 Apr 2014 15:10:10 -0700 (PDT)
Received: from [192.168.1.67] (unknown [118.209.107.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F352450A86; Mon, 28 Apr 2014 18:10:06 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAHBU6itycQmqzAuxWyrFZ_v=fHdenm2csyAqtUGGu+vteh6=yQ@mail.gmail.com>
Date: Tue, 29 Apr 2014 08:10:01 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1A5A24F-8336-4BE0-9636-2FEECD75FC14@mnot.net>
References: <535EB119.4000908@cisco.com> <CAHBU6itycQmqzAuxWyrFZ_v=fHdenm2csyAqtUGGu+vteh6=yQ@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/eHXk_2dxK-qjjT3fs7p6P895PYc
Cc: IETF JSON WG <json@ietf.org>, Matt Miller <mamille2@cisco.com>
Subject: Re: [Json] I-JSON Tpic #2: Top-Level
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, 28 Apr 2014 22:10:26 -0000

On 29 Apr 2014, at 6:20 am, Tim Bray <tbray@textuality.com> wrote:

> Allowing top-level JSON to be a primitive - true, null, 42​ - is batshit crazy for anything the IETF might contemplate, and one of I-JSON’s main virtues is ruling that out. 

Is the target audience for I-JSON just the IETF, or anyone who wants a more interoperable profile of JSON?

Regards,

--
Mark Nottingham   http://www.mnot.net/

v2.23.0 | Report a Bug | By Email