IETF Logo Mail Archive

Re: [Json] Schemas & so on

John Cowan <cowan@mercury.ccil.org> Tue, 03 May 2016 21:45 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 94BAA12D62D for <json@ietfa.amsl.com>; Tue, 3 May 2016 14:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.597
X-Spam-Level:
X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Oj_7WOxti4o for <json@ietfa.amsl.com>; Tue, 3 May 2016 14:45:34 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9145E12D19F for <json@ietf.org>; Tue, 3 May 2016 14:45:33 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1axi8H-0005YC-3m; Tue, 03 May 2016 17:45:29 -0400
Date: Tue, 03 May 2016 17:45:29 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Message-ID: <20160503214528.GF6756@mercury.ccil.org>
References: <CAHBU6itCV9MXmALdKtE9-vjUPG6-6ZqdqzrmZkcEzSUysi3S-w@mail.gmail.com> <AC93811D-A16A-4527-B2EB-C6A9FC6D4F17@mnot.net> <20160503010109.GA17482@mercury.ccil.org> <CAMm+LwjVnh5H4REM9tUJjb7QvL2arxjkhjWybHerxbXUvkcMdA@mail.gmail.com> <20160503172537.GM29513@mercury.ccil.org> <CAMm+LwhMyFawLEQ-e04TA9hw8nsRbG0+1f3hEAhAYc0sgNqtjA@mail.gmail.com> <b60b59d0-ec4e-fba9-fe81-13b0d924ae50@codalogic.com> <D134B11A-34D6-48C3-87EE-5BFAFDCEE757@cisco.com> <CAMm+LwjtwwVErnB3MDW_n4ONt-h5XYKg2SGGrOOqw7XwKr6zmQ@mail.gmail.com> <46FCFC42-3FF1-4CD5-A397-A0553B43AC39@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <46FCFC42-3FF1-4CD5-A397-A0553B43AC39@cisco.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/0HRT0KPgctznan7xHSXOrfa1Qz8>
Cc: Phillip Hallam-Baker <ietf@hallambaker.com>, Tim Bray <tbray@textuality.com>, Peter Cordell <petejson@codalogic.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Schemas & so on
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 03 May 2016 21:45:36 -0000

Joe Hildebrand (jhildebr) scripsit:

> You need to test integers larger than 2^53 with the JSON implementation
> in ECMAscript then.  RFC 7159, section 6 says

Indeed, and browsers are surely not the only JSON implementations to
treat all numbers as IEEE 64-bit binary floats.

If we are going to have a type for integers representable as floats,
then it should be called int54 according to the usual conventions,
with the caveat that -(2**53) cannot be represented, because floats
are not two's-complement.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
On the Semantic Web, it's too hard to prove you're not a dog.
        --Bill de hOra

v2.23.0 | Report a Bug | By Email