.gitlab/merge_request_templates/coversheet_contribution_simplified.md

+| Coversheet | Value |
+| ------ | ------ |
+| Meeting ID | #MEETING_ID# |
+| Work-item | #WI# |
+| Reason | #REASON# |

README.md

+# oneM2M tr-0073 Specification
+
+This repository hosts the oneM2M tr-0073 specification defined by oneM2M Partnership project.
+
+## Available versions
+
+All available baselines produced from this repository are available at [tr-0073-baselines](https://specifications.onem2m.org/tr-0073/) (**URL available only if there is at least one baseline**)
+
+## How to raise issues
+
+Please report errors, bugs or other issues [here](https://git.onem2m.org/specifications/tr-0073/issues) or [here](https://git.onem2m.org/issues/issues).
+
+## How to contribute
+
+oneM2M permits the use of Gitlab to manage contributions to this specification.
+For more information, visit the [oneM2M Gitlab contribution procedure](https://git.onem2m.org/tools/contribution-procedure).
+
+## Available tools
+
+A set of tools is used by this repository to facilitate the contribution management:
+
+- Autogeneration of Word CR documents:
+    - Upon creation of a Merge Request, a pipeline is executed to produce the associated Word CR document that contains the tracked changes proposed by the Merge Request.
+    - Right after creation of a Merge Request, the source branch is protected in order to avoid any further change to the submitted contribution
+
+- Publication of a new baseline
+    - Upon creation of tag, a Word document will be generated from the markdown specification in this repository and published at the [tr-0073 specifications](https://specifications.onem2m.org/tr-0073/)
+    - As Table of Content is not used in the markdown specfication document of this repository. A tool will generate the ToC and add it to the any new published baseline.
+
+Please, refer to [Tools/Scripts repository](hhtps://git.onem2m.org/tools/scripts) for more details.
+
+Some known issues:
+
+- Generation of Word CR:
+    - Additions/deletions of images will not appear as tracked change in the Word CR
+    - Additions/deletions of a list of elements will make the list appearing as not enumerated in the Word CR
+    - Changes in the first row of a table will break the conversion of such table to Word, the markdown table source code will be seen
+    - Changes in clause titles will break the conversion of corresponding headings to Word, the markdown heading code will be seen

TR-0073-Developer_Guide_Deploying_Semantics.md

+
+![oneM2M logo](media/logo.png)
+
+
+|oneM2M<br />Technical Report |oneM2M<br />Technical Report |
+|-|-|
+|Document Number |TR-00xx-V-x.y.z |
+|Document Name: |The name of the document<br /> |
+|Date: |&lt;20yy-mm-dd> |
+|Abstract: |&lt; An abstract of the document and information that may be used in subsequent electronic searches> |
+|Template Version: January 2020 (do not modify) | |
+
+
+
+The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this report.
+
+The present document has not been subject to any approval process by the oneM2M Partners Type 1.  Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.
+
+
+
+About oneM2M 
+
+The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. 
+
+More information about oneM2M may be found at:  http//www.oneM2M.org
+
+
+
+Copyright Notification
+
+(c) 2020, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
+
+All rights reserved.
+
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+
+
+Notice of Disclaimer & Limitation of Liability 
+
+The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. 
+
+NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.
+
+
+# Contents
+
+[Contents](#contents)  
+[1 Scope](#1-scope)  
+[2 References](#2-references)  
+&nbsp;&nbsp;&nbsp;&nbsp;[2.1 Normative references](#21-normative-references)  
+&nbsp;&nbsp;&nbsp;&nbsp;[2.2 Informative references](#22-informative-references)  
+[3 Definition of terms, symbols and abbreviations](#3-definition-of-terms,-symbols-and-abbreviations)  
+&nbsp;&nbsp;&nbsp;&nbsp;[3.1 Terms](#31-terms)  
+&nbsp;&nbsp;&nbsp;&nbsp;[3.2 Symbols](#32-symbols)  
+&nbsp;&nbsp;&nbsp;&nbsp;[3.3 Abbreviations](#33-abbreviations)  
+[4 Conventions](#4-conventions)  
+[5 User defined clause(s) from here onwards](#5-user-defined-clause%28s%29-from-here-onwards)  
+&nbsp;&nbsp;&nbsp;&nbsp;[5.1 User defined subdivisions of clause(s) from here onwards](#51-user-defined-subdivisions-of-clause%28s%29-from-here-onwards)  
+[Proforma copyright release text block](#proforma-copyright-release-text-block)  
+&nbsp;&nbsp;&nbsp;&nbsp;[Annexes](#annexes)  
+[Annex &lt;A>:Title of annex](#annex-%26lta%3E%3Atitle-of-annex)  
+[Annex &lt;B>:Title of annex](#annex-%26ltb%3E%3Atitle-of-annex)  
+&nbsp;&nbsp;&nbsp;&nbsp;[    First clause of the annex](#----first-clause-of-the-annex)  
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[B.1.1    First subdivided clause of the annex](#b11----first-subdivided-clause-of-the-annex)  
+[Annex &lt;y>:Bibliography](#annex-%26lty%3E%3Abibliography)  
+[History](#history)  
+# 1 Scope
+The present document ...
+
+
+`EXAMPLE:    The present document provides the necessary adaptions to the endorsed document.`  
+
+<mark>The Scope shall not contain requirements.</mark>
+
+
+# 2 References
+<mark>The following text block applies.</mark>
+
+References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.
+
+
+## 2.1 Normative references
+<mark>As a Technical Report (TR) is entirely informative it shall not list normative references.</mark>
+
+The following referenced documents are necessary for the application of the present document.
+
+Not applicable.
+
+
+## 2.2 Informative references
+<mark>Clause 2.2 shall only contain informative references which are cited in the document itself.</mark>
+
+The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.
+
+- <a name="_ref_i.1">[i.1]</a>    oneM2M Drafting Rules  [https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc](https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc)
+
+
+# 3 Definition of terms, symbols and abbreviations
+<mark>Delete from the above heading the word(s) which is/are not applicable.</mark>
+
+
+## 3.1 Terms
+<mark>Clause numbering depends on applicability.</mark>
+
+
+-  <mark>A definition shall not take the form of, or contain, a requirement.</mark>
+-  <mark>The form of a definition shall be such that it can replace the term in context. Additional information shall be given only in the form of examples or notes (see below).</mark>
+-  <mark>The terms and definitions shall be presented in alphabetical order.</mark>
+
+For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:
+
+<mark>Definition format</mark>
+
+<mark>&lt;defined term>: &lt;definition></mark>
+
+<mark>If a definition is taken from an external source, use the format below where [N] identifies the external document which must be listed in Section 2 References.</mark>
+
+<mark>&lt;defined term>[N]: &lt;definition></mark>
+
+<mark>example 1: text used to clarify abstract rules by applying them literally</mark>
+
+> NOTE:    This may contain additional information.
+
+## 3.2 Symbols
+
+<mark>Clause numbering depends on applicability.</mark>
+
+For the purposes of the present document, the [following] symbols [given in ... and the following] apply:
+
+<mark>Symbol format</mark>
+
+<mark>`&lt;symbol>    &lt;Explanation>`</mark>  
+<mark>`&lt;2nd symbol>    &lt;2nd Explanation>`</mark>  
+<mark>`&lt;3rd symbol>    &lt;3rd Explanation>`</mark>  
+
+## 3.3 Abbreviations
+
+<mark>Abbreviations should be ordered alphabetically.</mark>
+
+<mark>Clause numbering depends on applicability.</mark>
+
+For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:
+
+<mark>Abbreviation format</mark>
+
+<mark>`&lt;ABBREVIATION1>    &lt;Explanation>`</mark>  
+<mark>`&lt;ABBREVIATION2>    &lt;Explanation>`</mark>  
+<mark>`&lt;ABBREVIATION3>    &lt;Explanation>`</mark>    
+
+# 4 Conventions
+
+The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules <a href="#_ref_i.1">[i.1]</a>
+
+
+# 5 User defined clause(s) from here onwards
+&lt;Text>
+
+
+## 5.1 User defined subdivisions of clause(s) from here onwards
+&lt;Text>
+
+<mark>The following text is to be used when appropriate:</mark>
+
+
+# <mark>Proforma copyright release text block</mark>
+<mark>This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.</mark>
+
+<mark>Notwithstanding the provisions of the copyright clause related to the text of the present document, oneM2M grants that users of the present document may freely reproduce the &lt;proformatype> proforma in this {clause|annex} so that it can be used for its intended purposes and may further publish the completed &lt;proformatype>.</mark>
+
+<mark>&lt;PAGE BREAK></mark>
+
+
+## <mark>Annexes</mark>
+<mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark>
+
+# Annex &lt;A>:<br />Title of annex 
+
+&lt;Text>
+
+<mark>&lt;PAGE BREAK></mark>
+
+# Annex &lt;B>:<br />Title of annex
+
+&lt;Text>
+
+## <!--B.1-->    First clause of the annex
+
+&lt;Text>
+
+### B.1.1    First subdivided clause of the annex 
+
+&lt;Text>
+
+<mark>&lt;PAGE BREAK></mark>
+
+# Annex &lt;y>:<br />Bibliography
+<mark>The annex entitled "Bibliography" is optional.</mark>
+
+<mark>It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the document itself.</mark>
+
+<mark>It shall not include references mentioned in the document.</mark>
+
+
+- <mark>&lt;Publication>: "&lt;Title>".</mark>
+
+<mark>OR</mark>
+
+<mark>&lt;Publication>: "&lt;Title>".</mark>
+
+<mark>&lt;PAGE BREAK></mark>
+
+
+# History
+<mark>This clause shall be the last one in the document and list the main phases (all additional information will be removed at the publication stage).</mark>
+
+
+|Publication history |Publication history |Publication history |
+|-|-|-|
+|V1.1.1 |&lt;yyyy-mm-dd> |&lt;Milestone> |
+| | | |
+| | | |
+| | | |
+| | | |
+
+
+
+
+
+
+|Draft history (to be removed on publication) |Draft history (to be removed on publication) |Draft history (to be removed on publication) |
+|-|-|-|
+|V1.1.1 |&lt;yyyy-mm-dd> |&lt;CR ID> applied - &lt;Summary of changes> |
+| | | |
+| | | |
+| | | |
+| | | |
+
+
+