Re: a URI is a name (tel uri scheme and VCARD RDF)

I followed the link at the bottom of this email, and read Sean B. Palmer's interesting essay on URIs.  It's the first time I have ever bothered to read anything about URIs.  In one sense, that has been a great advantage -- I haven't been distracted by the details of how URIs are structured, or the ongoing discussions of whether a URI points to a document, or a graph, etc.

So, I can sit back, with a somewhat detached perspective, and observe that a URI is simply a name for something, and the meaning of a URI is the something that the name refers to.

For example, if we want to talk about Linus Torvalds in the context of URIs & RDFS, we might have three different somethings that we need three different names for:

    Linus Torvalds the person
    a document that contains RDFS statements that describe facts about Linus Torvalds
    a graph that contains nodes and links that describe facts about Linus Torvalds

My impression, based on a few RDF-interest emails, is that much confusion has been generated by trying to use one URI when three URIs are required.  It may be possible to adopt some conventions to allow one URI to be simply mapped to three URIs.
But the fact remains -- three URIs are required.
============ 
Dick McCullough 
knowledge := man do identify od existent done
knowledge haspart list of proposition

  ----- Original Message ----- 
  From: Doug Ransom 
  To: www-rdf-interest@w3.org 
  Sent: Sunday, November 24, 2002 8:43 AM
  Subject: tel uri scheme and VCARD RDF



  In http://www.w3.org/TR/vcard-rdf the following example is shown:

  <vCard:TEL rdf:parseType="Resource">
       <rdf:value> +61 7 555 5555 </rdf:value>
       <rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#work"/>
       <rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#voice"/>
      </vCard:TEL>


  I would suggest the value of a telephone number be a telephone number URI:

  http://infomesh.net/2001/09/urischemes/