SDS-2025-0016R02-ogc_ipe_configuration_aspects

Coversheet	Value
Meeting ID	TP#68
Work-item	WI-0100
Reason	rewordings & more precise descriptions

TS-0041-oneM2M-SensorThings_interworking.md

@@ -220,7 +220,7 @@ When a "Datastream" is created on the OGC/STA server, a reference ID (e.g. {"@io
 
 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, for example, from the "Label" or "ResourceName" attributes of the corresponding oneM2M `<container>` or if existing, from the corresponding `<AE>` 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>.
 
-Once the destination-"Datastream" is created, the IPE can send "Observations" to the OGC/STA server as HTTP POST messages. An interested OGC/STA client can subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server to receive each "Observation" forwarded by the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to retrieve the data as needed.
+Once the destination-"Datastream" is created, the IPE can send an "Observation" to the OGC/STA server as HTTP POST messages. An interested OGC/STA client can subscribe to the destination-"Datastream" at the MQTT Broker of the OGC/STA server to receive each "Observation" forwarded by the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to retrieve the data as needed.
 
 ![Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client](media/config_ogc2.png)