Re: [Json] Encoding Schemes

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 18 June 2013 18:54 UTC

Return-Path: <jhildebr@cisco.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 CA4FE11E80FA for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 11:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.686
X-Spam-Level:
X-Spam-Status: No, score=-10.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 p-7buehh+lZs for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 11:54:38 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 4C56D11E80F9 for <json@ietf.org>; Tue, 18 Jun 2013 11:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1346; q=dns/txt; s=iport; t=1371581677; x=1372791277; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=mxbp9kJoVWL6N6VOqdfxnydUcu7czfXQA9P8XEjQSUY=; b=mcSSC259rTqkuHqQjvpW3qgWvdRq/7VagNyllr5R0p4j0l0cKmXmb/5p geuBD3yxS7dCiO3Tfn3PtB2hn4l+xp0hMfBx5c69shBovJbQzEsCrfQOD uSyNd7JfTG/tF5sDkI/vKUaIPA0SlE3/JvYXSlHtMvWP/Y7zolkwOwN4h Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FALSrwFGtJXHA/2dsb2JhbABZgwl6vw+BAxZ0giUBBDo/EgEIIhRCJQIEDgUIiAa7A48KMQeDAGEDqQSDD4Io
X-IronPort-AV: E=Sophos;i="4.87,890,1363132800"; d="scan'208";a="224422072"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 18 Jun 2013 18:54:37 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5IIsane020122 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Jun 2013 18:54:36 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Tue, 18 Jun 2013 13:54:36 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: John Cowan <cowan@mercury.ccil.org>
Thread-Topic: [Json] Encoding Schemes
Thread-Index: AQHObFF5M05aOqj6pkC704hlIeI8tpk8IX8A//+fpgA=
Date: Tue, 18 Jun 2013 18:54:35 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70FC582BF@xmb-rcd-x10.cisco.com>
In-Reply-To: <20130618183926.GG12085@mercury.ccil.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [64.101.72.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FAA63D3B4780284EB2620E83D398B437@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "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 18:54:43 -0000

On 6/18/13 12:39 PM, "John Cowan" <cowan@mercury.ccil.org> wrote:

>Joe Hildebrand (jhildebr) scripsit:
>
>> "When serialized to an octet stream, JSON text SHALL be encoded in one
>>of
>> the following Unicode encoding schemes: UTF-8,  UTF-16BE, UTF-16LE,
>> UTF-32BE, and UTF-32LE.  The default and RECOMMENDED encoding is UTF-8.
>
>Oh no, that SHALL will not fly.  Any encoding (which means "encoding
>scheme" in a media-type context) can be used to represent JSON.
>Including an EBCDIC variant.

I assume you're talking about UTF-EBCDIC from tr16?  I don't see how you
could auto-determine the encoding for that.  How about this:

"""
Without an external mechanism that specifies encoding, when serialized to
an octet stream, JSON text SHALL be encoded in one of the following
Unicode encoding schemes: UTF-8,  UTF-16BE, UTF-16LE, UTF-32BE, and
UTF-32LE.  The default and RECOMMENDED encoding is UTF-8.

Note: the MIME type registered in section 6 does not specify a mechanism
to specify the encoding scheme, so when used in a MIME context, one of the
above encoding schemes MUST be used.


Other Unicode encoding schemes MAY be used, but such octet streams cannot
have their encoding scheme automatically detected and SHOULD NOT be
assumed to interoperate with existing software.
"""


-- 
Joe Hildebrand