Re: [Json] Allow any JSON value at the top level

John Cowan <cowan@mercury.ccil.org> Tue, 11 June 2013 19:09 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 15C9F21F8ECB for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 12:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.42
X-Spam-Level:
X-Spam-Status: No, score=-3.42 tagged_above=-999 required=5 tests=[AWL=0.179, 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 i1CjMhHUKUKI for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 12:09:50 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8F621F8607 for <json@ietf.org>; Tue, 11 Jun 2013 12:09:45 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UmTwj-0005tC-Qv; Tue, 11 Jun 2013 15:09:33 -0400
Date: Tue, 11 Jun 2013 15:09:33 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tatu Saloranta <tsaloranta@gmail.com>
Message-ID: <20130611190933.GA16049@mercury.ccil.org>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <A2D3D8F3-1EB3-4CD6-A331-4EDCDB7F9798@tzi.org> <CAGrxA27z-tqgKWcyKNc7ojoUi3Z==hReETrddfYMVxTfVEAhhQ@mail.gmail.com> <DA9A52D2-6956-4E6C-AE96-7F1C05AE3E57@tzi.org> <CAGrxA278XnWEAnJ3WT2YHdYixcvHDPzx7365K6WCWh6ZtLiECA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGrxA278XnWEAnJ3WT2YHdYixcvHDPzx7365K6WCWh6ZtLiECA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Carsten Bormann <cabo@tzi.org>, "Manger, James H" <James.H.Manger@team.telstra.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Allow any JSON value at the top level
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: Tue, 11 Jun 2013 19:09:55 -0000

Tatu Saloranta scripsit:

> My main concern is with UTF-16. My understanding is that for "Big 5"
> languages its use make sense, from efficiency perspective. I do not
> have data on this; in XML space document test sets had non-trivial
> amount of content in various encodings.

See <http://googleblog.blogspot.com/2012/02/unicode-over-60-percent-of-web.html>
which indicates that about 80% of Google-findable web content is in
Unicode, when you count in pure ASCII documents.  I asked Mark Davis,
and he said that UTF-16 was much less than 0.1%.  Of course, in absolute
terms that's a lot of documents.

-- 
Man has no body distinct from his soul,              John Cowan
for that called body is a portion of the soul        cowan@ccil.org
discerned by the five senses,                        http://www.ccil.org/~cowan
the chief inlets of the soul in this age.  --William Blake