http://wiki.onem2m.org/api.php?action=feedcontributions&feedformat=atom&user=ReinaortegaOneM2M - User contributions [en]2026-06-04T04:46:11ZUser contributionsMediaWiki 1.39.3http://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_8_-_FlexContainer.pdf&diff=471File:OneM2M - Tutorial 8 - FlexContainer.pdf2023-11-17T07:34:58Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_7_-_Notifications.pdf&diff=466File:OneM2M - Tutorial 7 - Notifications.pdf2023-05-30T08:45:21Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_6_-_Access_Control.pdf&diff=461File:OneM2M - Tutorial 6 - Access Control.pdf2023-05-04T08:04:38Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_5_-_Groups.pdf&diff=455File:OneM2M - Tutorial 5 - Groups.pdf2023-03-16T16:03:27Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_4_-_Resource_Discovery.pdf&diff=443File:OneM2M - Tutorial 4 - Resource Discovery.pdf2022-09-05T14:31:13Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_3_-_Basic_Resources_%26_Requests_using_REST_Calls.pdf&diff=442File:OneM2M - Tutorial 3 - Basic Resources & Requests using REST Calls.pdf2022-09-05T14:30:55Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_2_-_First_Contact_with_oneM2M.pdf&diff=441File:OneM2M - Tutorial 2 - First Contact with oneM2M.pdf2022-09-05T14:30:40Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_1_-_Set-up_Configurations.pdf&diff=440File:OneM2M - Tutorial 1 - Set-up Configurations.pdf2022-09-05T14:30:29Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=File:OneM2M_-_Tutorial_0_-_Introduction.pdf&diff=439File:OneM2M - Tutorial 0 - Introduction.pdf2022-09-05T14:29:58Z<p>Reinaortega: </p>
<hr />
<div></div>Reinaortegahttp://wiki.onem2m.org/index.php?title=Main_Page&diff=438Main Page2022-09-05T14:12:59Z<p>Reinaortega: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<!--<br />
<span style="font-size:250%;"> <div style='text-align: center;'> '''oneM2M Wiki''' </div></span><br />
--><br />
[[File:OneM2M-Logo Red 1000px.jpg|250px|center|top]] <br />
<br><br />
<div class="flex-row row"><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Community''' </div></big><br />
<div class="panel-body"><br />
* '''[[Open_Source | Open source projects]]''' List of the most well-known open source projects<br />
* '''[[questions | Issues/Questions]]''' raise you question or issue in stackoverflow or in the mailing list<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Development'''</div></big><br />
<div class="panel-body"><br />
* '''[https://github.com/oneM2M-Tutorials oneM2M github]''' <br />
* '''[[OneM2M_URN_Namespace | oneM2M URN Namespace]]'''<br />
* '''[[tools | Tools]]''' Usefull tools for developers<br />
* '''[[Developer_Guides | Developer guides]]'''<br />
* '''[[OpenAPI|OpenAPI repository]]''' OpenAPI Specification (OAS) for oneM2M API specifications<br />
* '''[[Testing | Testing activities]]'''<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
<br />
</div><!-- end of row 1--><br />
<br />
<div class="flex-row row"> <!-- start of row 2--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Teaching materials'''</div></big><br />
<div class="panel-body"><br />
* '''[[Advanced_tutorial| oneM2M Advanced Tutorial]]''' Full 2-day training to allow to build a complete IoT solution based on oneM2M<br />
* '''[[Semantic_tutorials| oneM2M Semantic Tutorial:]]''' An overview of semantics, applied to IoT and how using ontology can considerably enrich IoT applications and use cases. <br />
* '''[[oneM2M_Tutorials_using_Jupyter_Notebooks|oneM2M Tutorials using Jupyter Notebooks]]''': Video introductions and links to the oneM2M Jupyter Notebook tutorials. <br />
* '''[[oneM2M_hackster| oneM2M Hackster]]''' List of Hackster.io projects based on oneM2M. Some projects have been produced at the oneM2M International hackathon in Fall 2021.<br />
* '''[https://mooc.indiaeu-ictstandards.in/courses/onem2m/ IIIT Hyderabad MOOC]''':<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Getting started with oneM2M'''</div></big><br />
<div class="panel-body"><br />
* '''[[oneM2M_overview|oneM2M Overview]]''': Overall presentation. Understanding the main concept of oneM2M<br />
* '''[[oneM2M_Core | oneM2M Core functionnalities]]''':Quick descritpion of the Core functionnalities. <br />
* '''[[oneM2M_Features | oneM2M Main Features]]''': Presentation of the main functionnalities . <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
</div><!-- end of row 2--><br />
<br />
<div class="flex-row row"> <!-- start of row 3--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''oneM2M Hackathons'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[oneM2M_Hackathons|News]]''': Details on upcoming oneM2M Hackathons<br />
* '''[[Past_events | Past events]]''': Information on past oneM2M Hackathons (awarded projects details, winners, scope,...) <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Outreach'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[OneM2M webinar|oneM2M Webinars]]''': If you wish to know more about oneM2M , you might want to watch the oneM2M webinar videos <br />
* '''[[oneM2M_Videos| Other Videos]]''': See the Media library of oneM2M videos<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 2--><br />
<br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
<!-- end of col 3--><br />
<!-- end of row 3--><br />
<br />
<br />
<br />
__NOEDITSECTION__</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=MediaWiki:Tweeki-navbar-left&diff=437MediaWiki:Tweeki-navbar-left2022-09-05T14:11:53Z<p>Reinaortega: </p>
<hr />
<div><br />
Community<br />
* Open_Source | Open source projects<br />
* questions | Issues/Questions<br />
<br />
Development<br />
* https://github.com/oneM2M-Tutorials | oneM2M tutorial github<br />
* OneM2M_URN_Namespace | oneM2M URN Namespace<br />
* tools | Tools<br />
* Developer_Guides | Developer guides<br />
* Testing| Testing<br />
<br />
Teaching materials<br />
* oneM2M_Tutorials_using_Jupyter_Notebooks| oneM2M Tutorials using Jupyter Notebooks<br />
* Advanced_tutorial| oneM2M Advanced Tutorial<br />
* Semantic_tutorials| IoT Semantic Tutorial<br />
* OneM2M_hackster | hackster.io projects<br />
* https://mooc.indiaeu-ictstandards.in/courses/onem2m/ | IIIT Hyderabad MOOC<br />
<br />
Getting started<br />
* oneM2M_overview|oneM2M Overview<br />
* oneM2M_Core | oneM2M Core functionnalities<br />
* oneM2M_Features | oneM2M Main Features <br />
<br />
Hackathons<br />
* News| News<br />
* Past_events | Past Events<br />
<br />
Outreach<br />
* OneM2M webinar|oneM2M Webinars<br />
* oneM2M_Videos| Other Videos</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=MediaWiki:Tweeki-navbar-left&diff=433MediaWiki:Tweeki-navbar-left2022-09-05T13:33:51Z<p>Reinaortega: </p>
<hr />
<div><br />
Community<br />
* Open_Source | Open source projects<br />
* questions | Issues/Questions<br />
<br />
Development<br />
* https://github.com/oneM2M-Tutorials | oneM2M tutorial github<br />
* OneM2M_URN_Namespace | oneM2M URN Namespace<br />
* tools | Tools<br />
* Developer_Guides | Developer guides<br />
* Testing| Testing<br />
<br />
Teaching materials<br />
* OneM2M_Jupyter_Notebooks| oneM2M Tutorials using Jupyter Notebooks<br />
* Advanced_tutorial| oneM2M Advanced Tutorial<br />
* Semantic_tutorials| IoT Semantic Tutorial<br />
* OneM2M_hackster | hackster.io projects<br />
* https://mooc.indiaeu-ictstandards.in/courses/onem2m/ | IIIT Hyderabad MOOC<br />
<br />
Getting started<br />
* oneM2M_overview|oneM2M Overview<br />
* oneM2M_Core | oneM2M Core functionnalities<br />
* oneM2M_Features | oneM2M Main Features <br />
<br />
Hackathons<br />
* News| News<br />
* Past_events | Past Events<br />
<br />
Outreach<br />
* OneM2M webinar|oneM2M Webinars<br />
* oneM2M_Videos| Other Videos</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=Main_Page&diff=432Main Page2022-09-05T13:25:05Z<p>Reinaortega: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<!--<br />
<span style="font-size:250%;"> <div style='text-align: center;'> '''oneM2M Wiki''' </div></span><br />
--><br />
[[File:OneM2M-Logo Red 1000px.jpg|250px|center|top]] <br />
<br><br />
<div class="flex-row row"><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Community''' </div></big><br />
<div class="panel-body"><br />
* '''[[Open_Source | Open source projects]]''' List of the most well-known open source projects<br />
* '''[[questions | Issues/Questions]]''' raise you question or issue in stackoverflow or in the mailing list<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Development'''</div></big><br />
<div class="panel-body"><br />
* '''[https://github.com/oneM2M-Tutorials oneM2M github]''' <br />
* '''[[OneM2M_URN_Namespace | oneM2M URN Namespace]]'''<br />
* '''[[tools | Tools]]''' Usefull tools for developers<br />
* '''[[Developer_Guides | Developer guides]]'''<br />
* '''[[OpenAPI|OpenAPI repository]]''' OpenAPI Specification (OAS) for oneM2M API specifications<br />
* '''[[Testing | Testing activities]]'''<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
<br />
</div><!-- end of row 1--><br />
<br />
<div class="flex-row row"> <!-- start of row 2--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Teaching materials'''</div></big><br />
<div class="panel-body"><br />
* '''[[Advanced_tutorial| oneM2M Advanced Tutorial]]''' Full 2-day training to allow to build a complete IoT solution based on oneM2M<br />
* '''[[Semantic_tutorials| oneM2M Semantic Tutorial:]]''' An overview of semantics, applied to IoT and how using ontology can considerably enrich IoT applications and use cases. <br />
* [[oneM2M Jupyter Notebooks|'''oneM2M Tutorials using Jupyter Notebooks''']] : Video introductions and links to the oneM2M Jupyter Notebook tutorials. <br />
* '''[[oneM2M_hackster| oneM2M Hackster]]''' List of Hackster.io projects based on oneM2M. Some projects have been produced at the oneM2M International hackathon in Fall 2021.<br />
* '''[https://mooc.indiaeu-ictstandards.in/courses/onem2m/ IIIT Hyderabad MOOC]''':<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Getting started with oneM2M'''</div></big><br />
<div class="panel-body"><br />
* '''[[oneM2M_overview|oneM2M Overview]]''': Overall presentation. Understanding the main concept of oneM2M<br />
* '''[[oneM2M_Core | oneM2M Core functionnalities]]''':Quick descritpion of the Core functionnalities. <br />
* '''[[oneM2M_Features | oneM2M Main Features]]''': Presentation of the main functionnalities . <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
</div><!-- end of row 2--><br />
<br />
<div class="flex-row row"> <!-- start of row 3--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''oneM2M Hackathons'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[oneM2M_Hackathons|News]]''': Details on upcoming oneM2M Hackathons<br />
* '''[[Past_events | Past events]]''': Information on past oneM2M Hackathons (awarded projects details, winners, scope,...) <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Outreach'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[OneM2M webinar|oneM2M Webinars]]''': If you wish to know more about oneM2M , you might want to watch the oneM2M webinar videos <br />
* '''[[oneM2M_Videos| Other Videos]]''': See the Media library of oneM2M videos<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 2--><br />
<br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
<!-- end of col 3--><br />
<!-- end of row 3--><br />
<br />
<br />
<br />
__NOEDITSECTION__</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=Main_Page&diff=431Main Page2022-09-05T13:24:16Z<p>Reinaortega: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<!--<br />
<span style="font-size:250%;"> <div style='text-align: center;'> '''oneM2M Wiki''' </div></span><br />
--><br />
[[File:OneM2M-Logo Red 1000px.jpg|250px|center|top]] <br />
<br><br />
<div class="flex-row row"><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Community''' </div></big><br />
<div class="panel-body"><br />
* '''[[Open_Source | Open source projects]]''' List of the most well-known open source projects<br />
* '''[[questions | Issues/Questions]]''' raise you question or issue in stackoverflow or in the mailing list<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Development'''</div></big><br />
<div class="panel-body"><br />
* '''[https://github.com/oneM2M-Tutorials oneM2M github]''' <br />
* '''[[OneM2M_URN_Namespace | oneM2M URN Namespace]]'''<br />
* '''[[tools | Tools]]''' Usefull tools for developers<br />
* '''[[Developer_Guides | Developer guides]]'''<br />
* '''[[OpenAPI|OpenAPI repository]]''' OpenAPI Specification (OAS) for oneM2M API specifications<br />
* '''[[Testing | Testing activities]]'''<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
<br />
</div><!-- end of row 1--><br />
<br />
<div class="flex-row row"> <!-- start of row 2--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Teaching materials'''</div></big><br />
<div class="panel-body"><br />
* '''[[OneM2M_Jupyter_Notebooks| oneM2M Tutorials using Jupyter Notebooks]]''' oneM2M Tutorials using Jupyter Notebooks<br />
* '''[[Advanced_tutorial| oneM2M Advanced Tutorial]]''' Full 2-day training to allow to build a complete IoT solution based on oneM2M<br />
* '''[[Semantic_tutorials| oneM2M Semantic Tutorial:]]''' An overview of semantics, applied to IoT and how using ontology can considerably enrich IoT applications and use cases. <br />
* [[oneM2M Jupyter Notebooks|'''oneM2M Tutorials using Jupyter Notebooks''']] : Video introductions and links to the oneM2M Jupyter Notebook tutorials. <br />
* '''[[oneM2M_hackster| oneM2M Hackster]]''' List of Hackster.io projects based on oneM2M. Some projects have been produced at the oneM2M International hackathon in Fall 2021.<br />
* '''[https://mooc.indiaeu-ictstandards.in/courses/onem2m/ IIIT Hyderabad MOOC]''':<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Getting started with oneM2M'''</div></big><br />
<div class="panel-body"><br />
* '''[[oneM2M_overview|oneM2M Overview]]''': Overall presentation. Understanding the main concept of oneM2M<br />
* '''[[oneM2M_Core | oneM2M Core functionnalities]]''':Quick descritpion of the Core functionnalities. <br />
* '''[[oneM2M_Features | oneM2M Main Features]]''': Presentation of the main functionnalities . <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- end of col 2--><br />
</div><!-- end of row 2--><br />
<br />
<div class="flex-row row"> <!-- start of row 3--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''oneM2M Hackathons'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[oneM2M_Hackathons|News]]''': Details on upcoming oneM2M Hackathons<br />
* '''[[Past_events | Past events]]''': Information on past oneM2M Hackathons (awarded projects details, winners, scope,...) <br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 1--><br />
<br />
<div class="col-xs-12 col-md-6 col-lg-6"><br />
<div class="panel panel-default"><br />
<big><div class="panel-heading">'''Outreach'''</div></big><br />
<div class="panel-body"><br />
<br />
* '''[[OneM2M webinar|oneM2M Webinars]]''': If you wish to know more about oneM2M , you might want to watch the oneM2M webinar videos <br />
* '''[[oneM2M_Videos| Other Videos]]''': See the Media library of oneM2M videos<br />
<br />
</div><br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
</div><!-- End of col 2--><br />
<br />
<!-- <div class="panel-footer">Footer text 1</div> --><br />
</div><!-- End of pan --><br />
<!-- end of col 3--><br />
<!-- end of row 3--><br />
<br />
<br />
<br />
__NOEDITSECTION__</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=411OneM2M URN Namespace2022-02-25T16:48:00Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:<oneM2M-urn><br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
<nss-root>:<nss-restoftree><br />
<br />
where <nss-root> are the nodes allocated under oneM2M URN namespace as defined in Table 1 and <nss-restoftree> is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an <oneM2M-urn> under oneM2M URN namespace'''<br />
<br />
Applications for new <oneM2M-urn>, using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of <oneM2M-urn>. Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|mgmt<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|example<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
As general rule, the NSS-restoftree is limited to printable ASCII character set, unless otherwise specified by the sub-node namespace.<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
<nowiki>urn:onem2m:mgmt:nwkType</nowiki>:<identifier>[?=<parameters>] <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|urn:onem2m:mgmt:nwkType<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=410OneM2M URN Namespace2022-02-23T08:52:15Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:<oneM2M-urn><br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
<nss-root>:<nss-restoftree><br />
<br />
where <nss-root> are the nodes allocated under oneM2M URN namespace as defined in Table 1 and <nss-restoftree> is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an <oneM2M-urn> under oneM2M URN namespace'''<br />
<br />
Applications for new <oneM2M-urn>, using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of <oneM2M-urn>. Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|mgmt<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|example<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
<nowiki>urn:onem2m:mgmt:nwkType</nowiki>:<identifier>:[<parameters>] <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|urn:onem2m:mgmt:nwkType<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=408OneM2M URN Namespace2022-02-08T13:38:42Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:<oneM2M-urn><br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
<nss-root>:<nss-restoftree><br />
<br />
where <nss-root> are the nodes allocated under oneM2M URN namespace as defined in Table 1 and <nss-restoftree> is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an <oneM2M-urn> under oneM2M URN namespace'''<br />
<br />
Applications for new <oneM2M-urn>, using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of <oneM2M-urn>. Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|mgmt<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|example<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>] <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|urn:onem2m:mgmt:nwkType<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=407OneM2M URN Namespace2022-02-01T10:20:53Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
"<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>]" <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|urn:onem2m:mgmt:nwkType<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=406OneM2M URN Namespace2022-02-01T10:20:10Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
"<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>]" <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|urn:onem2m:nwkType urn:onem2m:mgmt:nwkType<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=405OneM2M URN Namespace2022-02-01T10:19:12Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
"<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>]" <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250 TS-0004]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=404OneM2M URN Namespace2022-02-01T10:17:02Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
"<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>]" <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in [[https://member.onem2m.org/Application/documentapp/downloadLatestRevision/default.aspx?docID=34250|TS-0004]]. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=403OneM2M URN Namespace2022-01-31T13:18:46Z<p>Reinaortega: /* MGMT URN Namespace */</p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace.<br />
<br />
The MGMT URN has the following structure: <br />
<br />
"<nowiki>urn:onem2m:mgmt.:nwkType</nowiki>:<identifier>:[<parameters>]" <br />
<br />
where <br />
<br />
<identifier> is network technology e.g. “zigbee”, “lora” etc.<br />
<br />
[parameters] is any additional optional variable<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=402OneM2M URN Namespace2022-01-31T13:15:52Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace|MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=401OneM2M URN Namespace2022-01-31T13:14:24Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[OneM2M_URN_Namespace#MGMT URN Namespace]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=400OneM2M URN Namespace2022-01-28T15:10:47Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|Table 2. MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:onem2m:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=399OneM2M URN Namespace2022-01-28T14:48:37Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|Table 2. MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=398OneM2M URN Namespace2022-01-28T14:45:59Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|[[Table 2. MGMT Rest of tree]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
=== '''MGMT URN Namespace''' ===<br />
The following table maintains namespaces for oneM2M area network technologies namespace registry as a subtree of the oneM2M root <nowiki>urn:onem2m</nowiki> namespace<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=397OneM2M URN Namespace2022-01-28T14:40:02Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
'''Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace'''<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|Table 2. MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi_c_12<br />
* zwave<br />
* dlms_cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=298OneM2M URN Namespace2021-11-08T13:00:58Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|Table 2. MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi c 12<br />
* zwave<br />
* dlms/cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=297OneM2M URN Namespace2021-11-08T12:55:05Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|<nowiki>urn:onem2m:mgmt</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|Table 2. MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT Rest of tree<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<br />
* lora<br />
* sigfox<br />
* 6lowpan<br />
* mbus<br />
* ansi-c-12<br />
* zwave<br />
* dlms-cosem<br />
* wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=296OneM2M URN Namespace2021-11-08T12:37:12Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|<nowiki>urn:onem2m:location</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|[[urn:onem2m:mgmt]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|[[Table 2. MGMT Rest of tree]]<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT-Roots<br />
!MGMT-sub-tree<br />
!Entire URN<br />
!Type<br />
|'''Description'''<br />
|-<br />
|nwkType <br />
|[urn:onem2m:nwkType urn:onem2m:mgmt:nwkType]<br />
|string<br />
|The namespace for the area network types for an oneM2M data type m2m:areaNwkType defined in TS-0004. The network types can have following values:<br />
* zigbee<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* lora<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* sigfox<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* 6lowpan<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* mbus<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* ansi c 12<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* zwave<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span><br />
* dlms/cosem<span lang="EN-IN">The namespace for the area network types for an oneM2M data type </span>wifi<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=295OneM2M URN Namespace2021-11-08T12:33:06Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|<nowiki>urn:onem2m:location</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|mgmt-nss<br />
|"mgmt"<br />
|[[urn:onem2m:mgmt]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|MGMT Rest of tree<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.<br />
<br />
{| class="wikitable"<br />
|+Table 2. MGMT-Roots<br />
!MGMT-sub-tree<br />
!Type<br />
!Description<br />
|-<br />
|nwkType <br />
|urn:onem2m:nwkType<br />
|string<br />
|?????<br />
|}</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=275OneM2M URN Namespace2021-11-01T16:31:00Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|<nowiki>urn:onem2m:location</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|sds-nss<br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=274OneM2M URN Namespace2021-11-01T16:30:29Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|<nowiki>urn:onem2m:location</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|sds-nss<br />
|"sds"<br />
|urn:onem2m:sds<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=273OneM2M URN Namespace2021-11-01T16:30:13Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|<nowiki>urn:onem2m:location</nowiki><br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|sds-nss<br />
|"sds"<br />
|[[urn:onem2m:sds]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=272OneM2M URN Namespace2021-11-01T16:29:35Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"location"<br />
|urn:onem2m:location<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|sds-nss<br />
|"sds"<br />
|[[urn:onem2m:sds]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=271OneM2M URN Namespace2021-11-01T16:26:02Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted to the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
<br />
• Node name(s) to be created<br />
<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|location-nss <br />
|"loctaion"<br />
|[[urn:onem2m:location]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|sds-nss<br />
|"sds"<br />
|[[urn:onem2m:sds]]<br />
|SDS<br />
|WPM URN Application procedure<br />
|??????<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=270OneM2M URN Namespace2021-11-01T15:31:24Z<p>Reinaortega: </p>
<hr />
<div><br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|sds-nss <br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|SDS URN application<br />
|SDS rest of tree<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=269OneM2M URN Namespace2021-11-01T15:31:00Z<p>Reinaortega: </p>
<hr />
<div>oneM2M URN Namespace<br />
<br />
<br />
<br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|sds-nss <br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|SDS URN application<br />
|SDS rest of tree<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=268OneM2M URN Namespace2021-11-01T15:30:31Z<p>Reinaortega: </p>
<hr />
<div>oneM2M URN Namespace<br />
<br />
<br />
<br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
<br />
<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|sds-nss <br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|SDS URN application<br />
|SDS rest of tree<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=267OneM2M URN Namespace2021-11-01T15:30:08Z<p>Reinaortega: </p>
<hr />
<div>oneM2M URN Namespace<br />
<br />
<br />
<br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
<br />
<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|sds-nss <br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|SDS URN application<br />
|SDS rest of tree<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=266OneM2M URN Namespace2021-11-01T15:28:55Z<p>Reinaortega: </p>
<hr />
<div>oneM2M URN Namespace<br />
<br />
<br />
<br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
<br />
<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
{| class="wikitable"<br />
|+Table 1. NSS-Roots<br />
!Structure<br />
!NSS-Root<br />
!<nowiki>urn:NID:NSS-Root</nowiki><br />
!oneM2M group<br />
!Application details reference<br />
!NSS-restoftree reference<br />
|-<br />
|sds-nss <br />
|"sds"<br />
|<nowiki>urn:onem2m:sds</nowiki><br />
|SDS<br />
|SDS URN application<br />
|SDS rest of tree<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|experimental-nss<br />
|"example"<br />
|<nowiki>urn:etsi:example</nowiki> <br />
| -<br />
|For experimental use<br />
|<br />
|}<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace&diff=265OneM2M URN Namespace2021-11-01T15:16:45Z<p>Reinaortega: Created page with "oneM2M URN Namespace oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs base..."</p>
<hr />
<div>oneM2M URN Namespace<br />
<br />
<br />
<br />
oneM2M maintains a namespace registry based on URNs in support of the specifications produced by oneM2M. The oneM2M registry allocates these URNs based upon a reserved NID ('onem2m'). See RFCXXXX for the document which reserved this NID.<br />
<br />
All URNs in the oneM2M URN namespace will have the following structure:<br />
<br />
<br />
urn:onem2m:"oneM2M-urn"<br />
<br />
<br />
The "oneM2M-urn" will have the following structure:<br />
<br />
<br />
<br />
"nss-root":"nss-restoftree"<br />
<br />
<br />
<br />
<br />
where "nss-root" are the nodes allocated under oneM2M URN namespace as defined in Table 1 and "nss-restoftree" is the rest of tree that has one or more strings each separated with a colon ":"<br />
<br />
Procedure for requesting an "oneM2M-urn" under oneM2M URN namespace<br />
<br />
Applications for new "oneM2M-urn", using one of the NSS-Roots (excluding experimental) specified in table 1, shall be addressed to the oneM2M working group in charge of the given NSS-Root. Each oneM2M working group may have a different policy for the allocation of "oneM2M-urn". Please, see the corresponding application details indicated in the Table 1.<br />
<br />
<br />
URNs within experimental is for those modules that are not expected to be used in any published work. So, there is no need to submit a request for such URNs. There is no capture of any URNs under experimental.<br />
<br />
<br />
<br />
When a URN application implies the creation of a new node under oneM2M URN namespace, then an application shall be submitted from the oneM2M Technical Plenary group to onem2m-tp@list.onem2m.org include the following:<br />
<br />
• oneM2M working group<br />
• Node name(s) to be created<br />
• Reference to the urn application procedure for the given group (i.e. a link, a document, etc..)<br />
• Reference to the location where the NSS-restoftree is available<br />
<br />
<br />
Table 1. NSS-Roots<br />
Structure NSS-Root urn:NID:NSS-Root oneM2M group Application details reference NSS-restoftree reference<br />
sds-nss "sds" urn:onem2m:sds SDS SDS URN application SDS rest of tree<br />
experimental-nss "example" urn:etsi:example - For experimental use <br />
<br />
<br />
<br />
where:<br />
<br />
NSS-Root = (ALPHANUMERIC)0*(ALPHANUMERIC/-/_)<br />
<br />
i.e. a string starts with an alphanumeric (a-zA-Z0-9) and has 0 or more mix alphanumeric (a-zA-Z0-9) or hyphen or underscore.</div>Reinaortegahttp://wiki.onem2m.org/index.php?title=MediaWiki:Sidebar&diff=264MediaWiki:Sidebar2021-11-01T15:09:11Z<p>Reinaortega: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** oneM2M URN Namespace|oneM2M URN Namespace<br />
** Developer Guides| Developer Guides<br />
<br />
//** Implementation Corners | Implementation Corners<br />
** Open Source |Open Source<br />
//** Commercial Implementations|Vendor implementations<br />
//** Developer day Nov 2016 slides|"Developer day" Nov 2016 slides<br />
** Gitlab|Gitlab<br />
** Tools|Tools<br />
** Events | Developer Events<br />
** Questions | Questions<br />
<br />
//** oneM2M showcases|oneM2M showcase Nov 2016<br />
<br />
** News|News<br />
** Wikipedia|Wikipedia<br />
<br />
// **Forum|Forum<br />
//** recentchanges-url|recentchanges<br />
// ** helppage|help<br />
//* SEARCH<br />
//* TOOLBOX<br />
//* LANGUAGES</div>Reinaortega