IETF Logo Mail Archive

Re: [Json] FYI ECMA, W3C, IETF coordination on JSON

"John Levine" <johnl@taugh.com> Thu, 10 October 2013 01:51 UTC

Return-Path: <johnl@iecc.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 9905921F9C06 for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 18:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.904
X-Spam-Level:
X-Spam-Status: No, score=-100.904 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
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 nUFbJopMmlm6 for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 18:51:19 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id BC7EA21F9C99 for <json@ietf.org>; Wed, 9 Oct 2013 18:51:15 -0700 (PDT)
Received: (qmail 39409 invoked from network); 10 Oct 2013 01:51:14 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Oct 2013 01:51:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52560812.xn--9vv.k1309; i=johnl@user.iecc.com; bh=3g2gkj5dsszsoGwPFd/x5zKfGVth8/9wkl7DnJaUKbs=; b=PoZfnlU8XBJRqdAu5oBCEoMuFnb0lf1l7OzIAW6hh5rcloXuNI3qesPBVMk9rR0HukjlgmARVXwG06ddzCHlxuaVYgERYQIvvnA08tYwPXnfA73Dj+gPbBtOSm5VIDpTWm5wAip5IcUzOo6zy/TBchT9stOLNtjiyWOufJfBVZjaoFB8Dvh7rzidhJ12JNsZKLk+Tza+6eySfhnmGqluIVNImhi/Z3S+AWyB634/CvB6oLMCGcXVE1brTbUloeFW
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52560812.xn--9vv.k1309; olt=johnl@user.iecc.com; bh=3g2gkj5dsszsoGwPFd/x5zKfGVth8/9wkl7DnJaUKbs=; b=QBMVQCnxdugbSeKp4ijHzueXs3ET7drVegYdOMu/aShnQH0k4NTqmQgRK8hVkIsdxluPiwaTluppOwYgL1K7BQy+lwDvsumR89fZnA81TlLs+iOPh+2BNj1HookC34kjmlPcW3Vn+1y9UegJF1oo6Ks3jnyEha559xHu0SmOAZptJlyemHoz/RsKd6nP72NFMrcsp53udaYIjTK4EGJhfFHvxNtQXwPChJk5MQS10GdSnPKiZU2nPH0onFZIl8Jh
Date: Thu, 10 Oct 2013 01:50:52 -0000
Message-ID: <20131010015052.3612.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: json@ietf.org
In-Reply-To: <5254619E.7040407@gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Cc: pfpschneider@gmail.com
Subject: Re: [Json] FYI ECMA, W3C, IETF coordination on JSON
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: Thu, 10 Oct 2013 01:51:23 -0000

>So I would say that JSON is only interoperable if you don't care too much 
>about interoperability, and you don't hit any of the really ugly corner cases.

JSON is very interoperable if your producer stays away from the corner
cases that have provoked blizzards of recent messages.

It is my impression that in practice, many, perhaps most, applications
do so.  Certainly for most of the stuff I do, the numbers are all
integers and the strings are straightforward Unicode.

R's,
John

v2.30.2 | Report a Bug | By Email | System Status