Re: [URN] Re: Relative URLs and URNs

Daniel LaLiberte wrote:
> 
>  > Thus spoke Omar Syed:
>  > > 2. clients must treat <NSS> as an opaque string (i.e. do not interperet)
>  >
> Ron Daniel, Jr. writes:
>  > I think assumption 2 is in error. Clients that know the structure of
>  > a name in a particular namespace are likely to manipulate it.
> 
> I agree.  Clients, of course, can do whatever they want (whatever they
> can get away with) anyway, but they have to be able to interpret the
> structure of an identifier in order to do as much processing of it on
> their own as they can.  Forcing clients (if that were possible) to
> always consult a remote server to process the whole identifier is a
> sure way to make the system unscalable.

To resolve a URN to a location, resource or citation, a client
always needs to consult a remote resolver and pass it the
complete URN or partially processed URN.  Is this not always true?

Omar