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

[Carsten Bormann <[e-mail]>]

On Nov 21, 2011, at 21:55, 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).

OK, folks, let's see where that leads to.

JSON document:
{"Bjørn/Carsten": "Fritz"}

JSON pointer:
"/Bjørn%2FCarsten"

Multi-segment URI-encoded version of this JSON pointer:

/Bj%C3%B8rn%252FCarsten

(For reference: Plain URI-encoded version:

%2FBj%C3%B8rn%252FCarsten
)

If this is what you want, please document it thoroughly, clearly, painfully redundantly.
Dozens of examples, including examples that show how to do it wrong.

With this kind of dual-layer percent-encoding, we are deeply in quoting hell, and implementers will need all the help we can give them (and they will still get it wrong).

Grüße, Carsten