Re: [Json] -0.0

John Cowan <cowan@mercury.ccil.org> Mon, 30 September 2013 00:58 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 679DC21F9D3E for <json@ietfa.amsl.com>; Sun, 29 Sep 2013 17:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.31
X-Spam-Level:
X-Spam-Status: No, score=-3.31 tagged_above=-999 required=5 tests=[AWL=0.289, 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 X41F8XFemHGG for <json@ietfa.amsl.com>; Sun, 29 Sep 2013 17:58:54 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 4377221F9D3B for <json@ietf.org>; Sun, 29 Sep 2013 17:58:54 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1VQRp7-0000gL-6r; Sun, 29 Sep 2013 20:58:53 -0400
Date: Sun, 29 Sep 2013 20:58:53 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20130930005853.GM27126@mercury.ccil.org>
References: <20130927214137.GC24460@mercury.ccil.org> <BF7E36B9C495A6468E8EC573603ED9411EF1E1E5@xmb-aln-x11.cisco.com> <CAChr6SxfAv+yjEzsn2R=S79MviRN+bYak=8Nnnkw9hfs3p1zxw@mail.gmail.com> <CAChr6SxYSzXGf5hrVNvmdmpHU2R+cKSH+37NhTc--6iDpfXG3g@mail.gmail.com> <9D959999-63A2-46EF-8C14-C48F586D9DA4@tzi.org> <CAChr6Sz4Hg--YrWnxXOxJJmbx=AmjDoEZXxs7HeTV58w5VSRDg@mail.gmail.com> <25C6CA6F-76F0-42DE-8845-850B8B69F1A6@tzi.org> <CAHBU6is6w6WpsYOeOP=yMREAhz90+J4OPC6uVB+nXca2aJMmpg@mail.gmail.com> <20130930002831.GJ27126@mercury.ccil.org> <590DB34F-489F-4FBD-8937-7CA14382F366@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <590DB34F-489F-4FBD-8937-7CA14382F366@vpnc.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] -0.0
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: Mon, 30 Sep 2013 00:58:59 -0000

Paul Hoffman scripsit:

> The additions that we are making about interoperability are about
> things that a significant number of JSON users might expect.

I don't actually think so.  They are edge cases (unpaired surrogates,
too-large or too-precise numbers, duplicate names), but edge cases wind
up being important to somebody.  Negative zero is just another edge case.

> The likely-forthcoming "implementation advice" document can take care
> of telling implementers of JSON encoders and parsers what they should
> consider.

Oh, I agree.  But all the things above, including negative zero, are about
what users can and cannot expect to survive when transmitted by JSON.

> "Don't boil the ocean." (Lots of people, recently.)

In the Middle East, that's where the drinking water comes from.  What's
more, if you have some high-temperature superconductor and need to kill
off a field of sunflowers, boiling the ocean may be just the thing.

> Number geeks^wspecialsts might expect certain things about -0, but the
> vast majority of normal JSON users won't. I think it is fine to remove
> the paragraph and assume that a more in-depth discussion will happen
> in the companion document.

You could make the same argument about Unicode geeks and unpaired
surrogates.  Are you doing so?  If not, why not?

-- 
                Si hoc legere scis, nimium eruditionis habes.