Public Comment Requested: Standard SensorThings API Part 1 - Sensing V1.1
The OGC SensorThings API provides an open, geospatially enabled, unified way to interconnect Internet of Things (IoT) devices, data, and applications over the web. SensorThings is currently being used by organizations around the world in support of logistics, public safety, energy utilities, environmental monitoring, and more.
At a high level, the OGC SensorThings API provides two main functionalities, with each function handled by a specific part of the standard: Sensing and Tasking.
Under public comment is a new version (v1.1) of the Sensing part, which provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The separate Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as sensors or actuators.
Version 1.1 of the SensorThings API is mostly backwards compatible with v1.0. The main changes in v1.1 include:
- An additional field for storing additional metadata that is useful for filtering.
- Additions to the service root page that allow users to easily see exactly which extensions and optional features a server implements. Additionally, the MQTT extension can now list the MQTT endpoints on the root page so that a user can discover those endpoints.
- A fix for inconsistencies and incompatibilities surrounding the transmission of the specification version number in MQTT topics.
The first two changes should not impact clients implemented based on version 1.0. The third change, however, may cause some minor issues for some clients that are not using the version prefix in MQTT topics.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template