Re: Naming ports vs. naming documents

Hi Alex,

Alessandro Vernet wrote:
> 2) I am not convinced that reusing schemes is a good idea. I don't
> feel comfortable with a step producing a document for
> http://www.google.com/xhtml and then having another step read that URI
> and get something different than the Google home page. There is an
> semantic attached to the http scheme, and an expectation of what XML
> document is returned when reading http://www.google.com/xhtml. This is
> discussed with a suggested solution on
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=3113#c14

The web architecture Rec says [1]:

   "Although many URI schemes (§2.4) are named after protocols, this does
    not imply that use of such a URI will necessarily result in access to
    the resource via the named protocol. Even when an agent uses a URI to
    retrieve a representation, that access might be through gateways,
    proxies, caches, and name resolution services that are independent of
    the protocol associated with the scheme name."

I think it's absolutely fine to use an HTTP URI to refer to a document
that is actually retrieved via a resource manager: the URI is just an
identifier for the resource.

Cheers,

Jeni

[1] http://www.w3.org/TR/webarch/#dereference-uri
-- 
Jeni Tennison
http://www.jenitennison.com

Received on Wednesday, 3 May 2006 10:01:15 UTC