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

Nico Williams <nico@cryptonector.com> Mon, 28 April 2014 19:58 UTC

Return-Path: <nico@cryptonector.com>
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 DB9481A6F9E for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 12:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334] autolearn=no
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 TmSIHlhttDR2 for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 12:58:51 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1FFDF1A03FC for <json@ietf.org>; Mon, 28 Apr 2014 12:58:51 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id 7FFB450808F for <json@ietf.org>; Mon, 28 Apr 2014 12:58:50 -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=b6AQJgNfpe4ThE9nZWpr7cE3I+0=; b=shrYMcUlA54 X9mZYP61Z6Y3LI+Oh2ec5cT2+OSOTODXg7LU2bA8aIgcPHDC/QWOwarvD8ftvjny L0AHvFQ4lBRPDhC//KUH2Artt9zMwxfbqxM0wVmy625a1Pz3BOud/FLuGY8kHyo+ DWFUq//cIILwU+su+ZX56Le/T+/Z1Ddw=
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTPSA id 34A58508084 for <json@ietf.org>; Mon, 28 Apr 2014 12:58:50 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id q59so1386091wes.9 for <json@ietf.org>; Mon, 28 Apr 2014 12:58:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.188.41 with SMTP id fx9mr3782303wjc.56.1398715128908; Mon, 28 Apr 2014 12:58:48 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Mon, 28 Apr 2014 12:58:48 -0700 (PDT)
In-Reply-To: <535EB119.4000908@cisco.com>
References: <535EB119.4000908@cisco.com>
Date: Mon, 28 Apr 2014 14:58:48 -0500
Message-ID: <CAK3OfOh7oUjC40D4_bSs0nY2aOaqBe2S4d3HWa0TMPRxFs0Z4w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Matt Miller <mamille2@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/RbDWV73NC2YsTMsqsM99LOEY5hQ
Cc: IETF JSON WG <json@ietf.org>
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 19:58:52 -0000

On Mon, Apr 28, 2014 at 2:50 PM, Matt Miller <mamille2@cisco.com> wrote:
> "draft-i-json-01 says the top level is an object (but doesn’t say
> MUST, eek).  I have heard arguments for allowing arrays too."
>
> If you are in favor -- or not -- of restricting the top-level I-JSON
> text to only be object (or array / object), please respond to this
> thread with your reasoning.

I am opposed.  The rationale given is that fields can be added to
objects.  Sure, but schemas can be changed in other ways, especially
if there's out-of-band signalling as to schema.

Nico
--