W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2004

Re: URI: Name or Network Location?

From: Phil Dawes <pdawes@users.sourceforge.net>
Date: Wed, 21 Jan 2004 21:16:22 +0000
Message-ID: <16398.60454.926895.626564@gargle.gargle.HOWL>
To: Patrick Stickler <patrick.stickler@nokia.com>
Cc: "ext Sandro Hawke" <sandro@w3.org>, www-rdf-interest@w3.org, "Thomas B. Passin" <tpassin@comcast.net>, "ext Jeremy Carroll" <jjc@hplb.hpl.hp.com>

Hi Patrick,

Patrick Stickler writes: 
 > Per your view, most URIs do not denote web pages, images,
 > video streams, services, etc. but all denote "locations" and
 > if we ever want to describe all those web-accessible resources,
 > we need an entirely different set of URIs for them if we wish
 > to talk about them.

But surely the only reason this argument has weight is because there
is usually only 1 way of retrieving that web resource* - i.e. HTTP. 
Thus it becomes an attractive choice for naming it.

If the web hadn't turned out the way it has, and there were lots of
protocols vying on equal footing for supremacy, then the 'it's a name'
argument wouldn't seem so obvious. We would, as you say, probably have
a way of talking about the web resource itself, and a seperate way of
talking about the numerous ways of locating it.

The problem now is that we are attempting to use HTTP URIs to describe
abstract concepts and physical objects, and so the 'it's a name'
argument for HTTP URIs is suddenly non-obvious again. It seems to me
that the most obvious way of addressing this is to use a URI to denote
the thing (i.e. a name) and a seperate way of talking about the
numerous ways of locating information about it.



* or the representation of that resource
Received on Thursday, 22 January 2004 10:22:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:49 UTC