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

"Paul C. Bryan" <paul.bryan@forgerock.com> Tue, 22 November 2011 00:56 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 B50FE21F84B7 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 16:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.665
X-Spam-Level:
X-Spam-Status: No, score=-6.665 tagged_above=-999 required=5 tests=[AWL=-0.067, 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 bPZrY0-EFmBM for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 16:56:18 -0800 (PST)
Received: from eu1sys200aog102.obsmtp.com (eu1sys200aog102.obsmtp.com [207.126.144.113]) by ietfa.amsl.com (Postfix) with SMTP id 8035F1F0C67 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 16:56:17 -0800 (PST)
Received: from mail-yw0-f46.google.com ([209.85.213.46]) (using TLSv1) by eu1sys200aob102.postini.com ([207.126.147.11]) with SMTP ID DSNKTsrzI76063RJTvVofxrm2DBU6f5rN6Qc@postini.com; Tue, 22 Nov 2011 00:56:17 UTC
Received: by mail-yw0-f46.google.com with SMTP id 32so7174436ywt.33 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 16:56:03 -0800 (PST)
Received: by 10.236.179.7 with SMTP id g7mr23118337yhm.74.1321923363588; Mon, 21 Nov 2011 16:56:03 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id c10sm16902279yhj.2.2011.11.21.16.56.02 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 16:56:03 -0800 (PST)
Message-ID: <1321923360.1990.34.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Date: Mon, 21 Nov 2011 16:56:00 -0800
In-Reply-To: <E880E90A-332F-4D2F-9B20-7B7ADD03FE27@mnot.net>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron> <4ECAA9FE.6080802@gmx.de> <1321905599.1990.23.camel@neutron> <4ECAAF39.8000702@gmx.de> <1321906189.1990.26.camel@neutron> <4ECAB0BC.0@gmx.de> <6462023D-F767-45DE-9AF0-011CC48374CF@mnot.net> <1321912269.1990.32.camel@neutron> <E880E90A-332F-4D2F-9B20-7B7ADD03FE27@mnot.net>
Content-Type: multipart/alternative; boundary="=-w6SzAmO2CMbMNO51UqSh"
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: Tue, 22 Nov 2011 00:56:22 -0000

And of course, if a pointer references a member name with a slash, then
%25 MUST be used...

Paul

On Tue, 2011-11-22 at 10:43 +1100, Mark Nottingham wrote:

> The usual approach to this sort of thing is to define the "canonical" way to do it; i.e., json pointers *are* unicode strings; then you can define encodings into various environments (like URIs).
> 
> In this case, it'd probably be good enough to say that json pointers are unicode strings, but that when they need to be in ASCII environments (like URIs) they get UTF-8'ed and then percent-escaped.
> 
> Cheers,
> 
> 
> On 22/11/2011, at 8:51 AM, Paul C. Bryan wrote:
> 
> > Okay, so I'll write-up separate sections for JSON string values and URI fragment identifiers. Any objections?
> > 
> > Paul
> > 
> > On Tue, 2011-11-22 at 07:55 +1100, Mark Nottingham wrote:
> >> +1 to Julian here -- there's no reason why non-ASCII chars need to be percent-encoded when they occur inside a JSON document, only when they're in a URI (or similar context).
> >> 
> >> Cheers,
> >> 
> >> 
> >> On 22/11/2011, at 7:12 AM, Julian Reschke wrote:
> >> 
> >> > On 2011-11-21 21:09, Paul C. Bryan wrote:
> >> >> 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.
> >> >> ...
> >> > 
> >> > Well, you could use it as fragment identifier (or otherwise URI component) by UTF-8-percent-escaping.
> >> > 
> >> > The question is whether that use case requires them to be all ASCII every else, such as in a JSON patch document.
> >> > 
> >> > Best regards, Julian
> >> > _______________________________________________
> >> > apps-discuss mailing list
> >> > 
> >> apps-discuss@ietf.org
> >> 
> >> > 
> >> https://www.ietf.org/mailman/listinfo/apps-discuss
> >> 
> >> 
> >> --
> >> Mark Nottingham   
> >> http://www.mnot.net/
> >> 
> >> 
> >> 
> >> 
> >> 
> > 
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
>