Re: URN Resolution Paths Considered Harmful


Let me add to your list of reasons that it is a bad idea for a
resolver name (or resolution service name) to be embedded in a URN.
There may well be (hopefully will be) more than one resolution service
available at any given time.  At any particular time (T) different
clients may prefer different such services for a variety of reasons
(correctness vs. cost, for example).  How can the name generator
possibly know the single "right" answer the resolution service to use
for all time, when at any given time more than one may be the right
answers for different clients?


Received on Tuesday, 27 June 1995 12:36:52 UTC