W3C home > Mailing lists > Public > www-rdf-interest@w3.org > August 2001

Re: [www-rdf-interest] <none>

From: Murray Altheim <murray.altheim@sun.com>
Date: Tue, 28 Aug 2001 11:08:25 -0700
Message-ID: <3B8BDE19.5AD7105B@sun.com>
To: Seth Russell <seth@robustai.net>
CC: cg@cs.uah.edu, RDF-IG <www-rdf-interest@w3.org>
Seth Russell wrote:
> From: "Murray Altheim" <murray.altheim@sun.com>
> > Ah, but there's where I won't follow your argument. My example was simply
> > an example in a discussion *here*, which is why the URI didn't dereference
> > to anything. You seem to deliberately ignore the scenario I'd set up that
> > stated that the URI *did* dereference to an XML Conceptual Graph document.
> I though if you could dereference a URI, then it was a URL ... but maybe I
> got confused.  If you can make the URI into a URL, then I agree you've
> kindOf solved the problem.  But then we have that other problem:  does the
> URL identify the bits returned when the URL is accessed, or identify the
> ~thing described by~ those bits.

Perhaps you are misunderstanding the terminology. Uniform Resource
Identifier (URI) is a term that includes both Uniform Resource Locator
(URL) and Uniform Resource Name (URN). I am only following the somewhat
common usage as found in specifications, but perhaps I should be more 
specific: absent a resolution service I mean "URL." Some of us (apparently
the entire standards community) have been belabouring for years under the 
general assumption that URNs would someday become more common. 

Sorry for the confusion.


Murray Altheim                         <mailto:murray.altheim&#x40;sun.com>
XML Technology Center
Sun Microsystems, Inc., MS MPK17-102, 1601 Willow Rd., Menlo Park, CA 94025

      In the evening
      The rice leaves in the garden
      Rustle in the autumn wind
      That blows through my reed hut.  -- Minamoto no Tsunenobu
Received on Tuesday, 28 August 2001 14:07:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:32 UTC