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

Julian Reschke <> Wed, 23 November 2011 13:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DA41921F8CA4 for <>; Wed, 23 Nov 2011 05:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -103.966
X-Spam-Status: No, score=-103.966 tagged_above=-999 required=5 tests=[AWL=-1.367, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oDpUeXqQAx1t for <>; Wed, 23 Nov 2011 05:17:51 -0800 (PST)
Received: from ( []) by (Postfix) with SMTP id 02D1D21F8C85 for <>; Wed, 23 Nov 2011 05:17:50 -0800 (PST)
Received: (qmail invoked by alias); 23 Nov 2011 13:17:49 -0000
Received: from (EHLO []) [] by (mp016) with SMTP; 23 Nov 2011 14:17:49 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18IkzMNQGYIx+3+a/FVZuezf3W2sGqVwsKdfkWnuY tNN4MiSwSUm5UG
Message-ID: <>
Date: Wed, 23 Nov 2011 14:17:43 +0100
From: Julian Reschke <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: IETF Apps Discuss <>
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Subject: Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 23 Nov 2011 13:17:52 -0000

On 2011-11-21 15:12, Julian Reschke wrote:
> ...

Summarizing the open questions:

1) Which characters to *allow* in a JSON pointer (independently of where 
it appears)

1a) Allow non-ASCII (also, how to represent non-BMP characters)

1b) Allow ASCII characters that are reserved in URIs

2) What to use as delimiter, given the fact JSON identifiers allow 
anything that can occur in a JSON string (or: how to represent the "/")

3) How to map a JSON pointer to something that can be used inside a URI 
(path, query?, fragment identifier)

My two cents:

1a) yes, and represent a surrogate pair by the Unicode character it 

1b) yes

2) I have no good idea; James suggested the Unicode replacement 
character, another idea would be a private use code point; using a 
JSON-escape ("\") has the drawback that it needs additional escaping in 
a URI, and that it may be hard to distinguish from the escaped variant 
when it appears in a JSON document, such as JSON-Patch)

3) encode-as-UTF8-then-percent-escape-everything-reserved-in-URI

Best regards, Julian