RE: URIs / URLs

Yes, this makes sense.  

You cannot necessarily rely on a URI alone, but must evaluate it in some
context.  

Does this imply a rdfs:Class of identifier that includes context with the
URI would be beneficial?  RDF statements can then be made about instances of
that class, which in turn identify a resource with a URI within some
context.

-----Original Message-----
From: Sean B. Palmer [mailto:sean@mysterylights.com]
Sent: 12 April 2001 16:36
To: Lee Jonas; 'Charles McCathieNevile'
Cc: 'Aaron Swartz'; RDF Interest
Subject: Re: URIs / URLs


> it would be inappropriate to use mailto:charles@w3.org
> unless you were making assertions about the owner of
> the charles mailbox at W3C.

Actually, it would be quite sensible to use that URI to identify
"Charles McCathieNevile" because the SW depends on contxtualization as
well as universality. In a closed world system, it doesn't matter all
that mcuh what identifier you use for anything, and even on an open
(webized) scale, it doesn't matter too much because of the concept of
equivalence. For example, say that in the year 2010, Chaals has the
mailbox URI mailto:charles@mccathienevile.info We could say something
like:-

   [ :- <mailto:charles@w3.org>; dc:date "2001" ] =
   [ :- <mailto:charles@mccathienevile.info>; dc:date "2010" ] .

Ah, the Semantic Web :-) Of course, anything that uses the w3.org or
the mccathienevile.info URIs would itself have to contain the date of
issue.

I remain not all that bothered.

--
Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
:Sean :hasHomepage <http://purl.org/net/sbp/> .

Received on Thursday, 12 April 2001 11:48:32 UTC