ogc.wps.2.0.wpsCommon.xsd Maven / Gradle / Ivy
WPS is an OGC Standard.
Copyright (c) 2015 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/.
WPS operation request base, for all WPS operations, except GetCapabilities.
In this XML encoding, no "request" parameter is included, since the element
name specifies the specific operation.
An 'Extension' element provides a placeholder for extra request parameters
that might be defined by WPS extension standards.
Any ancillary information to be sent from client to server.
Placeholder for further request parameters defined by WPS extension standards.
Service type identifier (WPS)
Version of the WPS interface specification implemented by the server (2.0.0)
This element is used for web accessible references to a data set or value.
Reference to an input (output) value that is a web accessible resource.
The contents of this element to be used as the body of the HTTP request
message to be sent to the service identified in ../Reference/@href.
For example, it could be an XML encoded WFS request using HTTP/POST.
Reference to a remote document to be used as the body of the an HTTP/POST request message
to the service identified in the href element in the Reference structure.
HTTP URI that points to the remote resource where the request body may be retrieved.
HTTP URI that points to the remote resource where the data may be retrieved.
This element is used to embed the data in a WPS request or response.
The content can be XML data, plain character data, or specially encoded binary data (i.e. base64).
Media type of the data.
Encoding procedure or character set used (e.g. raw, base64, or UTF-8).
Identification of the data schema.
This attribute type is used to specify data transmission modes for process outputs.
A JobID is a unique identifier for a process execution, i.e. a process instance.
Particularly suitable JobIDs are UUIDs or monotonic identifiers such as unique timestamps.
If the privacy of a Processing Job is imperative, the JobID should be non-guessable.
This attribute type is used to specify process control options.
The WPS specification only defines "execute-sync" and "execute-async",
each with an associated execution protocol.
Extensions may specify additional control options, such as "dimiss" which is
defined in the WPS dismiss extension.
A Result document is a structure that contains the results of a process execution.
It is a shared element between the Execute and GetResult operations.
Include if required. A JobId is usually required for
a) asynchronous execution
b) the Dismiss operation extension, where the client is allowed to
actively free server-side resources
Identifier of the Process that was executed.
This Process identifier shall be as listed in the ProcessOfferings
section of the WPS Capabilities document.
This type describes a process output in the execute response.
Identifier of this output.
StatusInfo document containing information about executed processes.
This element is used to communicate basic status information about executed processes.
Basic status set to communicate the status of a server-side job to the client.
Extensions of this specification may introduce additional states for fine-grained
monitoring or domain-specific purposes.
The job has finished with no errors.
The job has finished with errors.
The job is queued for execution.
The job is running.
Estimated date and time by which the job will be completed. Use if available.
The time of estimated completion lies significantly before the expiration date of this job.
Suggested date and time for the next status poll (GetStatus) for this job. Use if appropriate.
The time of the next poll shall lie significantly before the expiration date of this job.
If this element is provided but an expiration date for the job is not given, clients are expected to check
the job status on time to eventually receive an update on the expiration date and avoid missing the results.
Use as a progress indicator if appropriate. Like most progress bars the value is an estimate without accuracy guarantees.
Date and time by which the job and its results will be removed from the server. Use if appropriate.
In some situations the expiration date may not be known from the start. In this case, it is recommended
to specify a timestamp for NextPoll.
A typical example is a long running process for which the results are stored 48 hours after completion. While the
process is running, clients are provided with updated timestamps for NextPoll. As soon as the process has completed
the ExpirationDate is determined.