IETF Logo Mail Archive

Re: [Json] section 1 paragraph 2 on what JSON can represent

Tony Hansen <tony@att.com> Wed, 02 October 2013 20:49 UTC

Return-Path: <tony@att.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 E126C21F9C05 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 13:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level:
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 3Tz-kuhGhcwJ for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 13:49:38 -0700 (PDT)
Received: from flpi406.enaf.ffdc.sbc.com (egssmtp03.att.com [144.160.128.152]) by ietfa.amsl.com (Postfix) with ESMTP id CD20E21F90CF for <json@ietf.org>; Wed, 2 Oct 2013 13:49:25 -0700 (PDT)
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp03.att.com (8.14.4/8.14.4) with ESMTP id r92KnLTN013597 for <json@ietf.org>; Wed, 2 Oct 2013 13:49:25 -0700
Received: from [135.91.110.247] (ds135-91-110-247.dhcps.ugn.att.com[135.91.110.247]) by maillennium.att.com (mailgw1) with ESMTP id <20131002204920gw1009k12be> (Authid: tony); Wed, 2 Oct 2013 20:49:20 +0000
X-Originating-IP: [135.91.110.247]
Message-ID: <524C86D0.5050506@att.com>
Date: Wed, 02 Oct 2013 16:49:20 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: JSON WG <json@ietf.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <CAChr6SyznBktmOLpT-EiZ5Nm_0jZ16M0tOo4aZ_jhSDb=HHDqg@mail.gmail.com> <23C96FBA-3419-4C97-A075-462F7443013A@vpnc.org> <CAHBU6is2WzCNCwa0PYMM1Hr3Lij0GxWkVtVUan9=JPbvv0YCZg@mail.gmail.com> <CAChr6Sw72kxm8qJiDu=XMnARCttQPc5GNRQaXz4Xw9y+6-3=Mg@mail.gmail.com> <421F79DF-0B88-4E24-8666-189228E6E189@vpnc.org> <524C73B7.1060104@att.com> <524C76B0.9040900@att.com> <CAHBU6iv_yta9x_gRbkBwVxZy26QLsdMvtk2YEVBcsUp0KV9vfA@mail.gmail.com> <20131002204341.GF30371@mercury.ccil.org>
In-Reply-To: <20131002204341.GF30371@mercury.ccil.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [Json] section 1 paragraph 2 on what JSON can represent
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: Wed, 02 Oct 2013 20:49:51 -0000

On 10/2/2013 4:43 PM, John Cowan wrote:
> Tim Bray scripsit:
>
>> The “JSON can represent...” text is perfectly accurate.  It may not be able
>> to represent them in a standalone top-level way, but the parts of a JSON
>> text do in fact represent those things.
> +1.  If it read "JSON texts can represent" it would indeed be inaccurate,
> but it doesn't.

Am I the only one who read that statement to be referring to the
top-level value and *not* specifically to internal values?

At the least, I think the current statement is ambiguous. It *can* be
read either way.

    Tony Hansen

v2.23.0 | Report a Bug | By Email