Re: [Json] FYI ECMA, W3C, IETF coordination on JSON
"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Tue, 08 October 2013 19:14 UTC
Return-Path: <pfpschneider@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 4BE4D21F9248 for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 12:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.954
X-Spam-Level:
X-Spam-Status: No, score=-2.954 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599]
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 PjfqOp9HuT0M for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 12:14:42 -0700 (PDT)
Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D8D9C21F92B9 for <json@ietf.org>; Tue, 8 Oct 2013 12:14:40 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id b4so747655qen.20 for <json@ietf.org>; Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=yESz4YdB8ZLCRmB5WXtTP32IZldBoxJm9w+I3ueuEzE=; b=tL8oKTODQhKzE245q8f4vxjHs/qWJZrpEc49K3zRO2mH6j2qXkn2qdycHLUdgGNPRt A5S/ErMt8M5GLyC397QIK0r8ZHmBUSiJUMms6az9e33Of4nnVlNVW4pxXtdUJkqeBqow eECkMh5iJnFzIBJNXfk3hFjhCSVFvjq04MhNA09iI78+karIU6niA7X4lrF5+kXHyKhH pq78j9kDr2qIhVkyTbtN82H0NyLq6PfvTw5d2ur8OFUsnb0rWubZUhwQXlrD+ewBG296 nnWHccnRibx2AI3v4TS470T7gcUE6AhOSoI3q7NIgzETRTm2967ou0Frt249YEoea50E n9gg==
X-Received: by 10.224.171.196 with SMTP id i4mr6153727qaz.38.1381259680436; Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
Received: from [192.168.1.104] (out-on-245.wireless.telus.com. [207.219.69.245]) by mx.google.com with ESMTPSA id u3sm8009416qej.8.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
Message-ID: <5254599C.6090604@gmail.com>
Date: Tue, 08 Oct 2013 12:14:36 -0700
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jorge Chamorro <jorge@jorgechamorro.com>
References: <C68CB012D9182D408CED7B884F441D4D3482260661@nambxv01a.corp.adobe.com> <CAHBU6ivjOHyfMeSNPK3+A_4+VVsyH5Y9XDj77J01OZCjdB6wmA@mail.gmail.com> <525429ED.5000705@gmail.com> <04FC3123-33A4-40DA-AD5D-DA543435DE56@wirfs-brock.com> <20131008164219.GA16081@mercury.ccil.org> <52544E3C.7000907@gmail.com> <3BDEC79B-6B72-4282-955A-D31E156DB29F@jorgechamorro.com>
In-Reply-To: <3BDEC79B-6B72-4282-955A-D31E156DB29F@jorgechamorro.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Allen Wirfs-Brock <allen@wirfs-brock.com>, John Cowan <cowan@mercury.ccil.org>, Larry Masinter <masinter@adobe.com>, Tim Bray <tbray@textuality.com>, JSON WG <json@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>
Subject: Re: [Json] FYI ECMA, W3C, IETF coordination on JSON
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, 08 Oct 2013 19:14:43 -0000
Well, for starters, interchanging non-integers can lead to loss of precision, which can be dangerous. Further, interchanging numbers without some notion of the limits of the receiver is also dangerous. Second, JSON does not only use sequences of digits to represent numbers, and there are many JSON numbers that cannot be represented as a sequence of base-ten digits. Third, there are many numbers that humans interchange that cannot be represented as finite sequences of digits, even if you allow also a decimal point and a negative sign, for example 1/7, pi, and the square root of two. (Perhaps the wording in the introduction is meant to allow infinite sequences of digits, but then using JSON for interchange is a bit difficult.) My understanding is that limiting the representation of numbers to something like the JSON syntax is more of a computer thing than a human thing. peter On 10/08/2013 11:43 AM, Jorge Chamorro wrote: > On 08/10/2013, at 20:26, Peter F. Patel-Schneider wrote: > >> The paragraph on numbers, see below, seems rather dangerous, as well as being incorrect. > Is it? Why? >
- [Json] FYI ECMA, W3C, IETF coordination on JSON Larry Masinter
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tim Bray
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Allen Wirfs-Brock
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Carsten Bormann
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… John Cowan
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Jorge Chamorro Bieling
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tim Bray
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Jorge Chamorro
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Brian Kardell
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Carsten Bormann
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Allen Wirfs-Brock
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Paul Hoffman
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tatu Saloranta
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tatu Saloranta
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Peter F. Patel-Schneider
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Jorge Chamorro
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Brian Kardell
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tim Bray
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Larry Masinter
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Bjoern Hoehrmann
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… Tim Bray
- Re: [Json] FYI ECMA, W3C, IETF coordination on JS… John Levine