RE: Can "http://danbri.org" and "http://danbri.org/" URIs represent different things?

>>>> Could http://danbri.org be a URI for "me the person", and
>>>> http://danbri.org/
>>>> be a document about me (and also serve as my OpenID)?

Allowing http://danbri.org and http://danbri.org/ to "represent" 
different things would be a bad design choice. Don't do it.

Perhaps there isn't an audit trail in RFC 2616 that doesn't
tell you that you shouldn't do something, but that doesn't
mean that it isn't a bad idea.

RFC 2616 was not written with the "semantic web" in mind,
wasn't intended to solve the "semantic web"'s design problems
for how to use URIs to represent abstract concepts, and
so trying to do a close reading of the words (at least
some of which were written by me) is -- I can claim --
a futile exercise.
>>>> As I understand HTTP, any client must request something, so the former
isn't
>>>> directly de-referencable. The client has to decide to ask for / from
>>>> danbri.org instead. But they're still different URIs, aren't they?


The mapping of "http" URIs to actions of the HTTP protocol is defined
in the HTTP spec, which indicates that, as far as the action of
identifying HTTP protocol interactions go (which is as far as
it goes).

http://danbri.org and http://danbri.org/  are equivalent.

Any problems with disambiguating "denotation" are problems of
the denotation system.


Larry

Received on Friday, 3 July 2009 02:56:27 UTC