IETF Logo Mail Archive

Re: [Json] JSON irritants

Rob Sayre <sayrer@gmail.com> Fri, 05 August 2016 03:00 UTC

Return-Path: <sayrer@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 7C0F512D8AC for <json@ietfa.amsl.com>; Thu, 4 Aug 2016 20:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rGtgVUSR64gu for <json@ietfa.amsl.com>; Thu, 4 Aug 2016 20:00:46 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4B3912D897 for <json@ietf.org>; Thu, 4 Aug 2016 20:00:46 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id q83so289338874iod.1 for <json@ietf.org>; Thu, 04 Aug 2016 20:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LYA9wTYT7shT17ILJtrIV83UtOjBiiqO1W0K3DZR47E=; b=Ge+TnGo+oINQiqzy47+Y8EroamE4j4i6ZVlZ13Ax485FCY2w6smTz8n3XGx4vUZmJY 8ONFPtZ1hkryFS3puot9cdCJWGqlfG7bG7eVg2VfAVT1zhSnkajpd79gAvijUC+d62nM WtOXNRQo4SYhE8zPmu+FS/zBblvyXSCtbI/0oLhl8hzpEGBn+eh9naFMQx8kYAdM9pk0 eMFzdP5YNeE0WdZju9VkI3TcH4qX1ZYYa/SjdbG9mIJe79gdGJoLQLM3SX8JAOG13QVh SJwhal+eKtx9UzSZSFCSgqCdV7A4bGln+ytI5Z9VYkcfaXhI0kC+rVOJHX5pz+Wnv6O6 N8ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LYA9wTYT7shT17ILJtrIV83UtOjBiiqO1W0K3DZR47E=; b=Aof6mS0YXTwxvWb7YKQgoz1u3naCG3dX7sX/21Is0thw1hokABLbvaNdiPd1yZ/EIw iAxW8K7BUHoogEaH6DnBPe8r8UL4T8S4VdtJoM2i5yiI8/rGal9UGRXDYHYamd4QZDt7 U/8TN/FTQwJI+0H+z958TePRMqWjPTGB6PVtbNUrMaFNrh2FPUpgnXM41wduHc3pzrZH vZbOgj1yN37aaqO0PSYhJl1UlZY06g551gqT8Puz6f+hk/3kaGyJzcrZsMQeUGOREwaL 4XJyWNvPWHAMNMOGKwq/FxAKDd8Otxbryk2cfSo8O3gJVbFJKlFVas/k+ralobICEY4s BPEA==
X-Gm-Message-State: AEkoouuARYXDl5T2rmjtDHM1xBg6tZSrcjb+slNT8NRVNxo0iiEghZUsaQwbrwmQ9hO9NqTzOvH/sAEXmHa++w==
X-Received: by 10.107.14.74 with SMTP id 71mr76754100ioo.93.1470366045960; Thu, 04 Aug 2016 20:00:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.85.213 with HTTP; Thu, 4 Aug 2016 20:00:45 -0700 (PDT)
In-Reply-To: <90D00DC6-614E-465C-A57C-599F58FF71B4@cisco.com>
References: <CAHBU6iv+S5=bxh62G+ybcgUWzQLUngVSti8X1ptENn0fA=i3ng@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E13BFDE57E14@WSMSG3153V.srv.dir.telstra.com> <20160803133945.GC30359@mercury.ccil.org> <2C110290-8873-4A8C-B62D-DCE39D1FB745@cisco.com> <20160804192446.GA5679@mercury.ccil.org> <90D00DC6-614E-465C-A57C-599F58FF71B4@cisco.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 04 Aug 2016 20:00:45 -0700
Message-ID: <CAChr6Szr4sNvc8MROXKUN-MydAq22uP27DBqynuY2b_V2sxFog@mail.gmail.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: multipart/alternative; boundary="001a113fe1d4dc020e05394a455f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/waGGwB5Oscy3ypnV6Z0Anlp5_Gw>
Cc: Tim Bray <tbray@textuality.com>, "Manger, James" <James.H.Manger@team.telstra.com>, John Cowan <cowan@mercury.ccil.org>, "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: Fri, 05 Aug 2016 03:00:48 -0000

There are plenty of wire formats that don't have these problems. None of
them are called "JSON", and this one shouldn't be either (doesn't sound
like it will be).

YAML, TOML, Avro, Thrift, CBOR, Protocol Buffers, and many others all
address some of these problems. Some aren't as self-describing as JSON is.

- Rob


On Thu, Aug 4, 2016 at 12:56 PM, Joe Hildebrand (jhildebr) <
jhildebr@cisco.com> wrote:

> On 8/4/16, 1:24 PM, "John Cowan" <cowan@ccil.org on behalf of
> cowan@mercury.ccil.org> wrote:
>
> >Sure, and that way of thinking leads to YAML, which has had some success.
> >But it hasn't turfed out JSON, and it's unlikely that anything else will
> >turf out YAML.
>
> Agree.  Let a dozen flowers bloom.  Media types are cheap.
>
> --
> Joe Hildebrand
>
>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email