Request Open: September 25, 2024 9:00 am — October 25, 2024 11:59 pm (20 days left)
The Open Geospatial Consortium (OGC) is seeking feedback and comments on the candidate OGC API – Connected Systems v1.0, and supporting modernized Sensor Web Enablement (SWE) candidate Standards, before they are adopted. Comments from non-members are encouraged. Comments are due by October 25, 2024. To better understand the candidate OGC API – Connected Systems Standard v1.0, reviewers are encouraged to read the Reviewers Guide.
The OGC API – Connected Systems Standard v1.0 connects sensors and sensing systems of all kinds with associated infrastructure systems on or around the Earth into a common 4D framework for the purposes of discovery, access, processing, reasoning, visualization, tasking, and action. Such sensing systems may include sensors, “things,” robots, drones, satellites, control systems, devices, and platforms across the domains of space, air, land, sea, cyber, and electromagnetic, including digital twins.
The OGC API – Connected Systems Standard v1.0 builds on the OGC API – Features Standard with additional mechanisms for retrieving static and dynamic data from other systems. It therefore also provides a single API to access content served by other OGC API Standards such as OGC API – Maps, OGC API – Coverages, OGC API – Environmental Data Retrieval (EDR), OGC API – 3D GeoVolumes/3D Tiles, SensorThings API (STA), OGC API – Moving Features, and/or OGC API – Processes.
The development of the OGC API – Connected Systems Standard v1.0 is borne from OGC’s strategic guidance to all Standards Working Groups (SWG) to migrate their specification baseline to OpenAPI/RESTful patterns. Specifically, the OGC Sensor Web Enablement (SWE) architecture, which has been in global use since 2007, needed to be updated according to this architectural guidance and advances in information technologies.
As with other OGC API Standards, the OGC API – Connected Systems Standard v1.0 is divided into several parts, providing modularity and flexibility without breaking compliance. Currently seeking public comment are Part 1: Feature Resources, and Part 2: Dynamic Data.
OGC API – Connected Systems – Part 1: Feature Resources defines resource types and encodings for providing metadata about systems and their deployments, as well as the procedures and sampling strategies used by these systems. Part 1 also defines additional filtering capabilities and requirements for Create/Replace/Delete/Update operations.
OGC API – Connected Systems – Part 2: Dynamic Data enables the streaming of dynamic ‘Data Streams of Observations’ and the tasking of systems via ‘Control Streams of Commands.’ There will be subsequent public comment review periods of future Parts 3, 4, and 5 (Pub/Sub, Sampling Feature Types, and Binary Encoding Formats, respectively). This will occur after the review and approval of Parts 1 and 2.
In support of this new OGC API – Connected Systems Standard v1.0, the underlying sensor Standards, SensorML v3.0 and SWE Common v3.0. are proposed for update. SensorML provides a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations by sensors and sensing systems. The SWE Common Data Model defines and packages sensor data in a self-describing and semantically enabled way.
To better understand the candidate OGC API – Connected Systems Standard v1.0, reviewers are encouraged to read the Reviewers Guide.
OGC Members interested in staying up to date on the progress of this Standard and related Standards, or contributing to their development, are encouraged to join the Connected Systems Standards Working Group via the OGC Portal. Non-OGC members who would like to know more about participating in this SWG are encouraged to contact the OGC Standards Program.
The candidate OGC API – Connected Systems Standard and Supporting SensorML and SWE Common Standards (bundled as a ZIP) are available for review and comment on the OGC Portal. Comments are due by October 25, 2024, and should be submitted via the method below.
To Comment:
Comments can be submitted as an issue on the OGC API – Connected Systems GitHub repository for a period ending on the “Close request date” listed above. Comments received will be consolidated and reviewed by OGC members for incorporation into the document.
