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

[Julian Reschke <[e-mail]>]

On 2011-11-21 20:59, Paul C. Bryan wrote:
> On Mon, 2011-11-21 at 20:43 +0100, Julian Reschke wrote:
>
>> Not really -- RFC 3986 doesn't really require it; it just says it should
>> be the default for new schemes.
>>
>> So again, do you want the ability to use non-ASCII characters in JSON
>> pointers without escaping? (I think that would be the right approach.)
>
> Presuming section 2.5 is not applicable (or cannot be made applicable by
> reference), then we would need to explicitly specify an encoding. Since
> JSON is Unicode by definition, following the recommendation set forth in
> section 2.5 to encode as UTF-8 and percent-encode each non-unreserved
> octet would seem most appropriate.
>
> Paul
> ...

Yes, that would work.

However, why encode those characters in the first place? Where does the 
requirement that the pointer needs to be all-ASCII come from?

Best regards, Julian