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

Re: URIs / URLs

From: Lee Jonas <ljonas@acm.org>
Date: Fri, 13 Apr 2001 06:48:23 +0100
To: <www-rdf-interest@w3.org>, <aswartz@swartzfam.com>
Message-ID: <PJEHIGCEAMAHEAPOOFBEIEJCCBAA.ljonas@acm.org>
Aaron Swartz (aswartz@swartzfam.com) wrote:

>Lee Jonas <lee.jonas@cakehouse.co.uk> wrote:
[snip]

>> Taking 'http://example.edu/~champin/' to identify "the person named
Champin
>> currently enrolled at Example University" as you said above implies that
>> URLs do not identify these resources through representations, but
identify
>> mappings-to-resources through representations instead.  This would have
very
>> serious ramifications for RDF.
>
>I don't follow the difference between identifying resources through
>representations and identifying mappings-to-resources. Could you clarify
the
>difference? Fundamentally, the fact is that the resource represented by a
>URI should not change, and in the majority of cases, it does not.
>Unfortunately many times the resource represented is not made clear.
>
>(I'd also like to make clear that these issues are vague, and not clarified
>by any standard, to my knowledge. These are merely my views and
>interpretations.)

It seems that there is some notion of "absolute resource specifiers", e.g. a
specific person; and "relative resource specifiers", e.g. the person with a
login of 'champin' at Example University.  I was trying to portray that (in
the absense of statements from the publisher of the URI) it is safer to
assume URLs represent the latter.

>--
>[ Aaron Swartz | me@aaronsw.com | http://www.aaronsw.com ]

regards

Lee
Received on Friday, 13 April 2001 01:46:18 GMT

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