IETF Logo Mail Archive

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

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 21 November 2011 19:37 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 45CA11F0C62 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.92
X-Spam-Level:
X-Spam-Status: No, score=-2.92 tagged_above=-999 required=5 tests=[AWL=-0.321, BAYES_00=-2.599]
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 PTw9iCJj8wNP for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:37:02 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id F2CE31F0C79 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 11:37:01 -0800 (PST)
Received: (qmail invoked by alias); 21 Nov 2011 19:36:59 -0000
Received: from dslb-094-222-145-118.pools.arcor-ip.net (EHLO HIVE) [94.222.145.118] by mail.gmx.net (mp061) with SMTP; 21 Nov 2011 20:36:59 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19fXHdPNgRf5OAR1d1OmclBLqpAECtyGDINOohNrd 3cn9jITJEJK4Lv
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Paul C. Bryan" <paul.bryan@forgerock.com>
Date: Mon, 21 Nov 2011 20:37:05 +0100
Message-ID: <2n9lc79c8or4de9dpvi4s1s8vd186mosj8@hive.bjoern.hoehrmann.de>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron>
In-Reply-To: <1321903463.1990.16.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 19:37:07 -0000

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

RFC 3986 only defines the character encoding for the host component, in
other components it just defines that %C3 refers to the octet 0xC3. So,
if you want that %C3%B6 refers to an "ö", then you have to define that.
-- 
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/

v2.23.0 | Report a Bug | By Email