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

[Bjoern Hoehrmann <[e-mail]>]

* 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?

If I recommended "When writing a new crime novel, reveal the perpetrator
towards the end" then the author would still have to write the part, and
the reader would still have to read through the novel to find out where
the perpetrator is revealed, since the author might not be following the
recommendation. Besides, the draft does not define a new scheme. This is
just a matter of using the right incantation, but I don't know why, say,
"/Björn" isn't allowed, so I can't make a good suggestion at the moment.
-- 
Björn Höhrmann · mailto:[e-mail] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: [phone] · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/