IETF Logo Mail Archive

Re: [Json] Encoding Schemes

Carsten Bormann <cabo@tzi.org> Tue, 18 June 2013 19:21 UTC

Return-Path: <cabo@tzi.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 D497521F9954 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.196
X-Spam-Level:
X-Spam-Status: No, score=-106.196 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 8ys0OzNicy45 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:21:05 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id EFF0921F8F7B for <json@ietf.org>; Tue, 18 Jun 2013 12:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5IJKvLt013668; Tue, 18 Jun 2013 21:20:57 +0200 (CEST)
Received: from [192.168.217.105] (p54893361.dip0.t-ipconnect.de [84.137.51.97]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C9FD63501; Tue, 18 Jun 2013 21:20:56 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20130618183926.GG12085@mercury.ccil.org>
Date: Tue, 18 Jun 2013 21:20:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9527431-1354-4755-8280-634B4A47BA25@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC57CF2@xmb-rcd-x10.cisco.com> <20130618183926.GG12085@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1508)
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:21:22 -0000

> Any encoding (which means "encoding
> scheme" in a media-type context) can be used to represent JSON.
> Including an EBCDIC variant.

We are confusing JSON with JSON again.

JSON the interchange format, which specifies a sequence of characters, certainly can be encoded in any character encoding scheme that is able to represent the characters that are needed in a specific case.

JSON the media type (application/json) is specifically limited to UTF-8 (and theoretically the two or possibly four other character encoding schemes listed in RFC 4627; the RFC isn't quite consistent here).
There is no way to use another encoding in that media type as there is no charset parameter in the media type.
(This is intentional and certainly is not a candidate for change.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email