Backticks changed

TS-0041-oneM2M-SensorThings_interworking.md

@@ -180,7 +180,7 @@ 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 `<contentInstan2ce>`;, and vice versa as shown in Figure 6.1-1. The data type of the 'result' field of an "Observation" is acording to SensorThings API <a href="#_ref_i.1">[i.1]</a> 'any' and depends on the 'observationType' defined in the associated "Datastream". The 'content' attribute of an oneM2M instance may be opaque data <a href="#_ref_3">[3]</a> understandable with the help of the 'contentInfo' attribute. The 'contentInfo' attribute on the oneM2M side may be added by the IPE. The original timestamps, present in the "Observation" as 'phenomenonTime' and in the &lt;contentInstance&gt; as "creationTime," shall be discarded. These timestamps are to be reset by the OGC /STA server and the CSE, respectively. They may be transmitted for informational purposes as part of the 'result' or the 'content' fields.
+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 data type of the 'result' field of an "Observation" is acording to SensorThings API <a href="#_ref_i.1">[i.1]</a> 'any' and depends on the 'observationType' defined in the associated "Datastream". The 'content' attribute of an oneM2M instance may be stringified data <a href="#_ref_3">[3]</a> understandable with the help of the 'contentInfo' attribute. The 'contentInfo' attribute on the oneM2M side may be added by the IPE. The original timestamps, present in the "Observation" as 'phenomenonTime' and in the `<contentInstance>` as "creationTime," shall be discarded. These timestamps are to be reset by the OGC /STA server and the CSE. They may be transmitted for informational purposes as part of the 'result' or the 'content' fields.
 
 ![Figure 6.1-1: OGC / STA-to-oneM2M data model mapping](media/data_mapping.svg)
 
@@ -188,14 +188,14 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
 
 ## 6.2 Communication Flow
 
-Figure 6.2-1 shows the oneM2M-to-OGC/STA direction. In order to transfer data from a oneM2M sensor to OGC/STA the IPE creates a &lt;subscription&gt; to the &lt;container&gt; resource in the CSE containing the desired data. Triggert by a sensor event a new &lt;contentInstance&gt; is added to the &lt;container&gt; by the &lt;AE&gt;. The IPE gets a &lt;notification&gt; message containing the &lt;contentInstance&gt; resource.
-The IPE constructs an "Observation" creation request and copies the 'content' attribute of the &lt;contentInstance&gt; to the 'result' attribute of the "Observation" and sends it to a "Datastream" to be created as detailed in Section 6.3.1 at the OGC/STA server. The OGC/STA applcation gets the sensor data either by polling the OGC/STA server or subscribing to the regarded "Datastream" at the MQTT broker of the OGC/STA server.
+Figure 6.2-1 shows the oneM2M-to-OGC/STA direction. In order to transfer data from a oneM2M sensor to the OGC/STA server the IPE creates a `<subscription>` to the `<container>` resource in the CSE containing the desired data. Triggert by a sensor event a new `<contentInstance>` is added to the `<container>` by the `<AE>`. The IPE gets a `<notification>` containing the `<contentInstance>` resource.
+The IPE constructs an "Observation" creation request and copies the 'content' attribute of the `<contentInstance>` to the 'result' attribute of the "Observation" and sends it to a "Datastream" to be created as detailed in Section 6.3.1 at the OGC/STA server. The OGC/STA applcation gets the sensor data either by polling the OGC/STA server or subscribing to the regarded "Datastream" at the MQTT broker of the OGC/STA server.
 
 ![Figure 6.2-1: Communication oneM2M-to-OGC/STA direction](media/com_flow_1.png)
 
 **Figure 6.2-1: Communication oneM2M-to-OGC/STA direction** 
 
-Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. The IPE subscribes to the desired "Datastream" of the MQTT-Broker at the OGC/STA server. The OGC/STA server publishes a new "Observation" via the MQTT broker triggert by a Sensor Thing API sensor. The IPE creates a &lt;contentInstance&gt; in a container, to be created as detailed in Section 6.3.2 in the CSE and copies the 'result' attribute of the "Observation" to the 'content' attribute of the &lt;contentInstance&gt;. The oneM2M applcation gets the sensor data either by polling the CSE or subscribing to the desired &lt;container&gt; at the CSE.
+Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. The IPE subscribes to the desired "Datastream" of the MQTT-Broker at the OGC/STA server. The OGC/STA server publishes a new "Observation" via the MQTT broker triggert by a OGC/STA sensor. The IPE creates a `<contentInstance>` in a container, to be created as detailed in Section 6.3.2 in the CSE and copies the 'result' attribute of the "Observation" to the 'content' attribute of the `<contentInstance>`. The oneM2M applcation gets the sensor data either by polling the CSE or subscribing to the desired `<container>` at the CSE.
 
 ![Figure 6.2-2: Communication OGC/STA-to-oneM2M direction](media/com_flow_2.png)