W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: ISSUE-81 (resource vs representation)

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Wed, 7 Oct 2009 14:14:31 -0400
Message-ID: <7c2a12e20910071114o1506e1f0m70e4c292fe2bf34a@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Larry Masinter <masinter@adobe.com>, Ian Hickson <ian@hixie.ch>, HTMLWG WG <public-html@w3.org>
On Wed, Oct 7, 2009 at 11:24 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> It depends on the applied comparison function.
> For instance...
> <http://www.w3.org/>
> <HTTP://www.w3.org/>
> <http://www.w3.org:80/>
> all identify the same resource.
> Now you could claim that these URIs are indeed the same, and that also
> depends on which type of comparison you choose (see
> <http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.6.2>).

Let's say that two URLs are the same if they generate the exact same
request, so that the server can't tell the difference (and therefore
cannot possibly serve different responses).

> But of course servers can expose the same resource under many more names
> that differ just in the path or query component (for instance, consider a
> server that servers files from the file system, and the file system supports
> hard links). In those cases the same resource will appear with different
> path values.

Is there any practical difference between a case where two URLs
represent the same resource, and a case where two URLs represent
different resources that happen to have identical representations in
more or less every circumstance?  (But perhaps not quite *every*
circumstance, maybe due to hitting internal length limits somewhere,
or whatever -- so they can't be the *same* resource.)
Received on Wednesday, 7 October 2009 18:15:07 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:00 UTC