Re: [Json] section 1 paragraph 2 on what JSON can represent
John Cowan <cowan@mercury.ccil.org> Thu, 03 October 2013 04:53 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 4ED1221F9E94 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 21:53:28 -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 yf217sjnpy2S for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 21:53:17 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5AD21F9E6A for <json@ietf.org>; Wed, 2 Oct 2013 21:53:16 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1VRauT-0000Wr-Vh; Thu, 03 Oct 2013 00:53:10 -0400
Date: Thu, 03 Oct 2013 00:53:09 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Message-ID: <20131003045309.GN30371@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> <255B9BB34FB7D647A506DC292726F6E115318CAD1F@WSMSG3153V.srv.dir.telstra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E115318CAD1F@WSMSG3153V.srv.dir.telstra.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: Thu, 03 Oct 2013 04:53:28 -0000
Manger, James H scripsit: > There was a substantial discussion > <http://www.ietf.org/mail-archive/web/json/current/msg00553.html>; > half-a-dozen people strongly supported extending 4627-JSON to be > compatible with ECMA-JSON; about 3 were strongly against; and a handful > seemed to be in the middle. It doesn't seem to fit with the current mission, which is not to extend JSON but to clarify the spec and add warnings about compatibility issues. There are a whole mess of common extensions I'd rather do before I do this. For one thing, JSON numbers aren't self-delimiting, though strings and true/false/null are. -- It was dreary and wearisome. Cold clammy winter still held sway in this forsaken country. The only green was the scum of livid weed on the dark greasy surfaces of the sullen waters. Dead grasses and rotting reeds loomed up in the mists like ragged shadows of long-forgotten summers. --"The Passage of the Marshes" http://www.ccil.org/~cowan
- [Json] Working Group Last Call of draft-ietf-json… Matt Miller (mamille2)
- Re: [Json] Working Group Last Call of draft-ietf-… R S
- Re: [Json] Working Group Last Call of draft-ietf-… Tim Bray
- [Json] Differences between RFC 4627 or the curren… Paul Hoffman
- [Json] "suffer fatal runtime exceptions" Paul Hoffman
- [Json] -0.0 Paul Hoffman
- Re: [Json] -0.0 R S
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] -0.0 Tim Bray
- Re: [Json] "suffer fatal runtime exceptions" R S
- Re: [Json] Differences between RFC 4627 or the cu… Eliot Lear
- Re: [Json] "suffer fatal runtime exceptions" Tim Bray
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Working Group Last Call of draft-ietf-… Mark Nottingham
- Re: [Json] Working Group Last Call of draft-ietf-… Peter Saint-Andre
- Re: [Json] Working Group Last Call of draft-ietf-… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- [Json] Authorship Paul Hoffman
- [Json] Obsoletes RFC 4627 Paul Hoffman
- [Json] Section 1.3, "Changes from RFC 4627" Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Authorship R S
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Authorship Peter Saint-Andre
- Re: [Json] Authorship John Cowan
- Re: [Json] Obsoletes RFC 4627 Martin J. Dürst
- Re: [Json] Obsoletes RFC 4627 Tim Bray
- Re: [Json] Obsoletes RFC 4627 Eliot Lear
- Re: [Json] Authorship Eliot Lear
- Re: [Json] [authorship] (was: Working Group Last … Martin J. Dürst
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] Section 1.3, "Changes from RFC 4627" Martin J. Dürst
- Re: [Json] Obsoletes RFC 4627 Martin J. Dürst
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 Bjoern Hoehrmann
- Re: [Json] Authorship Pete Resnick
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Authorship Bjoern Hoehrmann
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Matt Miller (mamille2)
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 Peter Patel-Schneider
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Paul Hoffman
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Carsten Bormann
- [Json] Change Control (was: Re: Authorship) Martin J. Dürst
- [Json] Indentation (was: Re: Change Control) Martin J. Dürst
- Re: [Json] Indentation (was: Re: Change Control) Carsten Bormann
- Re: [Json] Indentation (was: Re: Change Control) Carsten Bormann
- Re: [Json] Change Control (was: Re: Authorship) Jorge Chamorro
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- [Json] ECMA-262 normative? Carsten Bormann
- Re: [Json] ECMA-262 normative? John Cowan
- Re: [Json] ECMA-262 normative? Paul Hoffman
- Re: [Json] ECMA-262 normative? Eliot Lear
- [Json] Change control for the MIME media type Paul Hoffman
- Re: [Json] ECMA-262 normative? R S
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] ECMA-262 normative? Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Bjoern Hoehrmann
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] section 1 paragraph 2 on what JSON can… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] section 1 paragraph 2 on what JSON can… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] section 1 paragraph 2 on what JSON can… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Martin J. Dürst
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Martin J. Dürst
- Re: [Json] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H