Copyright © 2011 Open Geospatial Consortium 181
Table 70 — Connections of the Scheduled state
Connector type name
Source state
Target state
Notes Transition
TaskCancellation Scheduled
Final State If supported by the service, a client may
cancel a scheduled task. A service may reject a cancellation
request. Data gathered and published for such a
task should not automatically be deleted so that a client can at least retrieve the
data that was gathered until the task was cancelled.
If supported, the service shall notify interested consumers about this event.
Transition
TaskFailure Scheduled
Final State If the service is not able to perform a
scheduled task as planned, the task fails. If supported, the service shall notify
interested consumers about this event.
10.1.2.2 InExecution State
A task that enters this state is executed by the service. The service starts the internal processing of the request.
182 Copyright © 2011 Open Geospatial Consortium
Table 71 — Connections of the InExecution state
Connector type name
Source state
Target state
Notes Transition
TaskCompletion InExecution Final State
If a task is completed as planned, it is finalized.
If supported, the service shall notify interested consumers about this event.
Transition
ExecutingTaskU pdate
InExecution InExecution If a tasking request to update a task that is in the state InExecution is feasible, the
update shall be performed and the task shall remain or transition back into
InExecution
state. Whether the update results in the
transition to the previous substate of InExecution
or in the transition to a new substate is not further specified here.
This behavior can be specified by an SPS extensionprofile that defines new
substates of InExecution.
If supported, the service shall notify interested consumers about this event.
Transition
DataPublication InExecution InExecution New data was gathered for the task and
published by the service - meaning that a client can now access the new data.
If supported, the service shall notify interested consumers about this event.
Transition
TaskConfirmatio n
Reserved InExecution A reserved
task that is confirmed by the client shall transition into InExecution
state. If supported, the service shall notify
interested consumers about this event.
Transition
TaskSubmission Tasking
Request Choice
InExecution A feasible tasking request with the intention to submit a task enters
InExecution state.
Note: a service can support notification that a task was submitted by implementing the
TaskingRequestAccepted event see Table 64.
Copyright © 2011 Open Geospatial Consortium 183
10.1.2.3 Reserved State
This state represents a task that has successfully been reserved at the service. The service blocks all resources required to execute the task as long as the reservation has not
expired.
The reserved task may be updated if the update is feasible - if it is not feasible the task does not change its state.
If a successful confirmation of the reserved task can no longer be guaranteed, the task fails.
Table 72 — Connections of the Reserved state
Connector type name
Source state
Target state
Notes Transition
TaskReservation Tasking
Request Choice
Reserved A feasible tasking request with the
intention to reserve a task enters the Reserved
state.
Note: a service can support notification that a task was reserved by implementing the
TaskingRequestAccepted event see Table 64.
Transition
ReservedTaskUpd ate
Reserved Reserved If a tasking request to update a reserved
task is feasible, the update shall be performed and the task shall remain or
transition back in Reserved state.
If supported, the service shall notify interested consumers about this event.
Transition
ReservationExpira tion
Reserved Final State If a reserved task expired, it shall be
finalized by the service. If supported, the service shall notify
interested consumers about this event.
Transition
TaskConfirmation Reserved InExecution A
reserved task that is confirmed by the
client shall transition into InExecution state.
If supported, the service shall notify interested consumers about this event.
10.1.2.4 Tasking Request Choice
Which substate of the Scheduled state is entered by a new task depends on the semantics of the tasking request. If the tasking request was sent with the intention to reserve a task
184 Copyright © 2011 Open Geospatial Consortium then the substate will be Reserved. If the intention was to submit a task then the substate
will be InExecution.
Table 73 — Connections of the Tasking Request choice
Connector type name
Source state
Target state
Notes Transition
TaskReservation Tasking
Request Choice
Reserved A feasible tasking request with the
intention to reserve a task enters the Reserved
state.
Note: a service can support notification that a task was reserved by implementing the
TaskingRequestAccepted event see Table 64.
Transition
TaskSubmission Tasking
Request Choice
InExecutio n
A feasible tasking request with the intention to submit a task enters the
InExecution state.
Note: a service can support notification that a task was submitted by implementing the
TaskingRequestAccepted event see Table 64.
Transition
TaskReservationO rSubmission
Initial State Tasking Request
Choice A feasible tasking request with the
intention to reserve or submit an implied task automatically enters the Scheduled
state.
10.1.2.5 Final State
A task that was completed, has expired, was cancelled or has failed is in its final state. The service does not allow any confirmation, update or cancellation of a finalized task.
An exception with ModificationOfFinalizedTask code will be thrown if one of these requests is received for a finalized task. An InvalidParameterValue exception is thrown if
the task identifier in the request is unknown to the service.
