> apache-avalon-merlin:
> avalon-merlin:
> merlin:
Any of the above patterns is fine with me. I imagine a two-stage registry
where the NID is mapped to an NID-specific registry, which then maps the NSS
to the identified object. Two stages are used because the second stage is
permitted to interpret the NSS however it wants. The NSS is not strictly a
lookup key.
Which actually lends strength to my earlier argument that
urn:avalon:phoenix-blah is a bad thing to do. It requires the Avalon
namespace to interpret the NSS on behalf of Phoenix. So that pretty much
settles the proper usage pattern in my mind.
Agreed?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
