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

["Paul C. Bryan" <[e-mail]>]

So far I can't say I like it very much. Is the suggestion that every
member name in a JSON pointer reference must contain \" ... \"? This
makes for one ugly pointer in JSON, and absolutely guarantees that a
fragment identifier will contain multiple percent-encoded values, even
if there are no members that contain path delimiters.

#/a/b/c ← intuitive
#/%5C%22a%5C%22/%5C%22b%5C%22/%5C%22c%5C%22 ← not!  

Paul

On Wed, 2011-11-23 at 10:12 +0100, Julian Reschke wrote:

> On 2011-11-23 00:17, Martin Thomson wrote:
> >> So yes, the fact that a JSON name can be anything a JSON string can take is
> >> indeed a problem, because it doesn't leave us any characters as delimiters
> >> (so this is very different from XML vs XPath).
> >
> > Maybe you could use a JSON string notation as your canonical form:
> >
> > { "Bjørn/Carsten/foo \uD834\uDD1E" : "Fritz" }
> > ->
> > "/\"Bjørn/Carsten/foo \uD834\uDD1E\""
> 
> I like that.
> 
> Best regards, Julian
> 
> _______________________________________________
> apps-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/apps-discuss