[
Lists Home |
Date Index |
Thread Index
]
I agree with that. But your use and the use
of your neighbor may be in conflict. You say
your use governs, and as far as the spec says,
it does. But practice is, the browser turns
it blue and makes it clickable.
I believe that it is good practice when using a URL as a URI that one
put something where it points for the sake of
politeness, or to use URN and be explicit in
that document (a URN only has one semantic, to
name, so I consider it a document) exactly
what is meant. The problem comes of overloading
and leaving only contextual clues as to intent.
If it is intended only to name: name it.
If it is a name with an addressable referent, address it.
If it is or can be both, address it (leave a RDDL or
RDF file there).
Leaving it dangling because in the future one might
want to change it is somewhat like letting your
2 year old child into the neighbor's yard without diapers
because you don't want to change them soon;
or the neighbor letting the Rottweiler into yours because
he may want to walk the dog later.
Avoid the conflict. Leash the puppies.
This should be common practice: a constantly
evolving protocol for getting along with the rest
of the people in the neighborhood.
len
From: Paul Prescod [mailto:paul@prescod.net]
In my world-view all URLs are URIs. Sometimes we use them as identifiers
and sometimes as locations. I also believe that URIs that can be used as
both are better than URIs that can be used as only one or the other.
HTTP URIs have that property.
|
