From 0e89b5b291a5c67dcf7ccba17de1e797faf73cb2 Mon Sep 17 00:00:00 2001 From: Ingo Friese <ingo.friese@telekom.de> Date: Tue, 4 Feb 2025 09:38:22 +0000 Subject: [PATCH] test backticks --- TS-0041-oneM2M-SensorThings_interworking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index b41286a..40efddc 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/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 `<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 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 <contentInstance> 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 `<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 <contentInstance> 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.  -- GitLab