IETF Logo Mail Archive

Re: [Json] Encoding Schemes

Norbert Lindenberg <ietf@lindenbergsoftware.com> Tue, 18 June 2013 19:19 UTC

Return-Path: <ietf@lindenbergsoftware.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 7AE7021E80A8 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.931
X-Spam-Level:
X-Spam-Status: No, score=-3.931 tagged_above=-999 required=5 tests=[AWL=-0.332, 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 V4Jk5XE8JNXR for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 12:18:57 -0700 (PDT)
Received: from mirach.lunarpages.com (mirach.lunarpages.com [216.97.235.70]) by ietfa.amsl.com (Postfix) with ESMTP id 8445421E8092 for <json@ietf.org>; Tue, 18 Jun 2013 12:18:57 -0700 (PDT)
Received: from 50-0-136-241.dsl.dynamic.sonic.net ([50.0.136.241]:63876 helo=[192.168.0.5]) by mirach.lunarpages.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <ietf@lindenbergsoftware.com>) id 1Up1Qd-0031jT-EL; Tue, 18 Jun 2013 12:18:55 -0700
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Norbert Lindenberg <ietf@lindenbergsoftware.com>
In-Reply-To: <20130618183926.GG12085@mercury.ccil.org>
Date: Tue, 18 Jun 2013 12:18:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D99FD989-EFA1-4188-85D4-FBB586B39F58@lindenbergsoftware.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC57CF2@xmb-rcd-x10.cisco.com> <20130618183926.GG12085@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1283)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - mirach.lunarpages.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - lindenbergsoftware.com
X-Get-Message-Sender-Via: mirach.lunarpages.com: authenticated_id: ietf@lindenbergsoftware.com
Cc: Norbert Lindenberg <ietf@lindenbergsoftware.com>, "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:19:03 -0000

On Jun 18, 2013, at 11:39 , John Cowan 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.

Do you mean JSON embedded in some other document format, or application/json? How do you align this statement with the current "JSON text SHALL be encoded in Unicode" in section 3 and with the encoding considerations and the lack of a charset parameter in section 6?

Norbert

v2.23.0 | Report a Bug | By Email