Re: [urn] NEW NAMESPACE REGISTRATION: KNX

[Ted Hardie <[e-mail]>]

I apologize, the formatting below came out badly.  Somehow my attempt to
provide a link to RFC 8141 resulted only in it being named on a single line
above the text; that seems quite odd, and I am sorry for any confusion that
may cause.

regards,

Ted Hardie

On Wed, Aug 30, 2023 at 4:21 PM Ted Hardie <[e-mail]> wrote:

> Hi Michael,
>
> RFC 8141.
>
>
> I retrieved the document you suggested.  First, you probably want to
> update the reference within it to RFC 8141 and you probably should review
> in particular section 4.3, which discusses using relative references with
> URNs.  Your document discusses "relative URNs" in a way that I don't think
> quite matches the RFC 8141 approach.  You may also wish to review Appendix
> B, which highlights changes from RFC 2141.
>
> The document also does not appear to have a definition of the
> namespace-specific identifiers.  It specifies that the NID would be knx,
> but does not seem to provide anything else.  Is there a different document
> which describes their production?
>
> regards,
>
> Ted Hardie
>
> On Wed, Aug 30, 2023 at 3:58 PM Michael Critchfield <
> [e-mail]> wrote:
>
>> Dear URN Team,
>>
>> As KNX Association cvba, we would like to register the following
>> Namespace from our KNX IoT Point API Specification with you for listing in Uniform
>> Resource Names (URN) Namespaces (iana.org)
>> <https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml>
>>
>>
>>
>> Reference is our KNX IoT Point API Specification available on
>> https://schema.knx.org.
>>
>> Specifically, the KNX IoT Point API Specification is found under this
>> link https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download.
>>
>>
>>
>>    - Namespace Identifier:  knx (example „urn:knx:dpa“)
>>    - Version:  1
>>    - Date:  2023-08-30
>>    - Registrant:  KNX Association cvba, De Kleetlaan 5, B-1831
>>    Brussels-Diegem, Belgium
>>       - Joost Demarest [e-mail]
>>    - Purpose:  KNX IoT Point API, as specified on https://schema.knx.org
>>    (specifically
>>    https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download) and future
>>    EN50090-4-4.
>>    - Syntax: urn:knx:<NSS> where the syntax of "<NSS>" is specified in
>>    Section 2.2 of the URN Syntax requirements [RFC2141].
>>    - Assignment: Assignment done by KNX Association through KNX
>>    Specifications.
>>    - Security and Privacy:
>>       - There are no additional security considerations other than those
>>       normally associated with the use and resolution of URNs in general, which
>>       are described in [RFC1737 <https://www.rfc-editor.org/rfc/rfc1737>],
>>       [RFC2141 <https://www.rfc-editor.org/rfc/rfc2141>], and [RFC3406
>>       <https://www.rfc-editor.org/rfc/rfc3406>].
>>       - This document registers a namespace for URNs.  KNX Association
>>       may assign special meaning to certain of the characters of the Namespace
>>       Specific String (NSS) in its specifications.
>>    - Interoperability: No known issues related to interoperability.
>>    - Resolution: Not applicable; the "knx" namespace is not listed with
>>    a Resolution Discovery System.
>>    - Documentation: KNX IoT Point API, as specified on
>>    https://schema.knx.org (specifically
>>    https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download) and future
>>    EN50090-4-4.
>>    - Additional Information: Not applicable
>>    - Revision Information: Not applicable
>>
>>
>>
>> In the meantime, please contact me for any registration related questions
>> in this regard.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> *MICHAEL CRITCHFIELD *
>>
>> ETS Product Management
>>
>> [e-mail] • T [phone]
>>
>>
>>
>> *KNX Association*
>>
>> De Kleetlaan 5, B-1831 Brussels-Diegem • Belgium
>>
>> www.knx.org
>>
>>
>>
>> <https://knxperience.knx.org/>
>>
>>
>>
>>
>> _______________________________________________
>> urn mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/urn
>>
>