> Applying RFC 2141 is fine from my point of view. As such I need to
> update the examples I provided earlier to reflect marlin and phoenix
> as subdomains of the avalon domain.
Is that what you want to do? There is no sub-domain notion within RFC 2141.
The format of a URN is "urn:" <NID> ":" <NSS>. NID is Namespace IDentifier,
and NSS is Namspace Specific String. One example might be:
urn:avalon:home.work
where "urn:" is required, avalon is the NID and home.work is the NSS. In
all of your examples, the NID was apache, and everything else was the NSS.
> update merlin specific keys to be RFC 2141 based on
> a *apache:avalon:merlin* domain
If "domain" is supposed to be NID, that would not be valid. The ':'
character is not valid within an NID, and is valid within the NSS. So your
string would be interpreted as having an NID of apache, with avalon:merlin:
being part of the NSS, which is probably not what you're going to want
internally when you process the NSS. Alternatively, you could use
apache-avalon-merlin as an NID.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
