Re: [Json] FYI ECMA, W3C, IETF coordination on JSON

"Peter F. Patel-Schneider" <> Tue, 08 October 2013 19:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4BE4D21F9248 for <>; Tue, 8 Oct 2013 12:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.954
X-Spam-Status: No, score=-2.954 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PjfqOp9HuT0M for <>; Tue, 8 Oct 2013 12:14:42 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c02::22f]) by (Postfix) with ESMTP id D8D9C21F92B9 for <>; Tue, 8 Oct 2013 12:14:40 -0700 (PDT)
Received: by with SMTP id b4so747655qen.20 for <>; Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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 with SMTP id i4mr6153727qaz.38.1381259680436; Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id u3sm8009416qej.8.1969. (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 12:14:40 -0700 (PDT)
Message-ID: <>
Date: Tue, 08 Oct 2013 12:14:36 -0700
From: "Peter F. Patel-Schneider" <>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jorge Chamorro <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Allen Wirfs-Brock <>, John Cowan <>, Larry Masinter <>, Tim Bray <>, JSON WG <>, "" <>
Subject: Re: [Json] FYI ECMA, W3C, IETF coordination on JSON
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.


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?