W3C home > Mailing lists > Public > www-tag@w3.org > August 2002

RE: [httpRange-14] What do HTTP URIs Identify?

From: Graham Klyne <GK@ninebynine.org>
Date: Thu, 01 Aug 2002 22:09:30 +0100
Message-Id: <5.1.0.14.2.20020801215622.038c2270@127.0.0.1>
To: Mike Dierken <mike@dataconcert.com>
Cc: www-tag@w3.org

At 11:59 AM 8/1/02 -0700, Mike Dierken wrote:


> > >
> > > Example:
> > >
> >     <http://example.org/myCar> ex:colour ex:Red .
> >
> > Suppose that I already know that ex:colour and ex:Red are to be
>interpreted
> > as describing the colour of the subject resource in the way that we (as
> > English speaking people) might expect.  Am I to conclude that:
> >     the web page at <http://example.org/myCar> is substantially red? Or
> >     a car described by the web page at <http://example.org/myCar> is
> > substantially red?
>
>Sorry to butt in again, but for me this statement is incorrect.
> >     the web page at <http://example.org/myCar> is substantially red?
>because there is no page /at/ <http://example.org/myCar>

(I assume you appreciate I was speaking hypothetically.)

I used the term 'page at' here as a shorthand for 'document for which one 
obtains a representation by dereferencing the URI'.

Roy's comments point to a flaw in this...

Maybe colour wasn't such a good example, but I think could adapt the 
idea.  Suppose I designed and built the car.  Then I authored a document 
describing the car, and posted that document on the web.  So we might have:

   <http://example.org/myCar> ex:madeBy ex:Me .

I think that this assertion could reasonably be an enduring truth, whether 
<http://example.org/myCar> identifies the document or the car it describes.

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
Received on Thursday, 1 August 2002 16:52:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:33 UTC