MEC URN namespace: Difference between revisions
Featherston1 (talk | contribs) (Implementation of MECDECODE(24)000007) |
Featherston1 (talk | contribs) m (Added "onwards" to indicate that versions later than 010-2 V2.2.1 are valid too) |
||
| 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 [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The MEC URN namespace has the following structure: | 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 [https://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 18: | Line 18: | ||
|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: | |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: | ||
<ul> | <ul> | ||
<li>ETSI GS MEC 010-2 v2.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li> | <li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li> | ||
</ul> | </ul> | ||
|- | |- | ||
Revision as of 11:31, 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).