Re: [Json] JSON irritants

John Cowan <cowan@mercury.ccil.org> Wed, 03 August 2016 13:47 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 A69DA12DD95 for <json@ietfa.amsl.com>; Wed, 3 Aug 2016 06:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.888
X-Spam-Level:
X-Spam-Status: No, score=-3.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, 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 S-a2-XLv4FF4 for <json@ietfa.amsl.com>; Wed, 3 Aug 2016 06:47:13 -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 3E81C12DDAC for <json@ietf.org>; Wed, 3 Aug 2016 06:39:52 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1bUwOg-0001h1-7t; Wed, 03 Aug 2016 09:39:46 -0400
Date: Wed, 3 Aug 2016 09:39:46 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Message-ID: <20160803133945.GC30359@mercury.ccil.org>
References: <CAHBU6iv+S5=bxh62G+ybcgUWzQLUngVSti8X1ptENn0fA=i3ng@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E13BFDE57E14@WSMSG3153V.srv.dir.telstra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E13BFDE57E14@WSMSG3153V.srv.dir.telstra.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/VJU7ax4TlBh9J9VBEZLxog-l1yg>
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] JSON irritants
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: Wed, 03 Aug 2016 13:47:16 -0000

Manger, James scripsit:

> Yuck for i800 and f49.399. I’d prefer the presence of a decimal
> point “.” or exponent symbol “e” to imply a float; and their
> absence to imply an integer.

+1.  That is how my JSON parser works in any case.

> Optional commas sounds okay. I wouldn’t like to forbid them as 
> [11, 234, 5, 6] is nicer than [11 234 5 6].

I think an important point is being allowed to include a redundant
final comma.

> Encouraging yyyy-mm-ddThh:mm:ss[.sss…]Z for instants of time is
> great. I’m less sure that distinguishing it from a string is so
> crucial.

Mmm, I think it's good to have it as a separate type.  I don't see any
need for the @ prefix, though.  A date-time literal doesn't look like
anything else.

But as someone who tried with XML 1.1 and XML 1.0 5e, I suspect that
any such effort as this is doomed to obscurity.  The improvements
aren't massive enough to be worth the conversion effort and loss of
interoperability.

FtanML, now ...
<http://www.balisage.net/Proceedings/vol10/print/Kay01/BalisageVol10-Kay01.html>

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
Mos Eisley spaceport.  You will never see a more wretched hive of scum
and villainy --unless you watch the Jerry Springer Show.
        --georgettesworld.com