IETF Logo Mail Archive

Re: [Json] Unpaired surrogates in JSON strings

John Cowan <cowan@mercury.ccil.org> Thu, 06 June 2013 05:11 UTC

Return-Path: <cowan@ccil.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 7610D21F88AC for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 22:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.166
X-Spam-Level:
X-Spam-Status: No, score=-3.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 tR7qE-Ih7r0k for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 22:11:46 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id ECD4921F888F for <json@ietf.org>; Wed, 5 Jun 2013 22:11:45 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UkSUB-0007vv-F9; Thu, 06 Jun 2013 01:11:43 -0400
Date: Thu, 06 Jun 2013 01:11:43 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20130606051142.GD1362@mercury.ccil.org>
References: <20130605162246.GG3680@mercury.ccil.org> <51AF7988.6040009@crockford.com> <20130605184702.GB6999@mercury.ccil.org> <51AF8A09.50806@crockford.com> <AE081E5F-82AB-416F-A690-E8373C0369B0@vpnc.org> <CAHBU6is9NBuicPm=mNSTLRUvXjrAt8BA5KH=A4pSeCNJy=vTNQ@mail.gmail.com> <20130606010945.GA1362@mercury.ccil.org> <CAHBU6isarPqHv0Xteg1c1xKNbZ7N8TE-9qh7N2uwEHU3uQubNA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHBU6isarPqHv0Xteg1c1xKNbZ7N8TE-9qh7N2uwEHU3uQubNA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Douglas Crockford <douglas@crockford.com>, "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: Thu, 06 Jun 2013 05:11:51 -0000

Tim Bray scripsit:

> It seems to me that if unpaired surrogates are to be allowed, it’s not OK
> for the spec to assert that strings are made of Unicode characters, because
> both of these things can’t be correct.  -T

The author has said that "Unicode character" doesn't mean what the
rest of us thinks it means, though no definition I can understand has
been forthcoming.  However, standards (like other kinds of legal codes)
are basically interpreted by their users, not their authors: what the
author says has a peculiar interest, but not a peculiar authority.

-- 
John Cowan      <cowan@ccil.org>       http://www.ccil.org/~cowan
                Charles li reis, nostre emperesdre magnes,
                Set anz totz pleinz ad ested in Espagnes.

v2.23.0 | Report a Bug | By Email