Re: [apps-discuss] character repertoire for fragment identifiers, was: Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt

[Julian Reschke <[e-mail]>]

On 2015-01-12 10:11, "Martin J. Dürst" wrote:
> On 2015/01/12 01:19, Sam Ruby wrote:
>> On 01/11/2015 10:53 AM, Julian Reschke wrote:
>
>> To you, RFC 3986 (including potential errata and/or bis work) implies
>> ASCII.
>
> Sam - As far as I have looked at your spec, the main difference between
> fragments and the rest of an URL is that fragments don't get %-encoded
> but stay as Unicode when parsing.
>
>
>> I point out that that restriction does not seem to make sense for
>> fragments.
>
>  From an user point, the restriction doesn't make sense for any part of
> an UR?. From a protocol point, there are protocols/formats where slots

Exactly.

Another thing to consider is what we gain by allowing non-ASCII in a 
single place in the identifier as opposed to the confusion caused of 
having different rules for the different parts.

> ...

Best regards, Julian