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

[Julian Reschke <[e-mail]>]

On 2011-11-21 15:12, Julian Reschke wrote:
> ...

Summarizing the open questions:

1) Which characters to *allow* in a JSON pointer (independently of where 
it appears)

1a) Allow non-ASCII (also, how to represent non-BMP characters)

1b) Allow ASCII characters that are reserved in URIs

2) What to use as delimiter, given the fact JSON identifiers allow 
anything that can occur in a JSON string (or: how to represent the "/")

3) How to map a JSON pointer to something that can be used inside a URI 
(path, query?, fragment identifier)


My two cents:

1a) yes, and represent a surrogate pair by the Unicode character it 
represents

1b) yes

2) I have no good idea; James suggested the Unicode replacement 
character, another idea would be a private use code point; using a 
JSON-escape ("\") has the drawback that it needs additional escaping in 
a URI, and that it may be hard to distinguish from the escaped variant 
when it appears in a JSON document, such as JSON-Patch)

3) encode-as-UTF8-then-percent-escape-everything-reserved-in-URI

Best regards, Julian