IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Mon, 21 November 2011 19:44 UTC

Return-Path: <julian.reschke@gmx.de>
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 2D37E1F0C79 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:44:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.426
X-Spam-Level:
X-Spam-Status: No, score=-104.426 tagged_above=-999 required=5 tests=[AWL=-1.827, BAYES_00=-2.599, 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 dfDLxNwKvjhK for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:44:04 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 49C6D1F0C62 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 11:44:04 -0800 (PST)
Received: (qmail invoked by alias); 21 Nov 2011 19:44:02 -0000
Received: from p5DCC9581.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.149.129] by mail.gmx.net (mp070) with SMTP; 21 Nov 2011 20:44:02 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18hFDI6SdMhNKcbYQSzZujNqFmO3uqdj0q9eFBXSN voF3V1xlNc3qnp
Message-ID: <4ECAA9FE.6080802@gmx.de>
Date: Mon, 21 Nov 2011 20:43:58 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Paul C. Bryan" <paul.bryan@forgerock.com>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron>
In-Reply-To: <1321903463.1990.16.camel@neutron>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
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:44:05 -0000

On 2011-11-21 20:24, Paul C. Bryan wrote:
> 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?
> ...

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.)

Best regards, Julian

v2.23.0 | Report a Bug | By Email