Re: URI comparison (was Re: minutes of 2008-10-08 telecon)

On Wed, Oct 15, 2008 at 9:20 PM, Yves Lafon <ylafon@w3.org> wrote:
>
> On Wed, 15 Oct 2008, Raphaël Troncy wrote:
>
>> Hi Yves,
>>
>> Thanks for completing this Action Point. Hum, just to be sure I
>> understand, can you please clarify:
>>
>>> So it means that http://example.com/what;date=1234/test is different from
>>> http://example.com/what;date=5678/test , pretty much like when using '?' as
>>> opposed to '#'.
>>
>> You said that http://example.com/what;date=1234/test is different from
>> http://example.com/what;date=5678/test. What is this difference?
>
> because when you are resolving the URI server side, what;date=1234 is a
> different element than what;date=5678. (like different archives, for
> examples)

They are regarded as different resources.


>> You said also that http://example.com/what?date=1234/test is similarly
>> different from http://example.com/what?date=5678/test. Correct?
>
> Yes (but in that case the last / should be escaped). Unlike above, the leaf
> is 'what' with the parameter date=5678%2Ftest or date=1234%2Ftest, instead
> of 'test' (and two different 'test' as the container is different, in the
> first example).

And they are still regarded as different resources.


>> Finally, you said that http://example.com/what#date=1234/test (is it a
>> valid URI?) is not different than http://example.com/what#date=5678/test ?
>> Because they point to the same resource?
>
> In that case, the resource is the same http://example.com/what, you are just
> addressing different fragments of the same resource, and not two different
> resources, like in the first two examples.

Because the # is not valid anywhere beyond the user agent - certainly
web proxies and origin servers are supposed to drop them if they ever
get there.

Cheers,
Silvia.

Received on Wednesday, 15 October 2008 10:35:49 UTC