Re: [Json] Encoding Schemes

John Cowan <cowan@mercury.ccil.org> Tue, 18 June 2013 19:56 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 E23B621F998F for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level:
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 pONr+ukxUTso for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:56:01 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 87C7621F9982 for <json@ietf.org>; Tue, 18 Jun 2013 12:56:01 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Up20W-0007XW-5T; Tue, 18 Jun 2013 15:56:00 -0400
Date: Tue, 18 Jun 2013 15:56:00 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Norbert Lindenberg <ietf@lindenbergsoftware.com>
Message-ID: <20130618195600.GH12085@mercury.ccil.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC57CF2@xmb-rcd-x10.cisco.com> <20130618183926.GG12085@mercury.ccil.org> <D99FD989-EFA1-4188-85D4-FBB586B39F58@lindenbergsoftware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D99FD989-EFA1-4188-85D4-FBB586B39F58@lindenbergsoftware.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Encoding Schemes
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, 18 Jun 2013 19:56:06 -0000

Norbert Lindenberg scripsit:

> Do you mean JSON embedded in some other document format, or
> application/json?

Either.

> How do you align this statement with the current "JSON
> text SHALL be encoded in Unicode" in section 3

Like Alice, I don't believe there's an atom of meaning in it.  "Unicode"
is not the name of an encoding.

> and with the encoding
> considerations and the lack of a charset parameter in section 6?

If there's no charset parameter, there isn't one.  Otherwise, section 6
only explains what Content-Transfer-Encoding to use in various cases,
without saying that no other cases are supported.

-- 
John Cowan <cowan@ccil.org>             http://www.ccil.org/~cowan
Pour moi, les villes du Silmarillion ont plus de réalité que Babylone.
		--Christopher Tolkien, as interviewed by Le Monde