[Json] LC comment on http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-07#section-11
Julian Reschke <julian.reschke@gmx.de> Tue, 12 November 2013 07:19 UTC
Return-Path: <julian.reschke@gmx.de>
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 A70CC21E808F for <json@ietfa.amsl.com>; Mon, 11 Nov 2013 23:19:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.562
X-Spam-Level:
X-Spam-Status: No, score=-103.562 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_00=-2.599, 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 4KH9NFSf8xU0 for <json@ietfa.amsl.com>; Mon, 11 Nov 2013 23:18:59 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 63D6121E8097 for <json@ietf.org>; Mon, 11 Nov 2013 23:18:57 -0800 (PST)
Received: from [192.168.2.117] ([93.217.69.91]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0M4002-1VOsJR3HEo-00raxl for <json@ietf.org>; Tue, 12 Nov 2013 08:18:55 +0100
Message-ID: <5281D65E.1080405@gmx.de>
Date: Tue, 12 Nov 2013 08:18:54 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Rfke3Mg3clF1gVqVPT6Q4NMMuO1s09ibJq8LAt5jdK3K3vGDvCm gyiZyx3guVCaYr1kKj0ZGhNMkQBJSqeHanI9Ir1fZRLw3aja14zIMwbhVyQVyQigFFADndZ 7+eAN0ohch1RCaDuFoEbsaQBo1faE8WwDX6z30KFrSZScM0AAX8EO/HNvHidAgWrwC8GL/Q RvdiEibimwKa8fuAMgbcg==
Subject: [Json] LC comment on http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-07#section-11
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, 12 Nov 2013 07:19:09 -0000
<http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-07#section-11>: > Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32. > JSON may be represented using UTF-8, UTF-16, or UTF-32. When JSON > is written in UTF-8, JSON is 8bit compatible. When JSON is > written in UTF-16 or UTF-32, the binary content-transfer-encoding > must be used. That is a bit misleading, because content-transfer-encoding isn't needed (nor defined) if the transport allows binary anyway (such as HTTP). Related to this: a frequent question on stackoverflow is about the charset parameter on application/json. Maybe it's worth re-stating that it is not only not defined but also really really has no effect. Best regards, Julian
- [Json] LC comment on http://tools.ietf.org/html/d… Julian Reschke
- Re: [Json] LC comment on http://tools.ietf.org/ht… Bjoern Hoehrmann
- Re: [Json] LC comment on http://tools.ietf.org/ht… Julian Reschke
- Re: [Json] LC comment on http://tools.ietf.org/ht… Carsten Bormann
- Re: [Json] LC comment on http://tools.ietf.org/ht… Paul Hoffman
- Re: [Json] LC comment on http://tools.ietf.org/ht… Bjoern Hoehrmann