Re: [Json] JSON for Internet messages

John Cowan <cowan@mercury.ccil.org> Wed, 03 July 2013 19:12 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 DDF6B21F9C8B for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.572
X-Spam-Level:
X-Spam-Status: No, score=-3.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 A7rnjypyoTmp for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:12:16 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id C461621F9C5F for <json@ietf.org>; Wed, 3 Jul 2013 12:12:13 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UuSTM-00008l-Of; Wed, 03 Jul 2013 15:12:12 -0400
Date: Wed, 3 Jul 2013 15:12:12 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20130703191212.GI32044@mercury.ccil.org>
References: <CAHBU6it55C5vCNLBki1LvjpWd4fANY8LdC4fzxj3a2G_+q=qSA@mail.gmail.com> <20130703171547.GH32044@mercury.ccil.org> <CAHBU6ist_Zq=-jY3C2C4m7EiJTv6JgHOCxGntvpg-jgKQ1D04g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHBU6ist_Zq=-jY3C2C4m7EiJTv6JgHOCxGntvpg-jgKQ1D04g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] JSON for Internet messages
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: Wed, 03 Jul 2013 19:12:21 -0000

Tim Bray scripsit:

> > > - All numbers MUST be of precision < 2**53 
> > Better: All numbers MUST be representable as IEEE 754:2008 binary
> > 64-bit floats.
> 
> I think my expression of the constraint is more readable, but I agree
> that yours is isomorphic.

Well, no.  1E400 requires only one bit of precision, but it's not
representable as a double, because doubles only go up to 1E308 or so.

> > The trouble with all this is that They Break Data.
> 
> I care -Inf about this.

That reminds me how *annoying* it is that there's no way to represent
Inf, -Inf, or NaN.  Too late now, I suppose.

> In my application domain, we cook these up in memory, we send them,
> we unpack them at the other end.   I agree, that if if we impose a
> new set of rules in a new RFC, previously-existing JSON might not pass
> muster as “Internet JSON” or whatever we choose to call it.

How about "Ephemeral Mini-JSON"?  Can't be too big, not expected to last.

-- 
With techies, I've generally found              John Cowan
If your arguments lose the first round          http://www.ccil.org/~cowan
    Make it rhyme, make it scan                 cowan@ccil.org
    Then you generally can
Make the same stupid point seem profound!           --Jonathan Robie