MECwiki - User contributions [en]

MEC URN namespace

2021-04-28T13:34:54Z

Rauschenbac:

<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:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|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:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>
|}

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
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).

MEC URN namespace

2021-04-28T13:32:04Z

Rauschenbac:

<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:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|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:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>
|}

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their 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).

MEC URN namespace

2021-04-28T13:31:36Z

Rauschenbac:

<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:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|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:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>
|}

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their 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).

MEC URN namespace

2021-04-28T13:26:03Z

Rauschenbac:

<h3> Introduction</h3>
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root URN 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 NFV URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
<table>
<th>
<td>MEC sub-tree</td>
<td>Full Namespace</td>
<td>Type</td>
<td>Description</td>
</th>

<tr>
<td>coord</td>
<td>urn:etsi:nfv:coord</td>
<td>string</td>
<td>The namespace for Llifecycle management (LCM) coordination actions specified in group
specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>
</td>
</tr>
</table>

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their 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).

MEC URN namespace

2021-04-28T13:24:33Z

Rauschenbac:

<h3> Introduction</h3>
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 [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The NFV URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
<table>
<tr>
<td>MEC sub-tree</td>
<td>Full Namespace</td>
<td>Type</td>
<td>Description</td>
</tr>

<tr>
<td>coord</td>
<td>urn:etsi:nfv:coord</td>
<td>string</td>
<td>The namespace for Llifecycle management (LCM) coordination actions specified in group
specifications defined by ETSI ISG MEC.

The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>
</td>
</tr>
</table>

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their 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).

MEC URN namespace

2021-04-28T13:23:46Z

Rauschenbac: Created page with "<h3> Introduction</h3> 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 ca..."

<h3> Introduction</h3>
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 [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The NFV URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

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

<h3>MEC sub-tree</h3>
<table>
<tr>
<td>MEC sub-tree</td>
<td>Full Namespace</td>
<td>Type</td>
<td>Description</td>
</tr>

<tr>
<td>coord</td>
<td>urn:etsi:nfv:coord</td>
<td>string</td>
<td>The namespace for Llifecycle management (LCM) coordination actions specified in group
specifications defined by ETSI ISG MEC.

The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>

<h3>Type definitions</h3>
<pre>
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}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their 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).

Main Page

2021-04-28T12:56:45Z

Rauschenbac: Undo revision 3021 by Rauschenbac (talk)

__NOTOC__

<div style="width:100%;display:block; overflow: auto">

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Ecosystem ==
* [https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem '''MEC Ecosystem'''] main page: Covers API Testing, [https://forge.etsi.org Forge] (OpenAPI descriptions) and details of relevant external projects
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Sandbox ==
API playground to learn MEC APIs
* [https://try-mec.etsi.org '''MEC Sandbox Portal'''] Link to the platform
* [https://mecwiki.etsi.org/index.php?title=MEC_Sandbox_Help '''MEC Sandbox Help'''] Platform usage documentation
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Testing ==
* [https://www.etsi.org/deliver/etsi_gr/MEC-DEC/001_099/025/02.01.01_60/gr_MEC-DEC025v020101p.pdf '''Testing Framework''']: Methodology, guidelines and framework
* '''API Conformance Test Suites'''
** [https://forge.etsi.org/rep/mec/gs032p2-test-purposes '''Test Purposes''']
** [https://forge.etsi.org/rep/mec/gs032p3-ttcn-test-suite '''TTCN-3''']: Testing and Test Control Notation version 3 testing language
** [https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite '''Robot Framework''']
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Proof of Concept Activity ==

* '''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.
* '''[[PoC Topics]]''' Information about ISG MEC PoC Topics.
* '''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).
* '''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.
* '''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Hackathons ==
* '''[[MEC Hackathon Framework]]''': Guidelines and call for proposals of hackathons for MEC
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Deployment Trials ==
* '''[[MEC Deployment Trials Framework]]''': Discover MDTs and how to participate.
* [[Ongoing MDTs|'''Check the list of MDT''']]

</div>
</div>

<div style="display:block; width:100%">
This Wiki is provided as a tool for the use of ISG MEC participants.
You may need to login to access some information

''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''

If you are an ISG MEC participant and do not have an EOL account yet,
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]

For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]

<center>
'''[http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''
</center>

</div>

Main Page

2021-04-28T12:55:58Z

Rauschenbac:

__NOTOC__

<div style="width:100%;display:block; overflow: auto">

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Ecosystem ==
* [https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem '''MEC Ecosystem'''] main page: Covers API Testing, [https://forge.etsi.org Forge] (OpenAPI descriptions) and details of relevant external projects
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Sandbox ==
API playground to learn MEC APIs
* [https://try-mec.etsi.org '''MEC Sandbox Portal'''] Link to the platform
* [https://mecwiki.etsi.org/index.php?title=MEC_Sandbox_Help '''MEC Sandbox Help'''] Platform usage documentation
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Testing ==
* [https://www.etsi.org/deliver/etsi_gr/MEC-DEC/001_099/025/02.01.01_60/gr_MEC-DEC025v020101p.pdf '''Testing Framework''']: Methodology, guidelines and framework
* '''API Conformance Test Suites'''
** [https://forge.etsi.org/rep/mec/gs032p2-test-purposes '''Test Purposes''']
** [https://forge.etsi.org/rep/mec/gs032p3-ttcn-test-suite '''TTCN-3''']: Testing and Test Control Notation version 3 testing language
** [https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite '''Robot Framework''']

== MEC Registries ==
** URN subtree registry
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Proof of Concept Activity ==

* '''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.
* '''[[PoC Topics]]''' Information about ISG MEC PoC Topics.
* '''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).
* '''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.
* '''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Hackathons ==
* '''[[MEC Hackathon Framework]]''': Guidelines and call for proposals of hackathons for MEC
</div>

<div style="width:40%; min-width: 100px; padding:20px;float:left; font-size:12pt">
== MEC Deployment Trials ==
* '''[[MEC Deployment Trials Framework]]''': Discover MDTs and how to participate.
* [[Ongoing MDTs|'''Check the list of MDT''']]

</div>
</div>

<div style="display:block; width:100%">
This Wiki is provided as a tool for the use of ISG MEC participants.
You may need to login to access some information

''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''

If you are an ISG MEC participant and do not have an EOL account yet,
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]

For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]

<center>
'''[http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''
</center>

</div>