IETF Logo Mail Archive

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

John Cowan <cowan@mercury.ccil.org> Wed, 02 October 2013 20:44 UTC

Return-Path: <cowan@ccil.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 D3B7E21F8C0C for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 13:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 S8RV8CLbVR40 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 13:44:00 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id C326021F9D35 for <json@ietf.org>; Wed, 2 Oct 2013 13:43:43 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1VRTGn-0001M3-7W; Wed, 02 Oct 2013 16:43:41 -0400
Date: Wed, 02 Oct 2013 16:43:41 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20131002204341.GF30371@mercury.ccil.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHBU6iv_yta9x_gRbkBwVxZy26QLsdMvtk2YEVBcsUp0KV9vfA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Tony Hansen <tony@att.com>, 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 20:44:10 -0000

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.

-- 
John Cowan    <cowan@ccil.org>     http://www.ccil.org/~cowan
But no living man am I!  You look upon a woman.  Eowyn I am, Eomund's daughter.
You stand between me and my lord and kin.  Begone, if you be not deathless.
For living or dark undead, I will smite you if you touch him.

v2.23.0 | Report a Bug | By Email