Final State Initial State

Copyright © 2011 Open Geospatial Consortium 185 Table 74 — Connections of the Final 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 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 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 TaskFailure Scheduled Final State If the service is not able to perform a scheduled task as planned, the task shall fail. If supported, the service shall notify interested consumers about this event.

10.1.2.6 Initial State

Once a tasking request with the intention to reserve or submit is received by the service and the implied task is feasible, a task gets scheduled by the service. 186 Copyright © 2011 Open Geospatial Consortium Table 75 — Connections of the Initial state Connector type name Source state Target state Notes 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.3 EventsTrigger

Requirement http:www.opengis.netspecSPS2.0reqTasksEvents REQ 118. If an SPS server supports event notification, events shall be sent as defined in clauses 10.1.3.1 to 10.1.3.9.

10.1.3.1 DataPublished

New data was published for a task that is InExecution. If supported by the service, this causes a notification of the event.

10.1.3.2 ReservationExpired

A reserved task has expired the expiration time set by the service is before now - now being the time measured by the service. If supported by the service, this causes a notification of the event.

10.1.3.3 TaskCancelled

A scheduled task has been cancelled. Data gathered and published for the cancelled task should not automatically be deleted so that a client can retrieve the data that was gathered until the task was cancelled. If supported by the service, this causes a notification of the event.

10.1.3.4 TaskCompleted

A task that was InExecution was completed as planned. Implies that all data gathered in the task has been published. If supported by the service, this causes a notification of the event. Copyright © 2011 Open Geospatial Consortium 187

10.1.3.5 TaskConfirmed

A reserved task was confirmed. If supported by the service, this causes a notification of the event.

10.1.3.6 TaskFailed

A scheduled task has failed. Data gathered and published for the failed task should not automatically be deleted so that a client can at least retrieve the data that was gathered until the task failed. If supported by the service, this causes a notification of the event.

10.1.3.7 TaskReserved

A task was reserved. Note: a service can support notification that a task was reserved by implementing the TaskingRequestAccepted event see Table 64.

10.1.3.8 TaskSubmitted

A task was submitted. Note: a service can support notification that a task was reserved by implementing the TaskingRequestAccepted event see Table 64.

10.1.3.9 TaskUpdated

A task was updated. If supported by the service, this causes a notification of the event.

10.2 Tasking Request State Machine

10.2.1 Diagrams

The following diagram defines the state machine of an SPS tasking request. NOTE: Figure 34 is the same as Figure 8