IETF Logo Mail Archive

Re: [apps-discuss] draft-ietf-appsawg-json-pointer escape characters

Julian Reschke <julian.reschke@gmx.de> Thu, 12 April 2012 15:52 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 EF0EB21F851B for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 08:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.848
X-Spam-Level:
X-Spam-Status: No, score=-102.848 tagged_above=-999 required=5 tests=[AWL=-0.249, 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 bpr12uAOHcOl for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 08:52:42 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id AD4E821F850C for <apps-discuss@ietf.org>; Thu, 12 Apr 2012 08:52:39 -0700 (PDT)
Received: (qmail invoked by alias); 12 Apr 2012 15:52:38 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp038) with SMTP; 12 Apr 2012 17:52:38 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19sSeRNXYNsNZIvF4P8fcu6kMjNHqrSK0Ui2eJ3wE y93JwJzMX9zJCr
Message-ID: <4F86FA46.4020504@gmx.de>
Date: Thu, 12 Apr 2012 17:52:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Joe Hildebrand <jhildebr@cisco.com>
References: <CBAC55A2.2784D%jhildebr@cisco.com>
In-Reply-To: <CBAC55A2.2784D%jhildebr@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] draft-ietf-appsawg-json-pointer escape characters
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: Thu, 12 Apr 2012 15:52:43 -0000

On 2012-04-12 17:49, Joe Hildebrand wrote:
> I really like this.  Would you unescape *all* %-encoded, or just the ones in
> that list?  What about escape sequences that lead to invalid UTF-8, for
> example?
> ...

Assuming that your question refers to the process of retrieving a 
sequence of reference tokens from a URI path...

I would

1) separate into URI path segments (using "/" as delimiter)

2) for each path segment, percent-unescape-then-UTF8-decode to obtain 
the reference token

Best regards, Julian

v2.23.0 | Report a Bug | By Email