17.3 Upate operation response
17.3.1 Normal response parameters
The normal response to a valid UpdateRequest operation request shall be UpdateRequestResponse. More precisely, a response from the UpdateRequest operation
shall include the parts listed in Table 21 and shown in the following figures. This table also specifies the UML model data type plus the multiplicity and use of each listed part.
Figure 41: UpdateRequestResponse in UML notation
Figure 42: UpdateRequestResponse in XMLSpy notation
84
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
Table 21: — Parts of UpdateRequest operation response Name
Definition Data type and values
Multiplicity and use
taskID Identifies the updated task,
provided by SPS server token one
mandatory status
Tells whether the UpdateRequest has been
accepted or rejected by the SPS server
String, enumerates: “confirmed”,
“rejected”,
“incomplete request
”
one mandatory
description additional continuous
text String one
optional estimatedToC
Estimated Time of Completion for this task
gml:TimeInstant one optional
missingParameters Definition of additional
parameters that are necessary to update a task
and have not been delivered in the UpdateRequest
InputDescriptor, see subclause 11.2.2
one to many optional
17.3.2 Normal response XML encoding
The following schema fragment specifies the contents and structure of a Update operation response, always encoded in XML.
See annex B.
17.3.3 Upate response example
A Update operation response for SPS can look like this encoded in XML:
?xml version=1.0 encoding=UTF-8? UpdateRequestResponse
xmlns =
http:www.opengis.netsps taskID
433 taskID
status confirmed
status UpdateRequestResponse
17.3.4 Upate exceptions
When a SPS server encounters an error while performing an Update operation, it shall return an exception report message as specified in Subclause 7.4 of [OGC 05-008]. The
allowed standard exception codes shall include those listed in the following table. For each listed exceptionCode, the contents of the “locator” parameter value shall be as
specified in the right column.
Table 22 — Exception codes for UpdateRequest operation
exceptionCode value Meaning of code
“locator” value
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
85
OperationNotSupported Request is for an operation that is not supported by this server
Name of operation not supported
MissingParameterValue Operation request does not include a parameter value, and this server did not declare a default
value for that parameter Name of missing
parameter InvalidParameterValue
Operation request contains an invalid parameter value
Name of parameter with invalid value
NoApplicableCode No other exceptionCode specified by this service
and server applies to this exception None, omit “locator”
parameter
TaskIDExpired taskID that has been issued by the client is no
longer supported by the service None, omit locator
parameter
InvalidRequest Request is not conform to the schema for this
operation Exception message
generated by validator
86
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
18 Cancel operation optional
18.1 Introduction