IETF Logo Mail Archive

Re: [Json] Proposal: the minimal edit

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 24 June 2013 23:42 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 B086B11E817F for <json@ietfa.amsl.com>; Mon, 24 Jun 2013 16:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level:
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 2GebPIZzVuE5 for <json@ietfa.amsl.com>; Mon, 24 Jun 2013 16:42:17 -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 D658F11E8167 for <json@ietf.org>; Mon, 24 Jun 2013 16:42:17 -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 r5ONgFh3090798 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Jun 2013 16:42:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130624233521.GF19899@mercury.ccil.org>
Date: Mon, 24 Jun 2013 16:42:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D442E5F-F9ED-47DB-9E1D-29ACA8588717@vpnc.org>
References: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com> <CAHBU6ivhoUM9cfUnc1YfnyDdQnWQ=Mj10cSoYn0qouMQ0F94XA@mail.gmail.com> <CAChr6SyQDjik_BTojXdw3G7_B=W5iZXksuM15VYwGJqr8WHdhw@mail.gmail.com> <CAChr6SwbFfR5UQuU2ceJhDeGAhv5Zy0dKA3szzO_KGfjA7fx5Q@mail.gmail.com> <B4858680-D319-4603-A1C3-D6A84195B300@vpnc.org> <CAHBU6ivUL6YvtMiajQwfftNgrRJk4dqiFs1yowoxfLi5wh2_hQ@mail.gmail.com> <20130624233521.GF19899@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1508)
Cc: "json@ietf.org WG" <json@ietf.org>
Subject: Re: [Json] Proposal: the minimal edit
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: Mon, 24 Jun 2013 23:42:18 -0000

On Jun 24, 2013, at 4:35 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Tim Bray scripsit:
> 
>> In general I’d support this, with one nit: s/that are not Unicode
>> characters/that can never be Unicode characters/ (just to make it clear
>> we’re not talking about unassigned code points, which don't seem to
>> distress anyone).
> 
> Well, that excludes not only surrogate code points, which are the really
> dangerous ones (because they have no standard representation) but non-character
> code points as well, which shouldn't be interchanged but aren't actually
> dangerous.  I don't know if you mean to do that or not.

I'm not sure what you mean by "exclude". The sentence Tim was referring to is about inclusion:

  - ECMAScript implementations can generate and consume code points in JSON strings that are not
    Unicode characters.

--Paul Hoffman

v2.46.0 | Report a Bug | By Email | System Status