IETF Logo Mail Archive

Re: [Json] JSON irritants

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 04 August 2016 19:56 UTC

Return-Path: <jhildebr@cisco.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 B102012DAF3 for <json@ietfa.amsl.com>; Thu, 4 Aug 2016 12:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 PgImWsu1LTyP for <json@ietfa.amsl.com>; Thu, 4 Aug 2016 12:56:41 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33D5E12D7C8 for <json@ietf.org>; Thu, 4 Aug 2016 12:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=490; q=dns/txt; s=iport; t=1470340601; x=1471550201; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GOL5TBu1KWhWwHVzzmkeEn9HvX34mpxIbanT0WYU774=; b=dmCYjoGTrseXe6F1CM5EMygRUYVCFTq8qcRdpilCTIXLgBDPDIzH8a3L kcuzVzba29nrenHC0l0YyOG2eZkBVeg//seVzFBwRcupsoHp4Em9/rHBP YFI22ccvYyawmaCb6GmVIdSHSVJ/lOyuUOTblfmhusUH5q/XVNVhQ1DQ5 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwBQC/naNX/5RdJa1dg0WBUge3D4IPgX2GHQIcgSw5EwEBAQEBAQFdJ4RfAQUjEUUQAgEIGgImAgICMBUQAgQOBYgxrmmQCwEBAQEBAQEBAQEBAQEBAQEBAQEBARyBAYUpgXiCVYdBK4IvAQSZNAGPAYFVAY1qkCcBIAEzg3puhix/AQEB
X-IronPort-AV: E=Sophos;i="5.28,471,1464652800"; d="scan'208";a="136389714"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Aug 2016 19:56:24 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u74JuO9m010957 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Aug 2016 19:56:24 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 4 Aug 2016 15:56:23 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1210.000; Thu, 4 Aug 2016 15:56:23 -0400
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: John Cowan <cowan@mercury.ccil.org>
Thread-Topic: [Json] JSON irritants
Thread-Index: AQHR7UZrh82lIZMJ7E6HoY6TwevAEaA3BXwAgAB8BACAAXPmgIAAftUA//+kPQA=
Date: Thu, 04 Aug 2016 19:56:23 +0000
Message-ID: <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>
In-Reply-To: <20160804192446.GA5679@mercury.ccil.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.203.25]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1E0C3EA842F3E74B93D666087340AF1D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/zRYbnJrSTmykrvNk5JAHQpFNCLg>
Cc: Tim Bray <tbray@textuality.com>, "Manger, James" <James.H.Manger@team.telstra.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: Thu, 04 Aug 2016 19:56:43 -0000

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

v2.23.0 | Report a Bug | By Email