RE: Clarifying what a URL identifies (Four Uses of a URL)

> -----Original Message-----
> From: Michael Mealling [] 
> Sent: Tuesday, January 21, 2003 5:59 PM
> To: Dare Obasanjo
> Cc: Tim Bray; Sandro Hawke; David Booth;; Roy 
> T. Fielding; Dan Connolly
> There's an intended difference between how other people use 
> an identifier and how you, the entity with authority over 
> that identifier, intends it to be used. I can claim that 
> is actually an identifier for me 
> but since I'm not authoritative for it no one is going to 
> believe me....

On the Web you cannot control how people will use an identifier. A
Semantic Web that is as limited as you describe would be particularly
useless in my personal opinion since it means only authorities that own
a resource can make statements about it. I hope no one actually working
on making the Semantic Web a reality has such a limited view of it. 
> > > It's a formalism.  The Web Architecture has a formalism called a 
> > > "Resource" which is the one thing that corresponds to each URI.
> > 
> > This statement is meaningless and yet W3C TAG members keep 
> repeating it.
> > What is the one resource that the URI 
> ""
> > identifies? 
> The Resource that has that identifier. You can point to it, 
> it just is by virtue of the URI existing. Its a platonic 
> 'Resource'. It doesn't exist physically or virtually. It just 
> _is_. Things can claim to be representations of it, but 
> nothing can ever actually _be_ it.

This is circular reasoning which doesn't answer the question being asked
but pretends it doesn't exist. It may work fine to spout this answer
when designing a system for retrieving network addressable documents off
of remote  machines since it is primarily inconsequential to this
scenario but for knowledge representation this ambiguity is
unsatisfactory. Sandro has already done a good job of showing examples
of how this breaks down and the only counter examples I've seen are
either attempts to ignore the problem or point out that it works fine
for grabbing files of the network using HTTP. 

An expert is one who knows more and more about less and less until he
knows absolutely everything about nothing.                            

This posting is provided "AS IS" with no warranties, and confers no

Received on Tuesday, 21 January 2003 23:48:00 UTC