@@ -45,26 +45,23 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
# Contents
# 1 Scope
The present document discusses how key features of the NGSI-LD API can be integrated in oneM2M.
The present document discusses how key features of the NGSI-LD API can be integrated in oneM2M and studies the impacts and necessary changes to oneM2M Specifications in particular in regard to the following.
In particular, the present document
- studies the impacts and necessary changes to oneM2M Specifications in particular with regards to the subsequent bulltets
The present document
- describes the additional functionality that the integration of NGSI-LD API and its related functionality can bring to the oneM2M standard, including the resulting integrated use cases.
- studies solutions for the architectural integration of NGSI-LD and its related functionalities into oneM2M, in particular with respect to oneM2M reference points and the existing oneM2M Common Service Functions.
- studies the mapping of the information stored in oneM2M resources to the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may lead to an evolution of the current NGSI-LD and Mca, and the related information models.
- studies the mapping of the information stored in oneM2M resources to the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may suggest changes to the current NGSI-LD and Mca, and the related information models.
- studies the integration of NGSI-LD into oneM2M’s management and security frameworks, in particular for registration, authentication, access control and device management.
# 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>
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.
The following referenced documents are necessary for the application of the present document.
Not applicable.
...
...
@@ -73,6 +70,8 @@ Not applicable.
## 2.2 Informative references
<mark>Clause 2.2 shall only contain informative references which are cited in the document itself.</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.
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.
@@ -146,11 +145,13 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
### 5.3.1 Overview
<mark>The NGSI-LD resource structure will be introduced here or in an additional subclause. </mark>
### 5.3.2 Query operations
### 5.3.2 Subscription/notification operations
### 5.3.3 Subscription/notification operations
### 5.3.3 Management operations
### 5.3.4 Management operations
## 5.4 Architectural considerations
...
...
@@ -162,9 +163,9 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
<mark>Study solutions for the architectural integration of NGSI-LD and its related functionalities into oneM2M, in particular with respect to oneM2M reference points and the existing oneM2M Common Service Functions.</mark>
# 8 Mapping of information stored in oneM2M resources to the NGSI-LD information model
# 8 Mapping between the information stored in oneM2M resources and the NGSI-LD information model
<mark>Study the mapping of the information stored in oneM2M resources to the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may lead to an evolution of the current NGSI-LD and Mca, and the related information models.</mark>
<mark>Study the mapping between the information stored in oneM2M resources and the NGSI-LD information model. This includes, but is not limited to the current oneM2M semantic models (in particular SDT and the oneM2M base ontology, including SAREF integration) to the NGSI-LD information model, with the goal of making it available through an integration of NGSI-LD API and the Mca reference point. This may lead to an evolution of the current NGSI-LD and Mca, and the related information models.</mark>
# 9 Integration of NGSI-LD into oneM2M's management and security frameworks
