actio OGC® Sensor Planning Service Implementation Standard

144 Copyright © 2011 Open Geospatial Consortium Message Facet a Action URI a Applicable in feature Y=yes, N=no SOAP 1.1 SOAPActio n SOAP

1.2 actio

n WS- Addressing [action] GetTask response http:www.opengis.netsps2.0 GetTaskResponse N N Y Reserve request http:www.opengis.netsps2.0 Reserve Y Y Y Reserve response http:www.opengis.netsps2.0 ReserveResponse N N Y Submit request http:www.opengis.netsps2.0 Submit Y Y Y Submit response http:www.opengis.netsps2.0 SubmitResponse N N Y Update request http:www.opengis.netsps2.0 Update Y Y Y Update response http:www.opengis.netsps2.0 UpdateResponse N N Y a Although some values listed in the column appear to contain spaces, they shall not contain spaces. NOTE The action URIs for the messages defined by the SWE Service Model and WS-Notification are not listed here – they can be found in table 35 of [OGC 09-001] and the according paragraphs of WS- Notification. Clause 9.6 provides example XML instances for operation requests and responses, some of which are wrapped by a SOAP envelope. These examples make use of the action URIs defined in this section. Table 69 — Action URI for SPS exceptionsfault types ExceptionFault type WS-Addressing [action] message addressing property value Exception defined by SPS http:www.opengis.netsps2.0Exception Copyright © 2011 Open Geospatial Consortium 145

9.4 Realization of PublishSubscribe

Requirement http:www.opengis.netspecSPS2.0reqSOAPPubSub REQ 112. In the SOAP binding of this service, PublishSubscribe functionality shall be implemented as defined in clause 19.4 of [OGC 09-001]. Clause 9.6 provides example XML instances for subscribing to and being notified of SPS events.

9.5 Realization of Asynchronous RequestResponse

Requirement http:www.opengis.netspecSPS2.0reqSOAPWSAdressing REQ 113. As defined in clause 19.4 of [OGC 09-001], an implementation of this standard shall use WS-Addressing to enable asynchronous request-response in the SOAP binding of the service. The behavior for handling asynchronous tasking responses shall be compliant to section 7.3.1.3. Requirement http:www.opengis.netspecSPS2.0reqSOAPAnonymousURI REQ 114. If a client used the anonymous-URI see 09-032 section 10.2 as value of the wsa:ReplyTo property in the SOAP header of a tasking request – and the service supports the anonymous-URI feature – then the tasking response shall be sent in the synchronous backchannel of the transport protocol e.g. the HTTP response message. If a client used the none-URI see 09-032 section 10.2 as value of the wsa:ReplyTo property in the SOAP header of a tasking request then the service can discard any operation response that would normally be generated, as the client is not receiving it anyway. Only the response requirements of the underlying communication protocol need to be satisfied, e.g. in case of HTTP an HTTP response message has to be returned.

9.6 SPS Examples Scenario

In the following, a scenario of tasking a pan, tilt, zoom camera is elaborated with XML examples.