Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
94 Copyright © 2012 Open Geospatial Consortium
7.3.14 Extensibility Model
Even if this specification is quite flexible e.g. the order and scene selection options are dynamic an additional flexibility mechanism has been included: in fact the following element:
xs:element name=extension type=xs:anySimpleType With multiplicit 0 ..N has been included in:
OrderSpecification, for setting additional parameter – implementation specific – at order level,
which are not already covered by order options;
CommonOrderItemType, for setting additional parameter – implementation specific – at order
item level, which are not already covered by order options;
OrderSearchCriteriaType, for setting additional - implementation specific – filtering criteria;
These elements allows to experiment additional functionalities – maintaining the backward compatibility – that can be included in future revisions of this specification.
Additionally they open pave the way for the definition and formalization of extensions for this specification see SPS and SPS EO specifications.
7.4 Operation encoding
All operations must support the embedding of requests and responses in SOAP messages. Only SOAP messaging via HTTPPOST with documentliteral style has to be used.
Messages must conform to SOAP 1.2 http:www.w3.orgTRSOAP. The message payload will be in the body of the SOAP envelope.
For SOAP transfer, each XML-encoded operation request shall be encapsulated in the body of a SOAP envelope. In other words, the SOAP-Body shall be used for transmitting the request.
The optional SOAP-Header shall be used for optional elements in order to invoke the service. For instance, these elements could be identity tokens, licenses or other elements that are not necessarily
required by the implementation specification.
Similarly, each XML-encoded operation response shall be encapsulated in the body of a SOAP envelope. Again, the optional header should be used for elements not directly related to the operation
response, e.g. licenses or information targeted at an SOAP receiver in the SOAP message path.
If an error is detected while processing an operation request encoded in a SOAP envelope, the Ordering Service shall generate a SOAP response message where the content of the Body element is a Fault
element containing an ExceptionReport element within the SOAP-Body.
7.4.1 Examples Operation encoding
7.4.1.1 Example of Request GetStatus - Request XML Request encoding
?xml version=1.0 encoding=UTF-8? GetStatus …
… GetStatus
SOAP Request encoding
Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
95 Copyright © 2012 Open Geospatial Consortium
soap:Envelope xmlns:soap=”http:www.w3.org200305soap-envelope” xmlns:ows=”http:www.opengis.netows2.0”
soap:Header …
soap:Header soap:Body
GetStatus … … GetStatus
soap:Body soap:Envelope
7.4.1.2 Example of Response GetStatus – Response with success XML Response encoding
?xml version=1.0 encoding=UTF-8? GetStatusResponse …
statussuccessstatus … all info about the status of the order …
GetStatusResponse
SOAP Response encoding
soap:Envelope xmlns:soap=”http:www.w3.org200305soap-envelope” xmlns:ows=”http:www.opengis.netows2.0”
soap:Header …
soap:Header soap:Body
GetStatusResponse …
statussuccessstatus … all info about the status of the order …
GetStatusResponse
soap:Body
soap:Envelope
7.4.1.3 Example of Response GetStatus – Response with partial success XML Response encoding
?xml version=1.0 encoding=UTF-8? GetStatusResponse …
statuspartialstatus errorMessageReason of the partial resulterrorMessage
… partial info about the status of the order … GetStatusResponse
SOAP Response encoding
soap:Envelope xmlns:soap=”http:www.w3.org200305soap-envelope” xmlns:ows=”
http:www.opengis.netows 2.0”
soap:Header …
soap:Header soap:Body
GetStatusResponse …
statuspartialstatus errorMessageReason of the partial resulterrorMessage
… partial info about the status of the order … GetStatusResponse
soap:Body
soap:Envelope
Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
96 Copyright © 2012 Open Geospatial Consortium
7.4.1.4 Example of Response GetStatus – Response failed SOAP FAULT
XML Response encoding
?xml version=1.0 encoding=UTF-8? soap:Fault
soap:Codesoap:Value…soap:Valuesoap:Code soap:Reason
soap:Text…soap:Text soap:Reason
soap:Detail ows:ExceptionReport
Exception exceptionCode= … locator=…
ExceptionText…ExceptionText Exception
ows:ExceptionReport soap:Detail
soap:Fault
The ‘soap:Code’ element shall have the Value: “soap:Server” indicating that this is a Server exception
“soap:Client” indicating that this is a Client exception. The ‘soap:Reason’ element shall have the ‘soap:Text’ value:
“Server exception was encountered”, indicating that this is a Server exception “Client exception was encountered”, indicating that this is a Client exception
The ‘ows:ExceptionReport’ element shall have the: ‘Exception’ entity with the ‘exceptionCode’ and ‘locator’ values that depend by operation.
‘ExceptionText’ entity with the value that describes the reason of the exception. SOAP Response encoding
soap:Envelope xmlns:soap=http:www.w3.org200305soap-envelope xmlns:ows=”http:www.opengis.netows2.0”
soap:Header …
soap:Header soap:Body
soap:Fault
soap:Codesoap:Value…soap:Valuesoap:Code soap:Reason
soap:Text…soap:Text soap:Reason
soap:Detail ows:ExceptionReport
Exception exceptionCode=
… locator=…
ExceptionText…ExceptionText Exception
ows:ExceptionReport soap:Detail
soap:Fault
soap:Body
soap:Envelope
Ordering Services for Earth Observation Products Interface Standard
OGC 06-141r6
97 Copyright © 2012 Open Geospatial Consortium
7.4.2 List of Operations
