Re: TR: URN Registration for UIC

[email protected] (Dale R. Worley)
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
SARFATTI David <[email protected]> writes:
> Please find attached our subscription form to obtain a Uniform
> Resource Name (URN) Namespace for the International Union of Railways
> (UIC).
> I remain at your disposal for any complementary information,

I approve of your registration, although I request you consider the
following editorial changes:

The title of the document is

    A Uniform Resource Name (URN) Namespace for the International
    Union of Railways (CGI)

Should "CGI" be "UIC"?

   Declared registrant of the namespace:

      Name:           Union International de Chemin de Fer
      Address:        16, rue Jean Rey 75015 Paris, France
      Contact:        David Sarfatti 
                      E-mail: [email protected]

You might want to consider providing a "role address" here rather than
an individual address as the address should remain valid over a period
of many years.

      The Namespace Specific String (NSS) of all URNs that use the "uic"
      NID has the following structure:

      urn:uic:{UICResource}:{ResourceSpecificString}

      where the "UICResource" is a US-ASCII string that conforms to the
      URN syntax requirements [RFC2141] and defines a specific class of
      resource type.  Each resource type has a specific labeling scheme
      that is covered by "ResourceSpecificString", which also conforms
      to the naming requirements of [RFC2141].

RFC 2141 has been replaced by RFC 8141, so these references should be
updated.  (I don't think that significantly affects your
specification.)

I think you want to clarify here that "UICResource" specifies the
"resource type", and make clearer the requirements on
ResourceSpecificString.  Perhaps:

      where the "UICResource" is a US-ASCII string that specifies the
      resource class and "ResourceSpecificString" specifies the
      individual resource, such that the entire string conforms to the
      URN syntax requirements [RFC8141].  Each resource type has a
      specific labeling scheme for "ResourceSpecificString".

Dale
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.