From ff9c418416f89ed2a1bc038d4c9c78e855657e7d Mon Sep 17 00:00:00 2001
From: Ingo Friese <ingo.friese@telekom.de>
Date: Thu, 6 Feb 2025 10:35:58 +0000
Subject: [PATCH] spell check
---
TS-0041-oneM2M-SensorThings_interworking.md | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md
index e9b583e..7a27d09 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -190,24 +190,24 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
### 6.3.0 Introduction
-In order to enable interworking, preparation is needed in both oneM2M-CSE and OGC/STA server (Figure 6.3.0-1).
+In order to enable interworking, preparation is needed for both the oneM2M-CSE and the OGC/STA server (Figure 6.3.0-1).
**Figure 6.3.0-1: Both sides of the IPE configuration**
-### 6.3.1 Configuration of OGC/STA Server side
+### 6.3.1 Configuration of OGC/STA Server Side
#### 6.3.1.0 Overview
-Both directions of the data flow between OGC/STA server and the IPE need their own configuration steps.
+Both directions of the data flow between the OGC/STA server and the IPE require their own configuration steps.
#### 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. The OGC/STA client publishes data to the OGC/STA server via a 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. 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.
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 doing that the IPE receives every "Observation" that is pushed to that "Datastream".
+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".
@@ -215,13 +215,12 @@ The IPE shall subscribe to the relevant "Datastream" at the MQTT-Broker of the O
#### 6.3.1.2 Communication direction IPE towards OGC/STA Server
-The IPE requires a destination-"Datastream" in order to send an "Observation". In case there is no associated "Datastream" on the OGC/STA server it shall be created. This may be done beforehand or at start-up time of the IPE and is up to the implementation.
-When a "Datastream" is created at the OGC/STA server a reference ID (e.g. {"@iot.id:3635353"}) is given back.
-This reference is needed by the IPE to relate an "Observation" to a "Datastream" and shall be available during IPE operation. Appart from the "Datastream" additional entities of the OGC data model like e.g. "Location" or "Sensor" may be created.
+The IPE requires a destination-"Datastream" in order to send an "Observation". If no associated "Datastream" exists on the OGC/STA server, it shall be created. This can be done beforehand or at the IPE's start-up time and is up to the implementation.
+When a "Datastream" is created on the OGC/STA server, a reference ID (e.g. {"@iot.id:3635353"}) is returned. This reference is needed by the IPE to relate an "Observation" to a "Datastream" and shall be available during IPE operation. Apart from the "Datastream," additional entities of the OGC data model, such as "Location" or "Sensor," may be created.
-The creation of entities like "Datastream" and "Thing" requires a number of mandatory properties that shall be known at configuration time, e.g. 'name' and 'description'. These property fields may automatically derived e.g. from the "Label" or "ResourceName" attributes of the regarded oneM2M `<AE>` or `<container>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
+The creation of entities like "Datastream" and "Thing" requires several mandatory properties that shall be known at configuration time (e.g., 'name' and 'description'). These property fields may automatically derived e.g. from the "Label" or "ResourceName" attributes of the regarded oneM2M `<AE>` or `<container>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
-When "Thing" and "Datastream" entities are created the IPE is able to send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA Client can now subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and thus getting every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1). Alternativly the OGC/STA client MAY use a HTTP-GET request to pull the data when needed.
+Once the "Thing" and "Datastream" entities are created, the IPE can send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA client can then subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and receive every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to pull the data as needed.
--
GitLab