W3C home > Mailing lists > Public > www-tag@w3.org > August 2002

RE: [httpRange-14] What do HTTP URIs Identify?

From: Joshua Allen <joshuaa@microsoft.com>
Date: Thu, 8 Aug 2002 13:39:03 -0700
Message-ID: <4F4182C71C1FDD4BA0937A7EB7B8B4C10602970E@red-msg-08.redmond.corp.microsoft.com>
To: "Jonathan Borden" <jonathan@openhealth.org>, "Bullard, Claude L (Len)" <clbullar@ingr.com>, "Bill de hOra" <dehora@eircom.net>, "Tim Berners-Lee" <timbl@w3.org>
Cc: <www-tag@w3.org>

> "The meaning of a URI(ref) as intended by its authority is defined by
the
> set of assertions obtained when the URI is referenced.

Do you mean "dereferenced"?

> When the media type of such a representation is: application/rdf+xml,
then
> the meaning of the represented URI is given by the graph as per the
RDF
> model theory."

While this is one *possible* scenario that could occur, there are many
other ways that meaning can be associated with a URI.  It's debatable
whether this particular approach ever stands a chance of succeeding.

I strongly recommend that TAG avoid endorsing any particular approach to
associating meaning with URIs.  

I suggest sticking with the simple affirmation that URIs *do* have
meaning.  

Assignation of meaning to symbols is a complex and fluid social process
(in which ownership of a DNS server can play a big part, of course).
The Web Architecture doesn't need to codify this process, and risks
looking foolish by trying.
Received on Thursday, 8 August 2002 16:39:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:55:42 GMT