IETF Logo Mail Archive

Re: [Json] Unpaired surrogates in JSON strings

Bjoern Hoehrmann <derhoermi@gmx.net> Fri, 07 June 2013 10:42 UTC

Return-Path: <derhoermi@gmx.net>
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 E2BEA21F8F2F for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 03:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 2nbhXEQJdL2t for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 03:42:22 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id B568221F8E93 for <json@ietf.org>; Fri, 7 Jun 2013 03:42:21 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Lh9yb-1TzhPw1lzz-00oWSz for <json@ietf.org>; Fri, 07 Jun 2013 12:42:19 +0200
Received: (qmail invoked by alias); 07 Jun 2013 10:42:18 -0000
Received: from p5B2339AC.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [91.35.57.172] by mail.gmx.net (mp010) with SMTP; 07 Jun 2013 12:42:18 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19xk51s8VNxRxq+SakGNTB8L4sB+oiNuYfP6bewdh tBSsaYJuPAG7q0
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Date: Fri, 07 Jun 2013 12:42:17 +0200
Message-ID: <9ld3r8pc0tufif18dohb2fmi0ijna1vs4n@hive.bjoern.hoehrmann.de>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC2E7E1@xmb-rcd-x10.cisco.com> <51B06F38.8050707@crockford.com> <CAHBU6iuFBuW-RfgBLQF5q4BnUOzs088QXW3uOQG1OjBFjZttkw@mail.gmail.com> <51B1B4E7.8090101@it.aoyama.ac.jp>
In-Reply-To: <51B1B4E7.8090101@it.aoyama.ac.jp>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Unpaired surrogates in JSON strings
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: Fri, 07 Jun 2013 10:42:27 -0000

* Martin J. Dürst wrote:
>I fully agree with what Tim says above: We know (and to a certain extent 
>have to accept) that there are implementations that, surely way more by 
>accident than by any kind of intent, send unpaired surrogates. But we 
>should try to do whatever we can in the spec to make it perfectly clear 
>that there are no good reasons whatsoever to actually do that.

Actually there are many good reasons for having unpaired surrogates in
JSON documents. A simple example would be a test suite for string APIs.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

v2.23.0 | Report a Bug | By Email