Lists Home |
Date Index |
Repeat after me; URLs are nothing more than URIs with a resolution
mechanism. http://www.markbaker.ca is as much an URN or URL as
urn:markbaker (once I register it with Netsol, er, I mean IANA 8-).
It's just that the former is well deployed, but the latter is not.
So the choice is not between URLs and URNs, it's between the devil you
know (deployed HTTP URI scheme resolution), and the devil you don't
If you expect URN namespace registration to eventually be any less of a
quagmire than ICANN, or any more "location independant" than DNS, then
I've got a, well, quagmire to sell you. 8-)
No Mark, a URL is a locator and you may use it as a "name" with the
inherent problem of location dependence. Hence, if you move the resource
its name is changing which counter the goal to provide an "invariant"
identification scheme to a resource. However, you can say that being a
practical mind living in a frozen world (i.e. the web which is about the
same as it was 5 or 6 years ago, just bigger) You use what's already
there and accept all the inconvenience attached to it. In that case, I
agree, this is adaptation to reality. Said that, a rose is a rose is a
rose. A location is a location is a location and a name is a name is a
name. I finally agree with my ET that he'll have to wait until human
beings are more evolved enough to make this distinction. But in practice
I agree with you, in a frozen world we have to adapt with what's already
there as long as long as we don't mix things. When I use my bike because
its more convenient during times of staled traffic I do not call my bike
a car :-).