Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII
"Paul C. Bryan" <paul.bryan@forgerock.com> Mon, 21 November 2011 19:24 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 AC81D1F0C85 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 J8t06R6B-Kkk for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:24:41 -0800 (PST)
Received: from eu1sys200aog103.obsmtp.com (eu1sys200aog103.obsmtp.com [207.126.144.115]) by ietfa.amsl.com (Postfix) with SMTP id 217501F0C5A for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 11:24:40 -0800 (PST)
Received: from mail-qw0-f44.google.com ([209.85.216.44]) (using TLSv1) by eu1sys200aob103.postini.com ([207.126.147.11]) with SMTP ID DSNKTsqlarP8yRF9IdceJ8E1wKTF5j90BwfU@postini.com; Mon, 21 Nov 2011 19:24:41 UTC
Received: by mail-qw0-f44.google.com with SMTP id b14so505265qad.10 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 11:24:26 -0800 (PST)
Received: by 10.224.98.8 with SMTP id o8mr6372711qan.79.1321903466321; Mon, 21 Nov 2011 11:24:26 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id t8sm11467778qaz.4.2011.11.21.11.24.25 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 11:24:25 -0800 (PST)
Message-ID: <1321903463.1990.16.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Date: Mon, 21 Nov 2011 11:24:23 -0800
In-Reply-To: <4ECA5C66.1040305@gmx.de>
References: <4ECA5C66.1040305@gmx.de>
Content-Type: multipart/alternative; boundary="=-m4Un/azgSRIwS7kWOAXI"
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 19:24:45 -0000
RFC 3986 prescribes encoding characters in UTF-8 and percent-encoding non-unreserved characters. Furthermore, JSON by definition uses Unicode for all string values (most often encoding in UTF-8). Do these not address the issue? Paul On Mon, 2011-11-21 at 15:12 +0100, Julian Reschke wrote: > Hi there. > > In > <https://tools.ietf.org/html/draft-pbryan-zyp-json-pointer-02#section-3> > we have: > > A JSON Pointer is a sequence of zero or more reference tokens, each > prefixed by a "/" (%x2F) character. Each reference token is a > sequence of unreserved and/or percent-encoded characters, per > [RFC3986]. > > json-pointer = *( "/" reference-token ) > reference-token = *( unreserved / pct-encoded ) > > Characters in reference tokens that are not unreserved SHOULD be > percent-encoded, per [RFC3986], and MUST be so encoded as "%2F" if > the character is "/" to avoid being interpreted as a reference token > prefix. > > It is an error condition if a JSON Pointer does not conform to this > syntax. > > This doesn't seem to consider the case where the reference token > contains non-ASCII characters, which can happen with JSON. > > There seem to be to obvious ways to address this: > > (1) Allow non-ASCII characters in the pointer (which would make the > pointers be more IRI-like, and I think that's consistent with XPath), or > > (2) Require UTF-8 encoding. > > I believe (1) makes more sense here. > > Best regards, Julian > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss
- 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