Re: [apps-discuss] What does it mean? (Re: Scope of RFC3986 and successor - what is a URI?)

["Martin J. Dürst" <[e-mail]>]

On 2015/01/17 02:34, Dave Cridland wrote:
> On 16 January 2015 at 15:43, Sam Ruby <[e-mail]> wrote:
>
>> On 01/16/2015 08:57 AM, Dave Cridland wrote:

>>> So with S as http://café.im:80/tŷ/%2e

>>   u.canonical => http://café.im/ty <http://xn--caf-dma.im/ty> <
>>> http://xn--caf-dma.im/ty>
>>>
>>
>> The use case for this would need to be provided.

Like Sam, I'm strongly doubting there is a use case here.

> Comparison for equivalency.

Definitely, 'ty' and 'tŷ' cannot be assumed to be equivalent.

What's more, as explained in
http://tools.ietf.org/html/rfc3986#section-6
comparison/equivalence isn't a single operation, because different 
contexts need and use different equivalences. At one end are XML 
namespaces and RDF, where even 'http://www.example.org' and 
'Http://www.example.org' are different. At the other end are crawlers, 
which in general don't go to 'http://www.example.org/A' if they have 
been to 'http://www.example.org/a', because the chance that they get the 
same thing once again is too big for them to waste time, even if there's 
a chance that the two addresses will return totally different stuff.

So any kind of 'equivalence' or 'canonicalization' or 'normalization' or 
whatever we want to call it has to be qualified: What kind of e.g. 
equivalence, for what.

Regards,    Martin.