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 20:12 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 4DA9321F8564 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.348
X-Spam-Level:
X-Spam-Status: No, score=-104.348 tagged_above=-999 required=5 tests=[AWL=-1.749, 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 AM1ZKdt82sIm for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:12:49 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 5E39911E80E7 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:12:49 -0800 (PST)
Received: (qmail invoked by alias); 21 Nov 2011 20:12:48 -0000
Received: from p5DCC9581.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.149.129] by mail.gmx.net (mp072) with SMTP; 21 Nov 2011 21:12:48 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/gS3Mqnx/ggwh13qivVhzIBso15MnF2XwG4vyEcF ndJFz79Ltzs+7Z
Message-ID: <4ECAB0BC.0@gmx.de>
Date: Mon, 21 Nov 2011 21:12:44 +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> <4ECAA9FE.6080802@gmx.de> <1321905599.1990.23.camel@neutron> <4ECAAF39.8000702@gmx.de> <1321906189.1990.26.camel@neutron>
In-Reply-To: <1321906189.1990.26.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:12:50 -0000

On 2011-11-21 21:09, Paul C. Bryan wrote:
> The intent is to allow a JSON Pointer to be expressed as a JSON string
> value as well as a URI fragment identifier. The latter is the most
> significant driver for URI percent-encoding.
> ...

Well, you could use it as fragment identifier (or otherwise URI 
component) by UTF-8-percent-escaping.

The question is whether that use case requires them to be all ASCII 
every else, such as in a JSON patch document.

Best regards, Julian

v2.29.0 | Report a Bug | By Email | System Status