EO Satellite Tasking Extension for SPS OGC 10-135
The ValidateResponse data type is derived from the ExtensibleResponse data type defined in [OGC 09-001] and therefore inherits all the properties contained in that data
type. ValidateResponse does not restrict the content model of ExtensibleResponse, but adds the additional status property that contains the reports. It shall therefore contain the
properties defined for the ExtensibleResponse data type plus the types defined in the following table.
Name Definition
Data Type Multiplicity
result Current status report eventually reflecting
validation of the selected segments if the operation is executed synchronously.
StatusReport from OGC 09-000
One mandatory
8.2.3 XML Encoding
The following XML schema snippet normalizes the XML encoding of the ValidateResponse class.
element name
= Validate
type =
eosps:ValidateType substitutionGroup
= swes:ExtensibleRequest
complexType name
= ValidateType
complexContent extension
base =
swes:ExtensibleRequestType sequence
element name
= task
type =
anyURI element
name =
segmentID type
= NCName
maxOccurs =
unbounded sequence
extension complexContent
complexType
Requirement http:www.opengis.netspecEOSPS2.0reqvalrequest-valid
Req 45. The XML message encoding a Validate request shall be valid with respect to
the validate.xsd XML schema. The server shall correctly reject an invalid request by
returning the proper correctly formatted exception as defined in [OGC 06‐121] and
[OGC 09‐001].
The following XML schema snippet normalizes the XML encoding of the ValidateResponse class.
element name
= ValidateResponse
type =
eosps:ValidateResponseType substitutionGroup
= swes:ExtensibleResponse
complexType name
= ValidateResponseType
complexContent extension
base =
swes:ExtensibleResponseType sequence
element name
= result
type =
sps:StatusReportPropertyType sequence
extension
Copyright ©
2011 Open
Geospatial Consortium
85
OGC 10-135 EO Satellite Tasking Extension for SPS
complexContent complexType
Requirement http:www.opengis.netspecEOSPS2.0reqvalresponse-valid
Req 46. The XML message encoding a ValidateResponse shall be valid with respect
to the validate.xsd XML schema.
Below is an example of Validate request and the corresponding response:
Validate service
= EOSPS
version =
2.0 xmlns
= http:www.opengis.neteosps2.0
task http:ws.spotimage.comspstasksT45EF36C23D4C89AB
task segmentID
S25 segmentID
segmentID S26
segmentID Validate
ValidateResponse xmlns
= http:www.opengis.neteosps2.0
xmlns:sps =
http:www.opengis.netsps2.0 result
sps:StatusReport ... result
ValidateResponse
8.2.4 Exceptions
When an SPS EO server encounters an error while performing a Validate operation, it shall return an exception report message as specified in the Sensor Planning Service 2.0
standard [OGC 09-000].
The following table presents exception codes that are applicable to the Validate operation.
Exception Codes Applicable
OperationNotSupported Yes MissingParameterValue Yes
InvalidParameterValue Yes VersionNegotiationFailed No
InvalidUpdateSequence No OptionNotSupported No
NoApplicableCode Yes InvalidRequest Yes
An InvalidParameterValue exception shall be returned when the task identifier is not recognized by the service.
86 Copyright
© 2011
Open Geospatial
Consortium
