Re: [apps-discuss] Confusing JSON Pointer

[지송원 James Songwon Chi <[e-mail]>]

2012년 3월 27일 오후 4:57, Julian Reschke <[e-mail]>님의 말:
> On 2012-03-27 07:22, 지송원 James Songwon Chi wrote:
>>
>> After reading JSON Pointer (draft-ietf-appsawg-json-pointer-01), I am
>> confused with encoding or escape scheme.
>> For me, it is an ambiguous scheme. For example, a reference token
>> "ref/1" can be expressed following ways:
>>
>> 1) If it is a URI fragment identifier and a JSON Pointer
>>      Step 1. apply URI encoding: ref%5C1
>>      Step 2. apply JSON Pointer encoding:  ref%5C1
>>      Final result: ref%5C1
>>
>> 2) If it is a JSON Pointer and a URI fragment identifier
>>      Step 1. apply JSON Pointer encoding: ref^/1
>>      Step 2. apply URI encoding:  ref^%5C1
>>      Final result: ref^%5C1
>>
>> I expected the same results.
>>
>> And if my interpretation is wrong, to prevent the similar question,
>> there should be some examples for this kind.
>> ...
>
>
> I don't understand the question.
>
> The spec states how to put JSON Pointers (^-escaping) into fragment
> identifiers (%-escaping).
>
> As far as I can tell the outcome then is what you have under 2), no?
>
> Best regards, Julian

Thank you Julian for the reply.
Yes. Answer is 2) for above question. Well, but I gave a wrong
question and a wrong example (And solidus is 0x2F, not 0x5C.)

This is corrected one:

If I want a JSON Pointer to be represented as both a JSON String and a
URI fragment identifier, I should apply three encoding scheme.
There are two sequences with example:

1) step 1. JSON Pointer escape:  ref^/1
    step 2. JSON String escape:    ref^\/1
    step 3. URI encoding:              ref^\%2F1

2) step 1. JSON Pointer escape: ref^/1
    step 2. URI encoding:              ref^%2F1
    step 3. JSON String escape:    ref^%2F1

The results are same except  only when there is a solidus and it is
encoded as '\/' during JSON String encoding.
As in the example, ref^/1 becomes either ref^\%2F1  or  ref^%2F1 ( differs '\').

Note that JSON String allows multiple encodings for a character.  For
a soldus(/) there are four possible encodings -  '/', '\/', '\u002F',
and '\u002f'.  Also URI encoding allows multiple encodings in case of
percentage encoding - %2F and %2f.


Any comment?

James