[urn] Re: Application: URN Namespace Identifier: nfi
Peter Waher <[email protected]> Fri, 1 Aug 2025 08:25:04 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <AS4P250MB0413B67E8AAB3BA63FC3DB12A926A@AS4P250MB0413.EURP250.PROD.OUTLOOK.COM> |
Hello Peter Thanks for the feedback, and the edits. I accepted and transferred them all into the original documents. I also found an additional reference that I removed, replacing it with a text reference, and changed the date to today's date. I generated a new PDF to match the edits as well. Best regards, Peter Waher ________________________________ Från: Peter Saint-Andre <[email protected]> Skickat: Torsdag, 31 juli 2025 18:31 Till: Peter Waher <[email protected]>; Dale R. Worley <[email protected]> Kopia: [email protected] <[email protected]> Ämne: Re: [urn] Re: Application: URN Namespace Identifier: nfi Hi Peter, Here is more feedback. You can also find my suggestions here: https://github.com/stpeter/urn-namespaces/pull/1 The version number should be "1". (It is the version of the namespace itself, not of the document or template registering this version.) I don't think we need the citations (e.g. to various RFCs) because we don't usually include those in the completed templates published here: https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml Peter On 7/31/25 6:10 AM, Peter Waher wrote: > Hello Dale > > Thanks for the feedback. I've addressed all the issues as you > recommended. Please find the revised application attached (version 3). > > Best regards, > Peter Waher > > ------------------------------------------------------------------------ > *Från:* Dale R. Worley <[email protected]> > *Skickat:* Torsdag, 31 juli 2025 03:27 > *Till:* Peter Waher <[email protected]> > *Kopia:* [email protected] <[email protected]> > *Ämne:* Re: [urn] Application: URN Namespace Identifier: nfi > > Reviewing this application: > > Namespace Identifier (formal) > > nfi > > Version > > 2 > > I am noting here that I am reviewing the "nfi" version. > > Contact Person: > > Peter Waher > email: [email protected] > email: [email protected] > xmpp: [email protected] > > It's desirable for the contact address to be given as a "role e-mail > address" rather than an individual's address. > > Syntax > > Using the format defined in RFC 3986 [5], and some of its base > classes, a formal definition of the syntax used for urn URIs > used together with the nfi Namespace Identifier is as follows: > > nfi-uri = "urn:nfi:" category ":" subcat : version > category = name > subcat = 1*( ":" name ) > name = 1*( unreserved / pct-encoded ) > version = 1*DIGIT "." 1*DIGIT > > I note that "urn:nfi:iot:ctr:1.0" and "urn:nfi:iot:ctr:1.0:1.0" both > conform to this syntax, though you probably don't want allocate the > second one. In practice, I think you want to restrict "name" to start > with an ALPHA so that any "name" part is imediately distingushable > from the "version" part by the human reader. It also allows the > possiblity of the future use of omitting the version part. > > name = ALPHA *( unreserved / pct-encoded ) > > Resolution > > There is no resolution mechanism anticipated for use with the > nfi namespace identifier. > > Documentation > > The Neuro-Foundation interfaces are documented publicly in [1]. > > The "Resolution" section is correct within the meaning of RFC 8141, > but for practical purposes, I would recommend pointing people to the > mapping between the URNs and the definition of the interfaces they > identify as a "resolution" process: > > Resolution > > There is no resolution mechanism anticipated for use with the > nfi namespace identifier. However, each URN identifies an > interface as described by the Documentation. > > -- > > [5] T. Berners-Lee, R. Fielding and L. Masinter, "Uniform Resource > Identifier (URI): Generic Syntax," 01 2005. [Online]. > Available: https://tools.ietf.org/html/rfc3986 <https:// > tools.ietf.org/html/rfc3986>. > [Accessed 03 07 2015]. > > If you provide a reference for RFC 3986, I would recommend adding a > reference to RFC 8141, even though strictly speaking, the registration > doesn't reference it: > > [6] "Uniform Resource Names (URNs)," [Online]. > Available: http://xmpp.org/rfcs/rfc8141.html <http:// > xmpp.org/rfcs/rfc8141.html>. > > Dale > > _______________________________________________ > 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]
IANA Application, urn-nf.pdf
(application/pdf, 237.4 KB) - not displayed
IANA Application, urn-nf.txt
(text/plain, 6.4 KB)
Trust Anchor Group AB Peter Waher Blekholmsterrassen 36 [email protected] 11164 Stockholm 2025-July-31 Sweden Namespace Identifier Registration Application nfi Abstract This document contains the formal application for registering the Namespace Identifier nfi for the purpose of clearly and compactly defining namespaces for interoperability as defined by the Neuro-Foundation, in accordance with RFC 8141. Keywords Internet of Things, Smart City, Interoperability. Copyright Notice Copyright (c) 2025 Trust Anchor Group AB and the persons identified as the document authors. All rights reserved. Upon registration of the Namespace Identifier, copyright can be transferred to the corresponding Internet body, if required. Namespace Registration for Neuro-Foundation Following is the formal application for the registration of the Namespace Identifier nfi. Namespace Identifier: nfi Version: 1 Date: 2025-08-01 Registrant: Name: Trust Anchor Group AB Address: Blekholmsterrassen 36 11164 Stockholm Sweden Contact Person: Peter Waher email: [email protected] xmpp: [email protected] Purpose: Neuro-Foundation presents communication infrastructure for a globally scalable, distributed infrastructure for smart societies. By harmonizing technologies (bridging technology boundaries), it allows different technologies to interact and interoperate. The interfaces support: * Local governance * Protection of privacy * Definition of ownership * Consent-based communication * High level of cybersecurity * Cross-domain interoperability * Cross-technology interoperability * Self-sovereign digital identities * Legally binding cross-domain agreements * Distributed discovery and decision support * Monetization and support for micro-transactions They do this by defining interoperability interfaces used over different Internet protocols such as HTTP and the versatile and extensible Internet protocol XMPP, as well as others. Each interoperability interface, be it a peer-to-peer interoperability interface or an edge service interface, is identified using a Neuro-Foundation namespace. For interoperability purposes, this namespace must be clear and unambiguous and not be associated with any particular domain. For efficiency, it must be short, to avoid unnecessary bytes during communication, as the namespace is repeated many times. For this purpose, a URN namespace is ideal. The interfaces are used by different organizations such as companies, academic institutions, non-governmental organizations, governmental organizations and other actors. It is also used within several working groups of standards bodies such as the IEEE. In an effort to make sure all interfaces are available open source and publicly accessible and usable, Neuro-Foundation is being formed. The purpose is to act as the custodian of the interfaces and the corresponding intellectual property. The Namespace Identifier will solely be used to identify interoperability namespaces published by the Neuro-Foundation in a short and unambiguous manner. Syntax: Using the format defined in RFC 3986, and some of its base classes, a formal definition of the syntax used for urn URIs used together with the nfi Namespace Identifier is as follows: nfi-uri = "urn:nfi:" category ":" subcat : version category = name subcat = 1*( ":" name ) name = ALPHA *( unreserved / pct-encoded ) version = 1*DIGIT "." 1*DIGIT As an example, the following are some of the namespaces defined for IoT interoperability and harmonization, as defined by the Neuro-Foundation: * urn:nfi:iot:concentrator:1.0 - Concentrators * urn:nfi:iot:ctr:1.0 - Actuator Control * urn:nfi:iot:disco:1.0 - Discovery * urn:nfi:iot:e2e:1.0 - End-to-End Encryption * urn:nfi:iot:events:1.0 - Event subscription * urn:nfi:iot:leg:id:1.0 - Legal identities * urn:nfi:iot:leg:sc:1.0 - Smart Contracts * urn:nfi:iot:p2p:1.0 - Peer-to-Peer Connectivity * urn:nfi:iot:prov:d:1.0 - Provisioning for Devices * urn:nfi:iot:prov:o:1.0 - Provisioning for Owners * urn:nfi:iot:prov:t:1.0 - Provisioning Tokens * urn:nfi:iot:sd:1.0 - Sensor Data * urn:nfi:iot:swu:1.0 - Software Updates * urn:nfi:iot:synchronization:1.0 - Synchronization Assignment: Names are assigned by the Neuro-Foundation in cooperation with funding and interested partners, as new interfaces are developed and published. No other resources are assigned names using the nfi namespace identifier. Security and Privacy: There are no known security or privacy implications of using the nfi namespace identifier. The URIs only identify public interfaces, which contain no personal, confidential or sensitive information. Interoperability: There are no known interoperability implications of using the nfi namespace identifier. One of the reasons for using the URN URI schema to identify interfaces, is to avoid confusion with namespaces using the http or https URI schema to identify the namespace, as they may or may not point to downloadable schema files for the corresponding namespaces. Using the URN URI schema ensures no attempts to download schema resources are attempted during interoperable communication across domains with different security policies. Resolution: There is no resolution mechanism anticipated for use with the nfi namespace identifier. However, each URN identifies an interface as described by this document and published by the Neuro-Foundation. Documentation: The Neuro-Foundation interfaces are documented publicly at: https://neuro-foundation.io/ Additional Information: The nfi namespace identifier is used to clearly identify Neuro-Foundation interfaces for interoperable communication in a short and clear manner. Interface names are not negotiated with other organizations, to avoid confusion and overlap.