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

Carsten Bormann <cabo@tzi.org> Tue, 22 November 2011 09:33 UTC

Return-Path: <cabo@tzi.org>
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 108B121F8CF9 for <apps-discuss@ietfa.amsl.com>; Tue, 22 Nov 2011 01:33:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.199
X-Spam-Level:
X-Spam-Status: No, score=-106.199 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 Cn935cftjRpF for <apps-discuss@ietfa.amsl.com>; Tue, 22 Nov 2011 01:33:58 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 1117221F8A7D for <apps-discuss@ietf.org>; Tue, 22 Nov 2011 01:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id pAM9XnHg020632; Tue, 22 Nov 2011 10:33:49 +0100 (CET)
Received: from [192.168.217.112] (p54899DAB.dip.t-dialin.net [84.137.157.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id B1A0EF18; Tue, 22 Nov 2011 10:33:48 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6462023D-F767-45DE-9AF0-011CC48374CF@mnot.net>
Date: Tue, 22 Nov 2011 10:33:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7E6E395-463D-4D0C-A352-EAD4B5A27202@tzi.org>
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>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1251.1)
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: Tue, 22 Nov 2011 09:33:59 -0000

On Nov 21, 2011, at 21:55, 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).

OK, folks, let's see where that leads to.

JSON document:
{"Bjørn/Carsten": "Fritz"}

JSON pointer:
"/Bjørn%2FCarsten"

Multi-segment URI-encoded version of this JSON pointer:

/Bj%C3%B8rn%252FCarsten

(For reference: Plain URI-encoded version:

%2FBj%C3%B8rn%252FCarsten
)

If this is what you want, please document it thoroughly, clearly, painfully redundantly.
Dozens of examples, including examples that show how to do it wrong.

With this kind of dual-layer percent-encoding, we are deeply in quoting hell, and implementers will need all the help we can give them (and they will still get it wrong).

Grüße, Carsten