Re: [apps-discuss] Confusing JSON Pointer

["Martin J. Dürst" <[e-mail]>]

Hello Paul, others,

On 2012/03/28 10:36, Paul C. Bryan wrote:
> On Wed, 2012-03-28 at 08:47 +0900, 지송원 James Songwon Chi wrote:
>
>> 2012년 3월 27일 오후 11:23, Julian Reschke<[e-mail]>님의 말:
>>> On 2012-03-27 15:49, 지송원 James Songwon Chi wrote:
>>>> 2012년 3월 27일 오후 4:57, Julian Reschke<[e-mail]>님의 말:
>>>>> On 2012-03-27 07:22, 지송원 James Songwon Chi wrote:

>>>>>> And if my interpretation is wrong, to prevent the similar question,
>>>>>> there should be some examples for this kind.
>>>>>> ...

Can we please make sure that we add some example(s) and clarify the spec 
so that such questions can be avoided in the future?

> The intent of the draft is to establish rules for encoding in a JSON
> string or in a URI. Of course, I agree that a URI can in turn be
> expressed in a JSON string, but in this case, URI encoding applies; you
> do not mix-and-match encodings.
>
>
>> By the way, do we really *need another escape* even there are two
>> encodings already?
>
>
> I'm not sure what you mean here. If you encode as URI, presumably all
> valid URI characters are representable without any further escaping in a
> JSON string.

Can we please make sure this is as clear as possible in the spec?

Regards,   Martin.