Re: TR: URN Registration for UIC

SARFATTI David <[email protected]>
Newsgroups gmane.ietf.urn
Message-ID <PAXP189MB1630F9E7BBD465D3994C66BDDF52A@PAXP189MB1630.EURP189.PROD.OUTLOOK.COM>
Dear Sir,
Please find attached the form revised and completed.

Please find below answers from our IT expert Clemens Gantert.
I stay at your disposal for any complementary information and thank you very much for our UIC URN registration.
Best regards,
David 


Should "CGI" be "UIC"?   --> Yes, this should be UIC.

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.
--> [email protected] 

RFC 2141 has been replaced by RFC 8141, so these references should be updated.  (I don't think that significantly affects your
specification.)
--> this is a proposal to replace the last paragraph on page 1 (Declaration of structure:)  of the request as the form has changed:

Old:
      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:

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

      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".


-----Message d'origine-----
De : Peter Saint-Andre <[email protected]> 
Envoyé : samedi 27 mai 2023 14:40
À : Dale R. Worley <[email protected]>; SARFATTI David <[email protected]>
Cc : [email protected]; GANTERT Clemens <[email protected]>
Objet : Re: [urn] TR: URN Registration for UIC

On 5/24/23 11:45 AM, Dale R. Worley wrote:
> 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,

I too think it is reasonable to register this namespace and agree with Dale's comments. Here are additional suggestions...

(1) The registration uses the template from RFC 2141. Please use the more modern template (see Appendix A of RFC 8141).

(2) When you do so, please pay special attention to the privacy and security considerations.

(3) Pointers to relevant documentation on the UIC website would also be helpful.

Best Regards,

Peter

_______________________________________________
urn mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/urn
URN OSDM Registration form 06062023.docx (application/vnd.openxmlformats-officedocument.wordprocessingml.document, 65.6 KB) - not displayed
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.