Re: [Json] WGLC comment about numeric values

Carsten Bormann <cabo@tzi.org> Fri, 11 October 2013 21:39 UTC

Return-Path: <cabo@tzi.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 2949021E813D for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 14:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.155
X-Spam-Level:
X-Spam-Status: No, score=-106.155 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 zupgjFzLgfVM for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 14:39:28 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 14CE321E8121 for <json@ietf.org>; Fri, 11 Oct 2013 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r9BLdINf017605; Fri, 11 Oct 2013 23:39:18 +0200 (CEST)
Received: from [192.168.217.105] (p54890CAC.dip0.t-ipconnect.de [84.137.12.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 27AD6D05; Fri, 11 Oct 2013 23:39:18 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6itryT-CLEVarK4TEmUJ-grkPAQ8cgx3LZcm0Axe6wyT9w@mail.gmail.com>
Date: Fri, 11 Oct 2013 23:39:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C7C7980-6023-4795-B22D-AA711D08A645@tzi.org>
References: <CAK3OfOhUtrd91SiLrnG=5xoNnvPGfgi4EPLwzU=jV=9oHHS4_g@mail.gmail.com> <CAHBU6isQgyO-qai2w61T-XJoLua+u9QAneXm=doweYSRvrVz-w@mail.gmail.com> <CAHBU6itryT-CLEVarK4TEmUJ-grkPAQ8cgx3LZcm0Axe6wyT9w@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1510)
Cc: Nico Williams <nico@cryptonector.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] WGLC comment about numeric values
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: Fri, 11 Oct 2013 21:39:34 -0000

On Oct 11, 2013, at 23:08, Tim Bray <tbray@textuality.com> wrote:

> A JSON number which is outside those bounds, such as 1E400 or 3.141592653589793238462643383279, may indicate potential interoperability problems since it suggests that the software which created it it expected greater magnitude or precision than is widely available.

Strike "which is outside those bounds".

> A JSON number such as 1E400 or 3.141592653589793238462643383279 may indicate potential interoperability problems since it suggests that the software which created it it expected greater magnitude or precision than is widely available.

(I don't want to restart the 1.1 discussion :-)

Grüße, Carsten