From c851847b44939504b4a467eca728ed3fe31d8b99 Mon Sep 17 00:00:00 2001 From: Ingo Friese <ingo.friese@telekom.de> Date: Wed, 22 Jan 2025 12:02:59 +0000 Subject: [PATCH] data formats --- 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 755b47a..99cee81 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -179,7 +179,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 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 <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 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