> sounds good, +1.
> some notes on implications:
> - "Further, the Namespace Identifier is case insensitive"
Correct. The "urn:" prefix and the NID are case insensitive. It is up to
the context specified by the NID to determine if case is sensitive.
> - allowed in the namespace identifier are alphanumerics and the hyphen,
> not dots, so "avalon.phoenix:blah" is not allowed but
> "avalon:phoenix:blah" or "avalon:phoenix.blah" or "avalon-phoenix:blah"
Correct. The resulting breakdowns from your examples are:
NID NSS
avalon phoenix:blah
avalon phoenix.blah
avalon-phoenix blah
I consider the third example would be the best pattern for a Phoenix
specific identifier. The avalon namespace should not know about container
specific keys.
> anyone know of a URNUtils class or something like that?
Check Apache SOAP/Axis for an implementation. SOAP uses RFC 2141.
By the way, the "urn:" prefix, at a cost of four characters (a) provides a
quick validation for the parser, and (b) informs the reader that the
identifier follows RFC 2141. And it is required by the RFC.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
