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

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 21 November 2011 20:09 UTC

Return-Path: <derhoermi@gmx.net>
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 ED86F21F87FA for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.895
X-Spam-Level:
X-Spam-Status: No, score=-3.895 tagged_above=-999 required=5 tests=[AWL=0.704, BAYES_00=-2.599, GB_I_LETTER=-2]
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 khkNK013XwId for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:09:14 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 966D21F0C98 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:09:13 -0800 (PST)
Received: (qmail invoked by alias); 21 Nov 2011 20:09:12 -0000
Received: from dslb-094-222-145-118.pools.arcor-ip.net (EHLO HIVE) [94.222.145.118] by mail.gmx.net (mp006) with SMTP; 21 Nov 2011 21:09:12 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/IfV415+bIGUTiSkw2iCjU30xcCQTJy65l8L9ujE 6enSanwQQpRI9X
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Paul C. Bryan" <paul.bryan@forgerock.com>
Date: Mon, 21 Nov 2011 21:09:18 +0100
Message-ID: <n8blc7pieuu5kv58j096g6hnmjqea1qjl5@hive.bjoern.hoehrmann.de>
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>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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:09:19 -0000

* 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?

If I recommended "When writing a new crime novel, reveal the perpetrator
towards the end" then the author would still have to write the part, and
the reader would still have to read through the novel to find out where
the perpetrator is revealed, since the author might not be following the
recommendation. Besides, the draft does not define a new scheme. This is
just a matter of using the right incantation, but I don't know why, say,
"/Björn" isn't allowed, so I can't make a good suggestion at the moment.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/