IETF Logo Mail Archive

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

Tim Bray <tbray@textuality.com> Tue, 20 May 2014 20:27 UTC

Return-Path: <tbray@textuality.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 D9DA91A0778 for <json@ietfa.amsl.com>; Tue, 20 May 2014 13:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 nPVvsW9ATmtm for <json@ietfa.amsl.com>; Tue, 20 May 2014 13:27:44 -0700 (PDT)
Received: from mail-ve0-f170.google.com (mail-ve0-f170.google.com [209.85.128.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B4171A0090 for <json@ietf.org>; Tue, 20 May 2014 13:27:44 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id db11so1316550veb.15 for <json@ietf.org>; Tue, 20 May 2014 13:27:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=dFDwOU8TnElJLvcnJsAAic5XCwU6tupRUBypkYf5bCU=; b=Hf93scSpQ3KlKgMiOYZyaPW2WhN0b9jeX1jyV7ApiSS3Z6g8NXo7Xo+Ntmb3KV6wjX LHnf8lGMlTi1yfv3+ry68N3uMGBxUOGsWYw7Iao3oEHfR9IylIF3vAux+MZ6Bk5vBiM1 8XikKpWl3JYrLHDG3otHy8UigkOjEDSyEnvCDBzybw3eF72xs8Sa36QhccfZUCZQ6M6Z ZpMy4CaCFPY0z3qMlN6xvHV67bu6LLbLd1BXMe2O90dzMAcmySF0d+YgwDYfihH3lbTB Yal8bSefBUSKwGDuaumlYsxRxdn1eMNiP56fPMM1EOrJzmHpRZuuGPX8gy7kDpOeBfNn xBfA==
X-Gm-Message-State: ALoCoQkFMqVeTktXuzOIrUgB4w9F36J6waCkwEkuECKXGpIG8500mejhVV++A2Vmj+MK3F1hXu3B
X-Received: by 10.220.105.4 with SMTP id r4mr5794139vco.27.1400617662999; Tue, 20 May 2014 13:27:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.98.73 with HTTP; Tue, 20 May 2014 13:27:22 -0700 (PDT)
X-Originating-IP: [107.19.76.28]
In-Reply-To: <537BB89E.2040305@cisco.com>
References: <535EB119.4000908@cisco.com> <CAHBU6itycQmqzAuxWyrFZ_v=fHdenm2csyAqtUGGu+vteh6=yQ@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1154581E82F@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iuqosV91W6CJyow_eaKdCNm_VOairJysuLS8mrWV+HM9g@mail.gmail.com> <ABB2BA00-6A21-4710-A1F5-49D4FB469E8F@vpnc.org> <CAK3OfOig8y5KpYZ86KrMPxrJOYC_hLBew_nmyneHCC2mXX+tag@mail.gmail.com> <537BB89E.2040305@cisco.com>
From: Tim Bray <tbray@textuality.com>
Date: Tue, 20 May 2014 13:27:22 -0700
Message-ID: <CAHBU6ivpG_H=UFd1fAQednN3Q2vvJtw5DD150GnRjq+Ar3bbTA@mail.gmail.com>
To: Matt Miller <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary="089e0122f3324505a604f9dab6d7"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/k-sJ8E0iJ47Ym4wYLUGAQ6GeuZI
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: Tue, 20 May 2014 20:27:46 -0000

For what it’s worth, this particular consensus excludes me.

1. The goal for I-JSOn is to maximize interoperability, and there is
software out there coded to 4627 which will fail when presented with 42 or
true; so interoperability suffers when you do that.
2. For the type of work the IETF is engaged in, Must-Ignore is almost
always a win in protocol designs, and thus we would do well to encourage
the use of JSON that makes this straightforward.


On Tue, May 20, 2014 at 1:18 PM, Matt Miller <mamille2@cisco.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> It has been several days since the last discussion on this topic.  As
> it currently stands, it appears there is no consensus to restrict the
> top-level to only object (or object / array).
>
> Does anyone have more to say with regards to top-level restrictions in
> I-JSON?
>
>
> - --
> - - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - https://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBCgAGBQJTe7ieAAoJEDWi+S0W7cO1/TAH/0l9Um416SDS1RNYyrVyVlip
> Bc/u5zGGaxjASEw1BVt0cckKMcp6syEMRFHmZ8XaUFMFJFFUMn8G6Ob4Lq7Za1K+
> untUCjYkmavzR8frGGJPfmH9EdlUov8Xjm3ByZ+TRswb20cIgrRqw+baI8TbTNR1
> eNZKJ2Y4vW0nFkPvIWdvYwf4Sht8DakM7bYjC4iImrU0t58ESwbFw1uLKGVgrVfU
> y62Jxmp1Yz6WWPIf1Q8MQupDXZNosBS/hLDUoF4FjOUXaNR3CCr8wpQBMm4uBlmZ
> tE6Kwddutq5Kwvvwq7YjpJGUS4uhYNcIVDWwkoBz7ZDOGtctva5UjLjIZ8OnQWg=
> =3Bkb
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)

v2.23.0 | Report a Bug | By Email