MEC URN namespace: Difference between revisions
From MECwiki
Rauschenbac (talk | contribs) No edit summary |
Featherston1 (talk | contribs) m (Changed https to http to avoid a "lock icon" being presented) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<h3> Introduction</h3> | <h3> Introduction</h3> | ||
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [ | ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [http://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure: | ||
<pre>urn:etsi:mec:<MEC sub-tree></pre> | <pre>urn:etsi:mec:<MEC sub-tree></pre> | ||
| Line 16: | Line 16: | ||
|<nowiki>urn:etsi:mec:coord</nowiki> | |<nowiki>urn:etsi:mec:coord</nowiki> | ||
|string | |string | ||
|The namespace for Lifecycle management (LCM) coordination actions specified in group | |The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions: | ||
specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions: | |||
<ul> | <ul> | ||
<li>ETSI GS MEC 010-2 v2.2.1 ( | <li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[http://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li> | ||
[ | |||
</ul> | </ul> | ||
|- | |||
|capifext | |||
|<nowiki>urn:etsi:mec:capifext</nowiki> | |||
|string | |||
|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions: | |||
* ETSI GS MEC 011 v3.2.1 (published at [[http://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]]) | |||
|} | |} | ||
| Line 34: | Line 39: | ||
<h3>Adding an entry (for ETSI ISG MEC group only)</h3> | <h3>Adding an entry (for ETSI ISG MEC group only)</h3> | ||
A new MEC sub-tree can only be requested by | A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE. | ||
<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification). | <b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification). | ||
Latest revision as of 15:00, 25 March 2024
Introduction
ETSI ISG MEC 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 webpage [1]. The MEC URN namespace has the following structure:
urn:etsi:mec:<MEC sub-tree>
The following sections describe the basic structure of the sub-tree and how an entry in the registry can be requested.
MEC sub-tree
| MEC sub-tree | Full Namespace | Type | Description |
|---|---|---|---|
| coord | urn:etsi:mec:coord | string | The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
|
| capifext | urn:etsi:mec:capifext | string | The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:
|
Type definitions
string = 1*(ALPHANUMERIC/-/_)
# a string should contain one or more upper- or lower-case letters, integer numbers, hyphens or underscores
ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}
Adding an entry (for ETSI ISG MEC group only)
A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE.
Pre-condition: a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).