IETF Logo Mail Archive

Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII

"Paul C. Bryan" <paul.bryan@forgerock.com> Mon, 21 November 2011 20:00 UTC

Return-Path: <paul.bryan@forgerock.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90AD811E80EE for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.689
X-Spam-Level:
X-Spam-Status: No, score=-6.689 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 PoEFK8B5ZCyF for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:00:03 -0800 (PST)
Received: from eu1sys200aog101.obsmtp.com (eu1sys200aog101.obsmtp.com [207.126.144.111]) by ietfa.amsl.com (Postfix) with SMTP id 1217A1F0C3C for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:00:02 -0800 (PST)
Received: from mail-qw0-f46.google.com ([209.85.216.46]) (using TLSv1) by eu1sys200aob101.postini.com ([207.126.147.11]) with SMTP ID DSNKTsqtwTYy5wFNrUmoCYjIiJdBCKlg+wAr@postini.com; Mon, 21 Nov 2011 20:00:03 UTC
Received: by mail-qw0-f46.google.com with SMTP id c14so539652qad.19 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:00:01 -0800 (PST)
Received: by 10.224.27.11 with SMTP id g11mr6590096qac.51.1321905601781; Mon, 21 Nov 2011 12:00:01 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id ho10sm11572251qab.11.2011.11.21.12.00.00 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 12:00:00 -0800 (PST)
Message-ID: <1321905599.1990.23.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Date: Mon, 21 Nov 2011 11:59:59 -0800
In-Reply-To: <4ECAA9FE.6080802@gmx.de>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron> <4ECAA9FE.6080802@gmx.de>
Content-Type: multipart/alternative; boundary="=-YCROgOGwkXckC7iGeRw0"
X-Mailer: Evolution 3.0.3-2
Mime-Version: 1.0
Subject: Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 20:00:04 -0000

On Mon, 2011-11-21 at 20:43 +0100, Julian Reschke wrote:


> Not really -- RFC 3986 doesn't really require it; it just says it should 
> be the default for new schemes.
> 
> So again, do you want the ability to use non-ASCII characters in JSON 
> pointers without escaping? (I think that would be the right approach.)


Presuming section 2.5 is not applicable (or cannot be made applicable by
reference), then we would need to explicitly specify an encoding. Since
JSON is Unicode by definition, following the recommendation set forth in
section 2.5 to encode as UTF-8 and percent-encode each non-unreserved
octet would seem most appropriate.

Paul

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