From b2fb49cbf5ada29da84f42d1c2c88cc6ca5d48a5 Mon Sep 17 00:00:00 2001
From: Ingo Friese <ingo.friese@telekom.de>
Date: Thu, 6 Feb 2025 10:38:32 +0000
Subject: [PATCH] typo 1
---
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 7a27d09..7bb4af1 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -204,7 +204,7 @@ Both directions of the data flow between the OGC/STA server and the IPE require
#### 6.3.1.1 Communication direction OGC/STA Server towards IPE
-In Figure 6.3.1.1-1, an OGC/STA client is connected to an OGC/STA server, and its data is forwarded to the IPE. he OGC/STA client publishes data to the OGC/STA server via an HTTP-POST message. The 'result' attribute of an "Observation" contains the sensor data.
+In Figure 6.3.1.1-1, an OGC/STA client is connected to an OGC/STA server, and its data is forwarded to the IPE. The OGC/STA client publishes data to the OGC/STA server via an HTTP-POST message. The 'result' attribute of an "Observation" contains the sensor data.
An "Observation" according to STA Sensing Entities Data Model <a href="#_ref_i.1">[i.1]</a> belongs to a "Datastream" (see Figure 5-2).
The IPE shall subscribe to the relevant "Datastream" at the MQTT-Broker of the OGC/STA Server using its specific URL or topic like e.g. {"sta-example-server-address.com/v1.0/Datastreams(8715)"}. After subscribing, the IPE receives every "Observation" that is pushed to that "Datastream".
--
GitLab