[urn] Re: Request for registration of formal URN namespace "dnp"

Director - Stakeholder Engagement <[email protected]> writes:
> URN NAMESPACE REGISTRATION TEMPLATE
> Formal Namespace Identifier: dnp
> Submitted under Section 6.2 of RFC 8141 (Expert Review)

This is easily the best registration template I've seen.

I heartily approve of it, although I suggest one minor change.  The
syntax is given as:

>      NSS         = class ":" local-id [ ":" edition ]
>
>      class       = 2*24( lowalpha )
>
>      local-id    = id-start *62( id-char ) id-end
>      id-start    = ALPHA / DIGIT
>      id-char     = ALPHA / DIGIT / "-" / "."
>      id-end      = ALPHA / DIGIT
>
>      edition     = ver-form / date-form
>      ver-form    = "v" 1*3DIGIT [ "." 1*3DIGIT ]
>      date-form   = 4DIGIT "-" 2DIGIT "-" 2DIGIT
>
>      lowalpha    = %x61-7A     ; a-z

Taken literally, this means that the "class" must be composed of
lower-case letters.  But the section on equivalence says that lower case
and upper case are equivalent:

>    URN-equivalence. Two names are URN-equivalent if they are
>    URN-equivalent under Section 3.1 of RFC 8141 after additionally
>    applying ASCII case folding to the entire NSS. That is, the NSS
>    in this namespace is case-insensitive, so that
>
>      urn:dnp:standard:dnp-d.002:v1
>      urn:dnp:standard:DNP-D.002:v1
>      URN:DNP:STANDARD:DNP-D.002:V1

Taking the syntax description strictly, the "class" must be lower-case
(although the local-id may be mixed case), which means that the third
example is not a valid DNP URN.

I recommend replacing the "class" production with

>      class       = 2*24( ALPHA )

and eliminating the "lowalpha" production.

Dale

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]