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

RE: silly question about rdf:about

From: Bill de hÓra <dehora@eircom.net>
Date: Mon, 8 Apr 2002 11:59:05 +0100
To: "'Uche Ogbuji'" <uche.ogbuji@fourthought.com>, "'Nikita Ogievetsky'" <nogievet@cogx.com>
Cc: "'Seth Russell'" <seth@robustai.net>, <www-rdf-interest@w3.org>, "'Sandro Hawke'" <sandro@w3.org>
Message-ID: <000d01c1deec$678b11e0$887ba8c0@mitchum>
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> -----Original Message-----
> From: www-rdf-interest-request@w3.org 
> [mailto:www-rdf-interest-request@w3.org] On Behalf Of Uche Ogbuji
>
> It shouldn't leave least bit puzzled.  
> It [http://uche.ogbuji.net] is obviously 
> talking aboout the Web 
> site, not the person.
>
> [...]
>
> But I don't see the confusion.  RFC 1738, which governs the URI 
> http://uche.ogbuji.net makes it clear that this URI 
> locates/identifies the 
> document that is retrieved using HTTP and that address.  Why 
> would anyone 
> thing it represents a person?

I would think:

http://uche.ogbuji.net :characteristics :very-interesting

is talking about a resource. Which one? Maybe >I'm< thick but I
have no idea.

[Which one? That one. Oh, right, _that_ one].

Now, I for one, wouldn't have got the resource known as the Uche
mixed up with the resource known as the website here. I would mix
up the resource know as the website with the resource known as the
page at that URL.

If the resource is obviously the website itself, must a HTTP GET on
that URI obviously return the representation of the website, i.e.
the document fetched is a representation of the website? And here's
me thinking it's Uche's homepage or something probably redirected
via a front controller or a config file for the server; oh well.
Are we allowed to point at different resources, or treat the URIs
differently depending on whether we're reasoning with RDF
applications or dereferencing with HTTP ones? HTTP applications
make up a big chunk of Web machinery, it would be good to know.
Saying that :characteristics is bound to the resource known as
website and not the resource known as web page, isn't immediately
obvious to me. 

Though it's much less obvious to me that :characteristics is bound
to the resource known as Uche (maybe that's saying anything about
anything for you), is there a really a constraint somewhere saying
it cannot be used for that? Saying 'obviously', makes me think
'can't' be the case rather than 'shouldn't' be the case. Possibly
I'm missing something fundamental about RDF, but if you can confuse
two resources under a single name, why not three, or more?  

Bill de hÓra

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPLF39uaWiFwg2CH4EQJEnACgrrRDlHRFNMZrwmGlE6Su/XEpNygAoMTX
5PdFLa60tjNVBb5g8xJZb1cn
=mTqg
-----END PGP SIGNATURE-----
Received on Monday, 8 April 2002 07:05:19 GMT

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