Re: [Json] Limitations on number size?

Jorge Chamorro <jorge@jorgechamorro.com> Tue, 09 July 2013 23:24 UTC

Return-Path: <jorge@jorgechamorro.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 7B8CD11E80D1 for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 16:24:24 -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 syrRFbM9fVfJ for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 16:24:17 -0700 (PDT)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 6327311E8193 for <json@ietf.org>; Tue, 9 Jul 2013 16:24:09 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id c10so5699303wiw.1 for <json@ietf.org>; Tue, 09 Jul 2013 16:24:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=QDpKJWwgOmX4N0MvEtcTqdLukfme1xYCvMWanIPWfZ8=; b=ePj3ipB6fiiSe1zxKvOUqLGprMkwk7r0FhhElus74x6GeWEuNZrsQYruBcnZlE1FR7 ilruELZ+ZBYZGetTwsbsunpj3NBNsiI+jG7BOd5nFGOERpVKZu0gs8PzGK3mxgH488CO FNqOCpjpF1Zdu7/U/EjcbvmZyh8gh5v45w36A7DxW7jDBqpkTyNo0bOiAMBVCxrEfn/Y uHhiOTefqcRdt9sUSKEm/9wV3cXhf3qTt8gv3gCue29F+Tuw+/iS9jlyRBb7fba4BQJ9 zPflSaE6t6Ny28HdF7pX0esRNNcl53kRLhiBJwcmXps2WaclZ1IoKfauqJzbuzsoj/ft 2Kag==
X-Received: by 10.180.188.97 with SMTP id fz1mr15597814wic.34.1373412246900; Tue, 09 Jul 2013 16:24:06 -0700 (PDT)
Received: from [192.168.10.50] (189.Red-79-155-151.dynamicIP.rima-tde.net. [79.155.151.189]) by mx.google.com with ESMTPSA id em10sm54629643wid.1.2013.07.09.16.24.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 16:24:06 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Jorge Chamorro <jorge@jorgechamorro.com>
In-Reply-To: <51DC92B1.7000908@gmail.com>
Date: Wed, 10 Jul 2013 01:24:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1BB87DE-6377-411A-9359-0714C1CC9549@jorgechamorro.com>
References: <51DC0F95.7010407@gmail.com> <hf8ot8hnpa93pi3t54c4d5qcc3p5tnb3ca@hive.bjoern.hoehrmann.de> <CAK3OfOgTNaLpRthrRcU4Bo+3z1aXUOOn0Ord7RBPN8z6TtiiWw@mail.gmail.com> <51DC7F87.6060503@gmail.com> <D3773B95-FF52-45D7-BE9F-2DEC92AFA67E@jorgechamorro.com> <51DC92B1.7000908@gmail.com>
To: Peter F. Patel-Schneider <pfpschneider@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Gm-Message-State: ALoCoQm+cpinzcje4iFznz44Y7CMOtSNUrqtNimZNXBytXbifK0YAx8J06fSYpcoHfZsiccfM9ht
Cc: Nico Williams <nico@cryptonector.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, json@ietf.org
Subject: Re: [Json] Limitations on number size?
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: Tue, 09 Jul 2013 23:24:38 -0000

On 10/07/2013, at 00:46, Peter F. Patel-Schneider wrote:
> 
> 
> OK, then, what I inferred was that a JSON number represents an IEEE floating point double and I was very surprised to find out that this was not the case.

And given the super-simple rules in the RFC *any* number can be properly represented which is -it seems to me- exactly what Crockford had in mind: that JSON (the data interchange format) does not impose the limits.

That the platforms, languages, libraries, and stringify()er and parse()r implementations may have numeric data type limitations, isn't JSON's (the data interchange format) business.
-- 
( Jorge )();