Re: What if an URI also is a URL

Sorry for re-opening this months later, it's just that

> The moment a server returns 200 OK for a request to the URI, it is  
> saying it identifies a document.
> You can't use the same URI for yourself.

puzzles me. It brings the answer to most of my problems with URIs in a
surprisingly short statement, but does so with some amazing
consequences.

Could anyone pls. verify my following assumptions:

a) http://www.some.org refers to the one document returned by the
request and should not be used to refer to the website as such (=the
collections of documents hosted at some.org)

b) The same way http://www.acme.com is not a good URI to refer to ACME,
the company, http://flickr.com is not a good URI to refer to flickr, the
service/community. It would only refer to the document retrieved from
there, the one that tells me to sign up or take a tour etc.

c) Consequently, if I want to make a reference to my weblog (meaning the
thing as such, a collection of all posts, pictures, the services offered
etc.), I'd better not use http://oskar.twoday.net as this would only
refer to one single HTML-document. In particular, the document served at
http://oskar.twoday.net might have been dc:created yesterday, while the
weblog as such started 2003.
I'd have to make up something like http://oskar.twoday.net/id/thisblog
and maybe state somewhere that http://oskar.twoday.net/id/thisblog has
an indexDocument http://oskar.twoday.net 

d) http://www.some.org can not be used to make statements about the URI
as such, like "contains 3 vowels" or "is valid according to some spec".


Is the above correct? If so, it could well be that I'm eventually
beginning to understand the URI-thing which kept me from using RDF all
the time...

Thank you for your support
Oskar

Received on Sunday, 26 August 2007 16:47:07 UTC