IETF Logo Mail Archive

Re: [Json] Wording on encoding; removing the table

"Pete Cordell" <petejson@codalogic.com> Tue, 26 November 2013 10:56 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03061AE1A2 for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 02:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.537
X-Spam-Level: ***
X-Spam-Status: No, score=3.537 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzbfuekXmoZG for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 02:56:45 -0800 (PST)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) by ietfa.amsl.com (Postfix) with ESMTP id A34701AE1A7 for <json@ietf.org>; Tue, 26 Nov 2013 02:56:44 -0800 (PST)
Received: (qmail 7192 invoked from network); 26 Nov 2013 10:56:23 +0000
Received: from host86-167-12-24.range86-167.btcentralplus.com (HELO codalogic) (86.167.12.24) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (RC4-MD5 encrypted, authenticated); 26 Nov 2013 10:56:23 +0000
Message-ID: <01320F468A324337AF1784853F7C7E39@codalogic>
From: Pete Cordell <petejson@codalogic.com>
To: Larry Masinter <masinter@adobe.com>
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de> <BE35B0E6-6C71-47EB-BA29-08A32935D20E@vpnc.org> <7404D1DCC5E84DC3B8F8CD300274962D@codalogic> <7468141ce23a4984a99486c70284ef72@BL2PR02MB307.namprd02.prod.outlook.com>
X-Unsent: 1
Date: Tue, 26 Nov 2013 10:56:58 -0000
MIME-Version: 1.0
x-vipre-scanned: 008BA024005CB6008BA171
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Cc: json@ietf.org
Subject: Re: [Json] Wording on encoding; removing the table
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2013 10:56:47 -0000

----- Original Message From: "Larry Masinter"
> To: "Pete Cordell"
>
> " The transfer encoding
>     used to represent the characters on-the-wire is beyond the scope
>     of this document."
>
> On the contrary, it seems to me that this document is (or should be)
> MAINLY ABOUT normatively establishing how JSON text is encoded
> in an application/json message body "on the wire" -- something
> ECMA 404 doesn't do.

Maybe the MIME type description could say only UTF-8 with or without a BOM, 
but the RFC is now the JSON Data Interchange Format, not just the MIME type. 
I think the JSON Data Interchange Format suggests wider applicability and 
should allow wider choice of UTFs.

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com

v2.23.0 | Report a Bug | By Email