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

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?

On 4/12/12 9:34 AM, "Julian Reschke" <julian.reschke@gmx.de> wrote:

> Hi there,
> 
> right now, the draft escapes forward slashes in reference tokens using
> ^-escapes, that is:
> 
>   a/b
> 
> becomes
> 
>   a^/b
> 
> and
> 
>   a^b
> 
> becomes
> 
>   a^^b
> 
> (Reminder: previously "\" was used, but it results in ugly double
> escaping when the pointer occurs in a JSON string).
> 
> A drawback of this scheme is that when the pointer is used inside a URI,
> such as the path component of a an HTTP URI, the / still needs to be
> escaped, so the name
> 
>    a/b
> 
> becomes the pointer
> 
>    a^/b
> 
> and would end up as
> 
>    a%5e%2fb
> 
> in the URI.
> 
> 
> An alternate proposal I heard during the IETF meeting in Paris was to
> simply apply URI percent escaping to the characters in the URI
> gen-delims range:
> 
>   gen-delims  = ":" / "/" / "?" / "#" / "[" / "]" / "@"
> 
> so
> 
>    a/b
> 
> would simply become
> 
>    a%2fb
> 
> and wouldn't need any further escaping in a URI path component.
> 
> Feedback appreciated,
> 
> Julian
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

-- 
Joe Hildebrand