Introduction Data Types Submit Operation

Co Figure 19 — Data types of the Submit operation The details of the operation request and response are explained in the following sub clauses. pyright © 2011 Open Geospatial Consortium 67 68 Copyright © 2011 Open Geospatial Consortium

7.3.5.3 Operation Request - Submit

Sending an instance of the Submit data type to the service performs an SPS Submit operation request. The Submit data type is derived from the TaskingRequest data type see clause 7.3.1.3 and therefore inherits all the properties contained in that data type. Submit neither restricts the content model of TaskingRequest nor adds additional properties. Requirement http:www.opengis.netspecSPS2.0reqSubmitRequestdataType REQ 51. The Submit data type shall contain the properties defined for the TaskingRequest data type.

7.3.5.4 Operation Response - SubmitResponse

The SubmitResponse data type represents the response to an SPS Submit operation request. The SubmitResponse data type is derived from the TaskingResponse data type see clause 7.3.1.4 and therefore inherits all the properties contained in that data type. SubmitResponse neither restricts the content model of TaskingResponse nor adds additional properties. Requirement http:www.opengis.netspecSPS2.0reqSubmitResponsedataType REQ 52. The SubmiResponse data type shall contain the properties defined for the TaskingResponse data type. A SubmitResponse contains a StatusReport see clause 7.3.1.5 to inform about the result of the requested operation. As a Submit request is a tasking request, the final result of that request might not be directly available and would then be Pending. The contents of the StatusReport properties after all possible state transitions are defined in table Table 31. If the request is reported to be pending then a client needs to retrieve information about the final status of the request in another way, per default by the GetStatus operation. Co Table 31 – StatusReport usage for different state transitions of a Submit request task is in execution task is already completed 1 task is in execution task is already completed 1 task 1 estimatedT oC 0..1 NA optional NA NA optional NA NA NA event code 0..1 NA TaskSub mitted TaskComp leted NA TaskSub mitted TaskCom pleted NA TaskingRe questExpir ed percentCo mpletion 0..1 NA 100 NA 100 NA NA procedure 1 requestStat us code 1 Pending Accepted Accepted Rejected Accepted Accepted Rejected Rejected statusMes sage 0.. taskingPar ameters 0..1 taskStatus code 0..1 NA InExecuti on Completed NA InExecuti on Complete d NA NA updateTim e 1 alternative StatusRep ort encoded as Reservatio nReport Applicable in Submit Response yes yes yes yes no no no no service may provide additional information to client in human readable form NA Initial → Accepted Initial → Rejected Initial → Pending NA = not applicable, means element is not used in response Notes: 1 this is a shortcut to convey information in the SubmitResponse that the Submit request was accepted and the submitted task already made the transitions Initial → InExecution and InExecution → Final TaskCompleted may be provided by service NA property name cardinality new identifier provided by service Pending → Accepted Submit Request State Transitions From → To Pending → Rejected Pending → Rejected request expired point in time when transition was made identifier previously provided by service identifier of procedure for which Submit request was made pyright © 2011 Open Geospatial Consortium 69