OSM URN Namespace: Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
(Created page with "=== Introduction === OSM is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> namespace. A description of the top level ET...")
 
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''THIS PAGE IS DEPRECATED'''. OSM User Guide has been moved to a new location: '''https://osm.etsi.org/docs/user-guide/'''
---
=== Introduction ===
=== Introduction ===
OSM is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx].
OSM is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> namespace. A description of the top level ETSI URN namespace can be found on the [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx ETSI PNNS page]


The OSM URN namespace has the following structure:
The OSM URN namespace has the following structure:
  <nowiki>urn:etsi:osm</nowiki>:<NFV sub-tree>
  <nowiki>urn:etsi:osm</nowiki>:<OSM sub-tree>
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.


=== NFV sub-tree ===
=== OSM sub-tree ===
{| class="wikitable"
{| class="wikitable"
|+
|+
!NFV sub-tree
!OSM sub-tree
!Full Namespace
!Full Namespace
!Type
!Type
Line 19: Line 23:
|string
|string
|Namespace for YANG modules specified in OSM.
|Namespace for YANG modules specified in OSM.
[https://osm.etsi.org/gitweb/?p=osm/IM.git;a=tree;f=models/yang]
[https://osm.etsi.org/gitweb/?p=osm/IM.git;a=tree;f=models/yang OSM/IM.git]
|}
|}


Line 32: Line 36:
The procedure to request an entry is described as follows.
The procedure to request an entry is described as follows.


* ''Step #1:'' Send an e-mail to OSM_TSC mailing list indicating the name of the sub-tree, the contact person and the purpose of that subtree.
* ''Step #1:'' Send an e-mail to the [mailto:OSM_TSC@list.etsi.org OSM_TSC@list.etsi.org] mailing list indicating the name of the sub-tree, the contact person and the purpose of that subtree.
* ''Step #2:'' The TSC will review the proposal.
* ''Step #2:'' The TSC will review the proposal.
** If the application is accepted, a new entry in the "OSM URN Namespace" will be enabled.
** If the application is accepted, a new entry in the "OSM URN Namespace" will be enabled.
** If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".
** If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".

Latest revision as of 17:18, 17 February 2021

THIS PAGE IS DEPRECATED. OSM User Guide has been moved to a new location: https://osm.etsi.org/docs/user-guide/

---

Introduction

OSM is maintaining a namespace registry as a sub tree of the ETSI root urn:etsi namespace. A description of the top level ETSI URN namespace can be found on the ETSI PNNS page

The OSM URN namespace has the following structure:

urn:etsi:osm:<OSM sub-tree>

The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.

OSM sub-tree

OSM sub-tree Full Namespace Type Description
yang
urn:etsi:osm:yang
string Namespace for YANG modules specified in OSM.

OSM/IM.git

Type definitions

string = (ALPHA)0*(ALPHANUMERIC/-/_)
# a string starts with an upper- or lower-case letter followed by zero or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}

Requesting a entry

The procedure to request an entry is described as follows.

  • Step #1: Send an e-mail to the OSM_TSC@list.etsi.org mailing list indicating the name of the sub-tree, the contact person and the purpose of that subtree.
  • Step #2: The TSC will review the proposal.
    • If the application is accepted, a new entry in the "OSM URN Namespace" will be enabled.
    • If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".