diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index 187d05e994acfcfa1295bd28fc1799fff07d3d4f..b6770850b2992f6bb0a9267b97216d960f7d8cce 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -139,7 +139,6 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in # 5 Introduction to OGC SensorThings API - The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is devided in two parts. SensorThings API Part 1 is dedicated to sensing and was published in 2016 and updated in 2021. A STA-based architecture works in client/server mode. A sensor device pushes data to the SensorThings Server via HTTP. A SensorThings Server may also support MQTT protocol to support publish and subscribe capabilities. An interested application can subscribe to the MQTT-Broker, in order to get notified about new sensor events. @@ -153,14 +152,12 @@ The data in the SensorThings server are organized as according to **Sensing Ent **Figure 5-2 STA Sensing Entities Data Model** -In the Sensing Entities Data Model events or sensor data are called "observations". Before a sensor is able to push an observation to the server it needs at least a 'Thing' and a 'Datastream' entity. This has to be created beforehand. One 'Thing' might have different 'Sensors', one 'Location' or many 'HistoricalLocations'. +In the Sensing Entities Data Model events or sensor data are called "observations". Before a sensor is able to push an "Observation" to the server it needs at least a "Thing" and a "Datastream" entity. This has to be created beforehand. One "Thing" might have different "Sensors", one "Location" or many "HistoricalLocations". -The Sensing Entities data model and the purpose of data within the data model discloses mainly two data characteristics, associated with a 'thing': +The Sensing Entities data model and the purpose of data within the data model discloses mainly two data characteristics, associated with a "Thing": - Data observations originated by sensors or commands sent to interact with actuators may be seen as IoT data from oneM2M point of view. While: -- Data embedded in the Sensing Entities Data Model, like "historic locations" should be seen as data for documentation purposes. - - +- Data embedded in the Sensing Entities Data Model, like "HistoricalLocations" should be seen as data for documentation purposes. # 6 Architecture Model of OGC/STA to oneM2M interworking