[urn] Re: Updated request: URN Namespace Registration Request for "PNO"

["Steindl, Guenter" <[e-mail]>]

Hi Dale,

i created a revised request including all received feedback.

This update was sent out yesterday - switching the format of the request into the Appendix A of RFC 8141.

It updates the examples too.

Regards
Günter

-----Ursprüngliche Nachricht-----
Von: Dale R. Worley <[e-mail]> 
Gesendet: Mittwoch, 15. Mai 2024 03:43
An: Peter Saint-Andre <[e-mail]>
Cc: Steindl, Günter (DI FA CTR ICO) <[e-mail]>; [e-mail]
Betreff: Re: [urn] Re: Updated request: URN Namespace Registration Request for "PNO"

For some reason, I didn't get this message from the mailing list.  So I'm quoting it from Peter's reply.  On the whole it looks fine, but there's one detail that needs to be fixed:

> On 5/13/24 6:55 AM, Steindl, Guenter wrote:
>> Dear IETF / IANA,
>> 
>> we would like to request the registration of a URN namespace with the 
>> following details:
>> 
>> *1. Namespace Identifier (NID):*
>> 
>> The PROFIBUS Nutzerorganisation e.V. (PNO) [PNO] is an international 
>> association that promotes and supports the development of PROFIBUS 
>> and PROFINET, industrial communication protocols used in automation technology.
>> 
>> We provide standards, certification programs, and resources to ensure 
>> product interoperability and reliability, fostering collaboration 
>> among manufacturers, system integrators, and end-users.
>> 
>> The Namespace Identifier (NID) of all URNs that are defined by the PNO is:
>> 
>>   * NID: pno
>> 
>> *2. Intended Purpose:*
>> 
>> The "pno" namespace is intended to provide a unique identifier for 
>> resources related to our organization PNO.
>> 
>> These resources may include documents, software artifacts, and other 
>> digital assets produced or managed by PNO.
>> 
>> *3. Guidelines for URN Structure:*
>> 
>> URNs within the "pno" namespace will follow the following structure:
>> 
>>   * urn:pno:{PNOresource}:{ResourceSpecificString}
>> 
>> where "PNOresource" is a US-ASCII string that conforms to the URN 
>> syntax requirements [RFC8141] 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 [RFC8141].
>> 
>> PNO maintains a registration authority, the PNO Registration 
>> Authority (PNO CO), that will manage the assignment of 
>> "PNOresource“, and the specific registration values assigned for each resource class.
>> 
>> *4. Example:*
>> 
>> The following examples are representative URNs that could be assigned 
>> by the PNO CO.
>> 
>>   * urn:pno:profinet:yang
>>   * urn:pno:foobar

Note that the example "urn:pno:foobar" doesn't conform to the syntax in section 3.  In particular, the syntax requires at least 3 colons in any PNO URN, whereas this example has only two.  Perhaps this is a typo for "urn:pno:foo:bar", which does conform to the syntax?

Dale