IETF Logo Mail Archive

Re: [Json] Proposal: the minimal edit

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 22 June 2013 23:54 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 6ED5921F9E95 for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 16:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level:
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 tYJCHwvBm+Nb for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 16:54:47 -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 8729321F9E87 for <json@ietf.org>; Sat, 22 Jun 2013 16:54:47 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5MNsi3r094550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 22 Jun 2013 16:54:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130622223906.GX31186@mercury.ccil.org>
Date: Sat, 22 Jun 2013 16:54:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2A5BBC1-BCF7-472A-B0F2-ECDB27B791A6@vpnc.org>
References: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com> <CAHBU6ivhoUM9cfUnc1YfnyDdQnWQ=Mj10cSoYn0qouMQ0F94XA@mail.gmail.com> <CAChr6SyQDjik_BTojXdw3G7_B=W5iZXksuM15VYwGJqr8WHdhw@mail.gmail.com> <CAChr6SwbFfR5UQuU2ceJhDeGAhv5Zy0dKA3szzO_KGfjA7fx5Q@mail.gmail.com> <20130622205936.GV31186@mercury.ccil.org> <CAChr6SwJ5TkYw4TFxWv=9hZPU_jtKuSLDSrN9u+SzBBwo1aspA@mail.gmail.com> <20130622212219.GW31186@mercury.ccil.org> <8DB99A42-7666-443A-9C99-53F8A1AACF17@tzi.org> <20130622223906.GX31186@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1508)
Cc: "json@ietf.org WG" <json@ietf.org>
Subject: Re: [Json] Proposal: the minimal edit
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: Sat, 22 Jun 2013 23:54:48 -0000

On Jun 22, 2013, at 3:39 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Carsten Bormann scripsit:
> 
>> So maybe it is more useful to point out that parsers (and that
>> observation is not limited to JavaScript) might convert JSON's decimal
>> numbers to a (binary or other) form, losing precision and range in
>> the process.
> 
> I had range rather than precision in mind: if you parse "[1, 10, 1E400]",
> you are likely to get either an exception or an array with 1.0, 10.0,
> and Inf in it.  But my point is that ECMAScript implementations MUST
> NOT represent 1E400 other than as Inf, nor 1.9999999999999999999999999
> as other than 2.0.  The same is not true in other languages, notably
> various Lisps.

I would propose that this proposal is in the wrong thread. Robert started this thread as "really minimal changes", and this is clearly an addition, or possibly a note for the likely implementation guidance document.

--Paul Hoffman

v2.46.0 | Report a Bug | By Email | System Status