Normal response parameters Normal response XML encoding Cancel response example Cancel exceptions

18.3 Cancel operation response

18.3.1 Normal response parameters

The normal response to a valid Cancel operation request shall be a CancelRequestResponse. More precisely, a response from the Cancel operation shall include the parts listed in the following table and shown in the following figures. The table also specifies the UML model data type plus the multiplicity and use of each listed part. Figure 45: CancelRequestResponse in UML notation Figure 46: CancelRequestResponse in XMLSpy notation Table 24 — Parts of Cancel operation response Name Definition Data type and values Multiplicity and use taskID Identifies the task token one mandatory status Tells whether the Cancel request has been accepted by the SPS server String, enumerates: “confirmed”, “rejected”, one mandatory description further information in continuous text String one optional Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 89

18.3.2 Normal response XML encoding

The following schema fragment specifies the contents and structure of a Cancel operation response, always encoded in XML. See annex B.

18.3.3 Cancel response example

A Cancel operation response for SPS can look like this encoded in XML: ?xml version=1.0 encoding=UTF-8? CancelRequestResponse xmlns = http:www.opengis.netsps taskID 433 taskID status confirmed status CancelRequestResponse

18.3.4 Cancel exceptions

When a SPS server encounters an error while performing a Cancel 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 25 — Exception codes for Cancel operation exceptionCode value Meaning of code “locator” value 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 90 Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 19 DescribeResultAccess operation mandatory

19.1 Introduction