Re: [Json] Ambiguous character references
Paul Hoffman <paul.hoffman@vpnc.org> Tue, 18 June 2013 14:05 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 A875F21F9ACC for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 07:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.505
X-Spam-Level:
X-Spam-Status: No, score=-103.505 tagged_above=-999 required=5 tests=[AWL=1.094, BAYES_00=-2.599, GB_I_LETTER=-2, 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 XDosuaq6V8ob for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 07:05:28 -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 26F3021F949F for <json@ietf.org>; Tue, 18 Jun 2013 07:05:25 -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 r5IE4RoM083325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 18 Jun 2013 07:05:19 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <8FDBF4EF-B2DF-458E-834E-5707ED7B27C9@lindenbergsoftware.com>
Date: Tue, 18 Jun 2013 07:05:20 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2AB1B2D-4843-4055-9D6F-2BC32B27AECD@vpnc.org>
References: <8FDBF4EF-B2DF-458E-834E-5707ED7B27C9@lindenbergsoftware.com>
To: "json@ietf.org" <json@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: Re: [Json] Ambiguous character references
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: Tue, 18 Jun 2013 14:05:31 -0000
<no hat> On Jun 17, 2013, at 11:07 PM, Norbert Lindenberg <ietf@lindenbergsoftware.com> wrote: > The existing text in section 2.5 of RFC 4627, first through third paragraph, has the same ambiguous character references as discussed below. Do they need to be fixed? > > quotation marks -> quotation marks (U+0022) > > quotation mark -> quotation mark (U+0022) > > reverse solidus -> reverse solidus (U+005C) > > control characters (U+0000 through U+001F) -> control characters U+0000 through U+001F > > lowercase letter u -> Latin small letter u (U+0075) > > hexadecimal digits -> hexadecimal digits U+0030 through U+0039, U+0041 through U+0046, U+0061 through U+0066 +1 --Paul Hoffman
- [Json] Ambiguous character references Norbert Lindenberg
- Re: [Json] Ambiguous character references Paul Hoffman