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

[Julian Reschke <[e-mail]>]

On 2012-04-12 18:21, Paul C. Bryan wrote:
> This takes us back to a previous version of JSON Pointer
> <http://tools.ietf.org/html/draft-pbryan-zyp-json-pointer-02>, which in
> fact did use URI escaping of %2F to distinguish between the '/' token
> delimiter and a '/' character within a token. IIRC, the objections that
> lead us to change were:
>
> 1. It requires URI decoding logic in non-URI-processing code (e.g. when
> pointers are used in JSON strings rather than in URI fragment
> identifiers). This has always been a somewhat weak argument, IMO.

The way you state is slightly misleading. You don't need URI decoding 
logic; you just need percent-decoding logic (which is only small part of 
URI parsing). And you need *some* kind of unescaping anyway, so I don't 
see the material difference...

> 2. Some URI parsers normalize the URI (i.e. expand %2F into '/') before
> any JSON Pointer parsing code can get a chance to see it.

Again; don't use a URI parser. Just %-unescape.

> In response to this, I went down the path of using a single escape
> character. If we can overcome these objections, I'd be happy to
> entertain returning to URI escaping.

I think it would be worthwhile to do.

Best regards, Julian