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

The usual approach to this sort of thing is to define the "canonical" way to do it; i.e., json pointers *are* unicode strings; then you can define encodings into various environments (like URIs).

In this case, it'd probably be good enough to say that json pointers are unicode strings, but that when they need to be in ASCII environments (like URIs) they get UTF-8'ed and then percent-escaped.

Cheers,

On 22/11/2011, at 8:51 AM, Paul C. Bryan wrote:

> Okay, so I'll write-up separate sections for JSON string values and URI fragment identifiers. Any objections?
> 
> Paul
> 
> On Tue, 2011-11-22 at 07:55 +1100, Mark Nottingham wrote:
>> +1 to Julian here -- there's no reason why non-ASCII chars need to be percent-encoded when they occur inside a JSON document, only when they're in a URI (or similar context).
>> 
>> Cheers,
>> 
>> 
>> On 22/11/2011, at 7:12 AM, Julian Reschke wrote:
>> 
>> > On 2011-11-21 21:09, Paul C. Bryan wrote:
>> >> The intent is to allow a JSON Pointer to be expressed as a JSON string
>> >> value as well as a URI fragment identifier. The latter is the most
>> >> significant driver for URI percent-encoding.
>> >> ...
>> > 
>> > Well, you could use it as fragment identifier (or otherwise URI component) by UTF-8-percent-escaping.
>> > 
>> > The question is whether that use case requires them to be all ASCII every else, such as in a JSON patch document.
>> > 
>> > Best regards, Julian
>> > _______________________________________________
>> > apps-discuss mailing list
>> > 
>> apps-discuss@ietf.org
>> 
>> > 
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> 
>> 
>> --
>> Mark Nottingham   
>> http://www.mnot.net/
>> 
>> 
>> 
>> 
>> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--
Mark Nottingham   http://www.mnot.net/