Contribution SDS-2024-0133-TS-0041-SensorThings_interworking-v5_1_0_baseline merged into R5

Original contribution: SDS-2024-0133-TS-0041-SensorThings_interworking-v5_1_0_baseline

See merge request !8

TS-0041-oneM2M-SensorThings_interworking.md

-![logo](media/image1.png)
+![~~CAPTION~~](media/image1.png)
 
 |oneM2M<br/>Technical Specification |oneM2M<br />Technical Specification |
 |-|-|
-|Document Number |TS-0041-V-5.0.0 |
+|Document Number |TS-0041-V-5.1.0 |
 |Document Name: |oneM2M-SensorThings Interworking<br /> |
-|Date: |2024-03-01 |
+|Date: |2024-09-13 |
 |Abstract: |&lt; An abstract of the specification and information that may be used in subsequent electronic searches> |
 |Template Version: | January 2020 (do not modify) |
 
@@ -38,20 +38,7 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
 
 
 # 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\(s\)-from-here-onwards)  
-&nbsp;&nbsp;&nbsp;&nbsp;[5.1 User defined subclause(s) from here onwards](#51-user-defined-subclause\(s\)-from-here-onwards)  
-[Annex &lt;y>: Bibliography](#annex-&lt;y>:-Bibliography)  
-[History](#history)
+
 
 # 1 Scope
 The present document ...
@@ -152,20 +139,18 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
 # 5 Introduction to OGC SensorThings API
 
 
-The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is devided in two parts. SensorThings API Part 1 is dedicated to sensing and was published in 2016 and updated in 2021 <a href="#_ref_1">[1]</a>.    
+The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is devided in two parts. SensorThings API Part 1 is dedicated to sensing and was published in 2016 and updated in 2021.    
 A STA-based architecture works in client/server mode. A sensor device pushes data to the SensorThings Server via HTTP. A SensorThings Server may also support MQTT protocol to support publish and subscribe capabilities. An interested application can subscribe to the MQTT-Broker, in order to get notified about new sensor events.
 
-<figure>
-  <img src="media/STA_flow.png" alt="STA_message_flow">
-  <figcaption>Figure 5-1 STA message flow</figcaption>
-</figure>
+![Figure 5-1 STA message flow](media/STA_flow.png)
+
+**Figure 5-1 STA message flow** 
+
+The data in the SensorThings server are organized as according to  **Sensing Entities** (see Figure 5-2: Sensing Entities data model.
 
-The data in the SensorThings server are organized as according to  **Sensing Entities** (see Figure 5.0-1: Sensing Entities data model <a href="#_ref_1">[1]</a>).
+![Figure 5-2 STA Sensing Entities Data Model](media/data_model.jpg)
 
-<figure>
-  <img src="media/data_model.jpg" alt="data_model">
-  <figcaption>Figure 5-1 STA Sensing Entities Data Model <a href="#_ref_1">[1]</a></figcaption>
-</figure>
+**Figure 5-2 STA Sensing Entities Data Model** 
 
 In the Sensing Entities Data Model events or sensor data are called "observations". Before a sensor is able to push an observation to the server it needs at least a 'Thing' and a 'Datastream' entity. This has to be created beforehand. One 'Thing' might have different 'Sensors', one 'Location' or many 'HistoricalLocations'.
 
@@ -184,10 +169,9 @@ Figure 6.0-1 shows an architecture approach for an Interworking Proxy Entity (IP
 
 The basic interworking enables applications that are connected to an oneM2M-based system to get data from sensors that are connected to an OGC/STA server. Furthermore, an application that is connected to an OGC/STA server will be able to get data from sensors that are connected to an oneM2M-based system.
 
-<figure>
-  <img src="media/STA_oneM2M_architekturbild_01.svg" alt="arch_overview">
-  <figcaption>Figure 6.0-1: IPE architecture overview</figcaption>
-</figure>
+![Figure 6.0-1: IPE architecture overview](media/STA_oneM2M_architekturbild_01.svg)
+
+**Figure 6.0-1: IPE architecture overview** 
 
 ## 6.1 OGC/STA-to-oneM2M Data Model Mapping
 
@@ -195,13 +179,11 @@ According to oneM2M TS-0033 <a href="#_ref_2">[2]</a> a representation of a non-
 - sensor (IoT-data); and 
 - administrative data (like historic locations or historic products IDs).
 
-The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'content' attribute of a oneM2M <contentInstance>, and vice versa as shown in Figure 6.1-1.
+The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'content' attribute of a oneM2M &lt;contentInstance&gt;, and vice versa as shown in Figure 6.1-1.
 
-<figure>
-  <img src="media/data_mapping.svg" alt="data_mapping">
-  <figcaption>Figure 6.1-1: OGC / STA-to-oneM2M data model mapping</figcaption>
-</figure>
+![Figure 6.1-1: OGC / STA-to-oneM2M data model mapping](media/data_mapping.svg)
 
+**Figure 6.1-1: OGC / STA-to-oneM2M data model mapping** 
 
 <mark>The following text is to be used when appropriate:</mark>
 
@@ -283,7 +265,7 @@ OR
 |Version (to be removed on publication) |Date (to be removed on publication) |Draft history (to be removed on publication) |
 |-|-|-|
 |V5.0.0 | 2024-03-01|Includes the following contributions agreed during SDS#58 meeting: 	SDS-2023-0219R01-initial_OGC_intro|
-| | | |
+|V5.1.0 | 2024-09-13|Includes the following contributions agreed during SDS#66 meeting: SDS-2024-0064R02_architecture_model and editorials agreed during SDS66|
 | | | |
 | | | |
 | | | |