Re: [Json] Proposal: Code points and surrogates

Nico Williams <nico@cryptonector.com> Sat, 22 June 2013 20:32 UTC

Return-Path: <nico@cryptonector.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 E6B7721F9CD3 for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 XpV5tKs4Kgcl for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:32:22 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 1216821F9CB3 for <json@ietf.org>; Sat, 22 Jun 2013 13:32:22 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id A2A8850808D for <json@ietf.org>; Sat, 22 Jun 2013 13:32:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=3pkQGIxvY6tpdvih6fvs CEuZ6bw=; b=NEi5RLkDDIg0oC/3xkszfhMtnheW5fK6d19iKxZ4c7GqzN7DThy8 3fHfFh0fQ2JYZKkqrwgH14U5hdOVaulW6TU0xRWfc+REs7pybT+H5soqHRulETRh ybHGhrP7TaxhcM7rMq8Ul6KEQQmWKaoXg2M1xA+8Cm+CM9qAn2iF6vA=
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTPSA id 56ECD50808C for <json@ietf.org>; Sat, 22 Jun 2013 13:32:20 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id ey16so1497292wid.10 for <json@ietf.org>; Sat, 22 Jun 2013 13:32:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q9YjQe0Uu/f2RSnoMjvYNbw2DWCM5gx1PpcMal++fzM=; b=P32/3MdYfvtPMauL04lazJEdunkmtc8JzHiCjZJJXbdepE21fCqLxPg/LGnxOeTssh k0qrFiOVLy46NJie8AHtLc+iFMMpo1iXz2fX68UDXIlfK9xO2Lnmu57i873JZBdx5XbY sDl+lt8Mn8H3t+mx4zj75ig5Blu/mVm7eiGnuo/6yDmCw3NPhp2HBUsWugVEC7ys/ARP v3r4RsfZ2g1tVUkdgsx4d/1FuqCAUixTIZ7l9O+kgDdW/PzyakBICty6NcL9uBkq4AO1 G2oilt2mHP3yCdX4RqWgLDnxGG5TFTOZ15gGkHYzR9a92qGipM5PGRLFhM8Oo1AhH2AA 9vmQ==
MIME-Version: 1.0
X-Received: by 10.194.8.163 with SMTP id s3mr12863290wja.41.1371933138908; Sat, 22 Jun 2013 13:32:18 -0700 (PDT)
Received: by 10.216.29.5 with HTTP; Sat, 22 Jun 2013 13:32:18 -0700 (PDT)
Received: by 10.216.29.5 with HTTP; Sat, 22 Jun 2013 13:32:18 -0700 (PDT)
In-Reply-To: <FB5408B8-68ED-4ACB-96DE-C3AD69240B10@lindenbergsoftware.com>
References: <05A7D2E5-C119-4900-B52B-54B0F1206300@lindenbergsoftware.com> <CA+mHimPF5Q4us+pUKnT79h6SbS63Qh7bAOkp4tSpaCvDWZf-2g@mail.gmail.com> <FB5408B8-68ED-4ACB-96DE-C3AD69240B10@lindenbergsoftware.com>
Date: Sat, 22 Jun 2013 15:32:18 -0500
Message-ID: <CAK3OfOhKc4PP7NHoTDce8KK-ZB01DEw=hCQLAZc+EyUjsD0tRw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Norbert Lindenberg <ietf@lindenbergsoftware.com>
Content-Type: multipart/alternative; boundary="047d7b5d253e66a06604dfc41398"
Cc: Stephen Dolan <stephen.dolan@cl.cam.ac.uk>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal: Code points and surrogates
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: Sat, 22 Jun 2013 20:32:27 -0000

I don't think it's any more reasonable to require that parsers pass through
any old non-Unicode string contents than it would be to require a specific
range of real numbers to be passed by all parsers.  Or at least it would be
surprising to find JSON to be so.  Also, I can agree that parsers should
pass through any odd escaped non-character data, but not that they should
unescape such data.