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

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

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?

Paul

On Mon, 2011-11-21 at 20:37 +0100, Bjoern Hoehrmann wrote:

> * Paul C. Bryan wrote:
> >RFC 3986 prescribes encoding characters in UTF-8 and percent-encoding
> >non-unreserved characters. Furthermore, JSON by definition uses Unicode
> >for all string values (most often encoding in UTF-8). Do these not
> >address the issue?
> 
> RFC 3986 only defines the character encoding for the host component, in
> other components it just defines that %C3 refers to the octet 0xC3. So,
> if you want that %C3%B6 refers to an "ö", then you have to define that.