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

Julian Reschke <julian.reschke@gmx.de> Mon, 21 November 2011 20:02 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 C3B3D1F0C62 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.378
X-Spam-Level:
X-Spam-Status: No, score=-105.378 tagged_above=-999 required=5 tests=[AWL=-0.779, BAYES_00=-2.599, GB_I_LETTER=-2, 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 GeE6Y9A6XTxh for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:02:07 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id C3FE11F0C3C for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:02:06 -0800 (PST)
Received: (qmail invoked by alias); 21 Nov 2011 20:02:04 -0000
Received: from p5DCC9581.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.149.129] by mail.gmx.net (mp011) with SMTP; 21 Nov 2011 21:02:04 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+RF688S2iRR4hxsDgF5KX/hWEzh7EWxXpYeIN9sm NEcHKnDY+khNNX
Message-ID: <4ECAAE38.8050100@gmx.de>
Date: Mon, 21 Nov 2011 21:02:00 +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> <2n9lc79c8or4de9dpvi4s1s8vd186mosj8@hive.bjoern.hoehrmann.de> <1321905297.1990.20.camel@neutron>
In-Reply-To: <1321905297.1990.20.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 20:02:07 -0000

On 2011-11-21 20:54, Paul C. Bryan wrote:
> I'm interpreting section 2.5 of RFC 3896:
>
>> When a new URI scheme defines a component that represents textual data
>> consisting of characters from the Universal Character Set [UCS], the
>> data should first be encoded as octets according to the UTF-8
>> character encoding [STD63]; then only those octets that do not
>> correspond to characters in the unreserved set should be
>> percent-encoded. For example, the character A would be represented as
>> "A", the character LATIN CAPITAL LETTER A WITH GRAVE would be
>> represented as "%C3%80", and the character KATAKANA LETTER A would be
>> represented as "%E3%82%A2".
>
> Is this not applicable?

No.

For starters, we are not defining a URI scheme at all.

We're just re-using percent-encoding, and that is about mapping octets 
to characters. We still need to state what the octets are.

Best regards, Julian