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

[Julian Reschke <[e-mail]>]

On 2011-11-21 20:54, Paul C. Bryan wrote:
> I'm interpreting section 2.5 of RFC 3896:
>
>> When a new URI scheme defines a component that represents textual data
>> consisting of characters from the Universal Character Set [UCS], the
>> data should first be encoded as octets according to the UTF-8
>> character encoding [STD63]; then only those octets that do not
>> correspond to characters in the unreserved set should be
>> percent-encoded. For example, the character A would be represented as
>> "A", the character LATIN CAPITAL LETTER A WITH GRAVE would be
>> represented as "%C3%80", and the character KATAKANA LETTER A would be
>> represented as "%E3%82%A2".
>
> Is this not applicable?

No.

For starters, we are not defining a URI scheme at all.

We're just re-using percent-encoding, and that is about mapping octets 
to characters. We still need to state what the octets are.

Best regards, Julian