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

Hallo Peter,

i'll create an updated version following Appendix a of RC 8141 today.

Best regards
Günter

-----Ursprüngliche Nachricht-----
Von: Peter Saint-Andre <[email protected]>
Gesendet: Montag, 13. Mai 2024 20:52
An: Steindl, Günter (DI FA CTR ICO) <[email protected]>; [email protected]
Betreff: Re: [urn] Updated request: URN Namespace Registration Request for "PNO"

Hallo Guenter,

Overall the details look fine to me. If you would be so kind, please format the registration request in accordance with Appendix A of RFC 8141. [1] This will expedite the process of registration with IANA.

Kind Regards,

Peter

[1] https://www.rfc-editor.org/rfc/rfc8141#appendix-A

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
>
> *5. Additional Information*
>
> These (PNO) / (PI) specified URNs will be part of next editions of
> e.g., "PROFINET" as part of the IEC61158/IEC61784 at the IEC.
>
> *6. Contact Information:*
>
>   * Organization: PROFIBUS Nutzerorganisation e.V. (PNO)
>   * Email: [email protected] <mailto:[email protected]>
>   * Phone: +49 721 986197 0
>
> We believe that the registration of the "pno" namespace will
> facilitate the management and identification of resources associated with PNO.
>
> Please let us know if any additional information or documentation is
> required for the registration process.
>
> Thank you for your attention to this matter.
>
> Sincerely,
>
> Günter Steindl
>
> Committee B "PROFINET" Chair
>
> PROFIBUS Nutzerorganisation e.V. (PNO)
>
> With best regards,
> Guenter Steindl
>
> Siemens AG
> Digital Industries
> Factory Automation
> Industrial Communications
> DI FA CTR ICO
> Werner-von-Siemens-Str. 50
> 92224 Amberg, Germany
> Mobile: +49 (173) 9137406
> mailto:[email protected]
> <mailto:[email protected]>
> http://www.t/
> witter.com%2Fsiemens&data=05%7C02%7Cguenter.steindl%40siemens.com%7C2d
> 12d0654e8f4cd040f308dc737dd2e6%7C38ae3bcd95794fd4addab42e1495d55a%7C1%
> 7C0%7C638512231488177433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=kIGwa
> gj1sFWaxPROmz9GurjNsJiK%2Be7JxoYXbVywzKM%3D&reserved=0
> <http://www/.
> twitter.com%2Fsiemens&data=05%7C02%7Cguenter.steindl%40siemens.com%7C2
> d12d0654e8f4cd040f308dc737dd2e6%7C38ae3bcd95794fd4addab42e1495d55a%7C1
> %7C0%7C638512231488184248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi
> LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JsMo
> tZrYHWeY%2FJrT13Wamf6Rp8iWH08lS1cgujf%2B1Cw%3D&reserved=0>
> http://www.siemens.com/ <http://www.siemens.com/>
> Logo
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim
> Hagemann Snabe; Managing Board: Roland Busch, Chairman, President and
> Chief Executive Officer; Cedrik Neike, Matthias Rebellius, Ralf P.
> Thomas, Judith Wiese; Registered offices: Berlin and Munich, Germany;
> Commercial registries: Berlin-Charlottenburg, HRB 12300, Munich, HRB
> 6684; WEEE-Reg.-No. DE 23691322
>
>
> _______________________________________________
> urn mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

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