IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 02 October 2013 21:35 UTC

Return-Path: <paul.hoffman@vpnc.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 4759021F9EB6 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 14:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 FXjaMP6f0UXB for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 14:35:12 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0322F21F9E7C for <json@ietf.org>; Wed, 2 Oct 2013 14:35:00 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r92LYvI8034596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Oct 2013 14:34:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <524C86D0.5050506@att.com>
Date: Wed, 02 Oct 2013 14:34:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA667B1B-F1E4-48F4-B529-D6531ED1A8A4@vpnc.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> <524C86D0.5050506@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.1510)
Cc: JSON WG <json@ietf.org>
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 21:35:19 -0000

<no hat>

On Oct 2, 2013, at 1:49 PM, Tony Hansen <tony@att.com> wrote:

> 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?

Maybe. When you hit the definition of JSON-text, it sounds like you said "these disagree" instead of "these are describing different things".

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

The question of what is a JSON-text seems important, but maybe should not be made to the detriment of the clarity of the first sentence.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email