Sensor Planning Service SPS SPS EO Profile Sensor Observation Service SOS

Copyright © 2009 Open Geospatial Consortium, Inc. 31 receive a confirmation about this as a synchronous result of the request. After processing is finished, the service could send the response to the client. But this obviously requires the client to provide a network endpoint to establish a communication. The latter implementation also requires the use of unique message IDs that are protected towards integrity, so that the calling and responding service can reference the request and the response, not exchanged within the same communication. The notification communication pattern is described in [71] section 3.24 S200 Event notification, such that ―An application subscribes to notifications of certain named events from an event source. When such events occur, notifications are sent back to the originating application first party notification or to another application third party notification.‖ [71]. This pattern actually requires a subscription of the receiver to the sensor of the event that can be implemented according to the requestresponse communication pattern. The actual notification can according to [71] be implemented according to the ―fire-and-forget to multiple receivers scenario‖ also described in [71], section S002. This scenario does not guarantee the delivery to the sender, as it is implemented without acknowledgment from the receiver to the sender. The implementation can be based on any distribution technology. One popular implementation is XMPP, but also SOAP-enabled event receiver services are possible, so long the implementation manages to send notifications to subscribed receivers only.

9.3 Interface Summary for Baseline Services

9.3.1 Sensor Planning Service SPS

Operation name Input encoding Output encoding HTTP Binding GetCapabilities KVP or valid XML Valid XML GET or POST GetFeasibility Valid XML Valid XML POST Submit Valid XML Valid XML POST GetStatus Valid XML Valid XML POST Update Valid XML Valid XML POST Cancel Valid XML Valid XML POST DescribeResultAccess Valid XML Valid XML POST DescribeTasking Valid XML Valid XML POST Table 1 – SPS operation summary Summary: All operations can be invoked by a valid XML request and return a valid XML 32 Copyright © 2009 Open Geospatial Consortium, Inc. document using the HTTP POST binding and adhere to the requestresponse communication pattern.

9.3.2 SPS EO Profile

A SPS EO Profile supports all SPS operations as listed above, plus the following: Operation name Input encoding Output encoding HTTP Binding DescribeGetFeasibility Valid XML Valid XML POST DescribeSensor Valid XML SensorML POST EstimateSenorWorkload Valid XML Valid XML + SensorML POST DescribeSubmit Valid XML Valid XML POST Table 2 – SPS-EO Profile operation summary Summary: All operations can be invoked by a valid XML request and return a valid XML document using the HTTP POST binding. Different to the SPS core specification see above is that the GetFeasibility and Submit operations operate according to the notification communication pattern. The invocation of the operation GetFeasibility or Submit is used to subscribe to the SPS and the GetFeasibiltiyResponse or the SubmitRespnse message represents the notification.

9.3.3 Sensor Observation Service SOS

Operation name Input encoding Output encoding HTTP binding GetCapabilities KVP or Valid XML Valid XML GET or POST GetObservation Valid XML OM POST DescribeSensor Valid XML TML or SensorML POST GetObservationById Valid XML OM POST GetResult Valid XML OM POST Copyright © 2009 Open Geospatial Consortium, Inc. 33 DescribeResultModel Valid XML Valid XML POST GetFeatureOfInterest Valid XML GML POST GetFeatureOfInterestType Valid XML GML POST DescribeObservationType Valid XML Valid XML POST DescribeFeatureType Valid XML Valid XML POST RegisterSensor TML or SensorML + OM document Valid XML POST InsertObservation OM Valid XML POST Table 3 – SOS operation summary : Mandatory for transaction profile : plus an OM instance template document from previous GetObservation Summary: All operations can be invoked by a valid XML request and return a valid XML document using the HTTP POST binding and leverage the requestresponse communication pattern.

9.3.4 Sensor Alert Service SAS