Re: [Json] Numeric ECMAScript limitations

R S <sayrer@gmail.com> Sat, 22 June 2013 20:50 UTC

Return-Path: <sayrer@gmail.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 5EC8021F9E9D for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level:
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, NO_RELAYS=-0.001]
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 HUiLdXNEoQFy for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:50:35 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6C28A21F9D52 for <json@ietf.org>; Sat, 22 Jun 2013 13:50:35 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id hq4so1553056wib.6 for <json@ietf.org>; Sat, 22 Jun 2013 13:50:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zoRH0mNV9P7IkEidC14DVbe1LI/ZGqA2mrQiJmoYg94=; b=B1YJE9chSGZpPjjtFmNp/dfTATaeRyU3akTYS6BbLG2d+WPhgsijeUayyqseZIr9ny MZ5w2G7GgJLDWpbkbKgfpIOa8Z07Ck/deyegXBMOGUHh2/dDPsPt3X5lmpinbFtxJijx xSjoZW7QKo/IjYDaGuxwXlAjIKBc3hMn5EG+UtrRhryrl/3nPahStfSfCALEF9fTqqVi i8x4b8krxkFLFQ44hBn2vrr9jQXaQlaH5eg61Qr1w0Xstdjmg+oxYt9gZHG4ev+lIq6O gL45oHZ56Zuo1vCo8V8e0m11Bqat2hrbhARDfUqJdjHbNSF1PTQnWcE5il4+xAFhJLt9 EbkQ==
MIME-Version: 1.0
X-Received: by 10.194.86.106 with SMTP id o10mr12512205wjz.93.1371934234610; Sat, 22 Jun 2013 13:50:34 -0700 (PDT)
Received: by 10.194.44.138 with HTTP; Sat, 22 Jun 2013 13:50:34 -0700 (PDT)
In-Reply-To: <20130622204200.GT31186@mercury.ccil.org>
References: <05A7D2E5-C119-4900-B52B-54B0F1206300@lindenbergsoftware.com> <CA+mHimPF5Q4us+pUKnT79h6SbS63Qh7bAOkp4tSpaCvDWZf-2g@mail.gmail.com> <FB5408B8-68ED-4ACB-96DE-C3AD69240B10@lindenbergsoftware.com> <CAK3OfOhKc4PP7NHoTDce8KK-ZB01DEw=hCQLAZc+EyUjsD0tRw@mail.gmail.com> <20130622204200.GT31186@mercury.ccil.org>
Date: Sat, 22 Jun 2013 13:50:34 -0700
Message-ID: <CAChr6SzPv1_ZsJshR-LUP2uUDpWCYFmteczCPx+VdxwUCewNpw@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: multipart/alternative; boundary="089e0102e0dcb591c804dfc454b3"
Cc: "json@ietf.org" <json@ietf.org>, Nico Williams <nico@cryptonector.com>, Stephen Dolan <stephen.dolan@cl.cam.ac.uk>, Norbert Lindenberg <ietf@lindenbergsoftware.com>
Subject: Re: [Json] Numeric ECMAScript limitations
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 20:50:36 -0000

On Sat, Jun 22, 2013 at 1:42 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Right, that's another thing for the ECMAScript Stupid Tricks section:
> ECMAscript JSON limits the range of numbers to the finite values of
> 64-bit IEEE floats, whereas RFC JSON has no fixed limitation, though it
> licenses parsers to specify one.
>

I think ECMAScript JSON.parse implementations conform to RFC 4627 in this
case, so a note is not strictly necessary. I wouldn't oppose including it,
though. Similar interoperability issues could occur between Python and
Java, for example.

- Rob