IETF Logo Mail Archive

Re: [Json] Unpaired surrogates in JSON strings

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 05 June 2013 23:56 UTC

Return-Path: <paul.hoffman@vpnc.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 A307911E80D1 for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 16:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 g5-vGxgnP5ae for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 16:56:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E81F111E80AE for <json@ietf.org>; Wed, 5 Jun 2013 16:56:52 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r55NtwQh099847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Jun 2013 16:55:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51AF8A09.50806@crockford.com>
Date: Wed, 05 Jun 2013 16:55:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE081E5F-82AB-416F-A690-E8373C0369B0@vpnc.org>
References: <20130605162246.GG3680@mercury.ccil.org> <51AF7988.6040009@crockford.com> <20130605184702.GB6999@mercury.ccil.org> <51AF8A09.50806@crockford.com>
To: Douglas Crockford <douglas@crockford.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Wed, 05 Jun 2013 23:56:56 -0000

On Jun 5, 2013, at 11:57 AM, Douglas Crockford <douglas@crockford.com> wrote:

> On 6/5/2013 11:47 AM, John Cowan wrote:
>> Douglas Crockford scripsit:
>> 
>>> Such a requirement will be breaking. Breaking changes are out of scope.
>> How is it a breaking change to limit what documents are allowed to be
>> *generated*?
>> 
> Because JSON is currently being used in applications that deliver those codepoints.

Can you say why an application would do that, given the JSON specification?

--Paul Hoffman

v2.23.0 | Report a Bug | By Email