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:09 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 BFE9721F8A4E for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.682
X-Spam-Level:
X-Spam-Status: No, score=-6.682 tagged_above=-999 required=5 tests=[AWL=-0.084, 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 RIKe1YPuOu3j for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:09:55 -0800 (PST)
Received: from eu1sys200aog111.obsmtp.com (eu1sys200aog111.obsmtp.com [207.126.144.131]) by ietfa.amsl.com (Postfix) with SMTP id 5757C21F89BA for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:09:54 -0800 (PST)
Received: from mail-gy0-f175.google.com ([209.85.160.175]) (using TLSv1) by eu1sys200aob111.postini.com ([207.126.147.11]) with SMTP ID DSNKTsqwEbw4crlKfmRynLlD9czczeuCSUmN@postini.com; Mon, 21 Nov 2011 20:09:54 UTC
Received: by ghy10 with SMTP id 10so3180614ghy.6 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:09:52 -0800 (PST)
Received: by 10.42.156.9 with SMTP id x9mr14887059icw.42.1321906192541; Mon, 21 Nov 2011 12:09:52 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id dd36sm50104470ibb.7.2011.11.21.12.09.51 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 12:09:51 -0800 (PST)
Message-ID: <1321906189.1990.26.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Date: Mon, 21 Nov 2011 12:09:49 -0800
In-Reply-To: <4ECAAF39.8000702@gmx.de>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron> <4ECAA9FE.6080802@gmx.de> <1321905599.1990.23.camel@neutron> <4ECAAF39.8000702@gmx.de>
Content-Type: multipart/alternative; boundary="=-ib3CyF6vNPll2VuP0bza"
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:09:56 -0000
The intent is to allow a JSON Pointer to be expressed as a JSON string value as well as a URI fragment identifier. The latter is the most significant driver for URI percent-encoding. Paul On Mon, 2011-11-21 at 21:06 +0100, Julian Reschke wrote: > On 2011-11-21 20:59, Paul C. Bryan wrote: > > 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 > > ... > > Yes, that would work. > > However, why encode those characters in the first place? Where does the > requirement that the pointer needs to be all-ASCII come from? > > Best regards, Julian
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- [apps-discuss] draft-pbryan-zyp-json-pointer: nam… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Bjoern Hoehrmann
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Bjoern Hoehrmann
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Frank Ellermann
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Mark Nottingham
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Mark Nottingham
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Martin J. Dürst
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Carsten Bormann
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Graham Klyne
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Martin Thomson
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Carsten Bormann
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Martin Thomson
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Martin J. Dürst
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer:… Paul C. Bryan
- [apps-discuss] Fw: draft-pbryan-zyp-json-pointer:… t.petch
- Re: [apps-discuss] Fw: draft-pbryan-zyp-json-poin… Martin J. Dürst
- [apps-discuss] draft-pbryan-zyp-json-pointer prog… Julian Reschke
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer … Paul C. Bryan
- Re: [apps-discuss] draft-pbryan-zyp-json-pointer … Julian Reschke