¥Using the
same URI to refer to me and to access my website
isnÕt even an example of overloading. It only becomes that if we assume that the
name which accesses the website therefore also refers to the website.
But why do we make this assumption? There is nothing in the HTTP specs
which seems to have anything particularly to do with reference.
¥
¥A
suggestion: names (IRIs) refer to accessible things just when the thing is
actually assigned that name; and assigning is done
only by an explicit naming convention, by pointing to the object and asserting, this is called
<name>. Unlike reference by description, this kind of naming can
be completely unambiguous.
¥
¥There are
two ways to point to an accessible object: by being it, or by
using a URI which accesses it. (Access is a kind of Ôpointing
gestureÕ.) The two kinds of naming convention this makes possible are similar
respectively to wearing a name badge, and to having someone point at you and say, ÒI will call
you SpidermanÓ.