/[volute]/trunk/projects/grid/uws/doc/UWS.html
ViewVC logotype

Contents of /trunk/projects/grid/uws/doc/UWS.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 2709 - (show annotations)
Tue Sep 30 11:23:42 2014 UTC (6 years ago) by harripa@gmail.com
File MIME type: application/xhtml+xml
File size: 141166 byte(s)
changed blocking behaviour to use ?WAIT on /{jobs}/{job-id}
1 <?xml version="1.0" encoding="UTF-8"?><!-- $Id$
2 Universal Worker Service WD
3 Note that this file should be xhtml with div to mark sections so that it can be updated with xslt.
4 Paul Harrison -->
5 <!DOCTYPE html
6 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
7 <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xml:lang="en" lang="en" xsi:schemalocation="http://www.w3.org/1999/xhtml http://www.w3.org/2002/08/xhtml/xhtml1-transitional.xsd" xml:space="preserve">
8 <head profile="http://www.w3.org/1999/xhtml/vocab"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
9
10 <title>Universal Worker Service Pattern 1.1 - IVOA Working Draft 30 September 2014</title>
11 <meta name="Title" content="IVOA WG Internal Draft" />
12 <meta name="author" content="Paul Harrison, paul.harrison@manchester.ac.uk" />
13 <meta name="maintainedBy" content="Paul Harrison, paul.harrison@manchester.ac.uk" />
14 <link href="http://www.ivoa.net/misc/ivoa_a.css" rel="stylesheet" type="text/css" />
15 <link href="http://volute.googlecode.com/svn/trunk/projects/ivoapub/ivoadoc/XMLPrint.css" rel="stylesheet" type="text/css" />
16 <link href="http://volute.googlecode.com/svn/trunk/projects/ivoapub/ivoadoc/ivoa-extras.css" rel="stylesheet" type="text/css" />
17 <link rel="stylesheet" type="text/css" href="http://www.ivoa.net/misc/ivoa_wd.css" />
18 </head>
19 <body><div class="head">
20 <div id="titlehead" style="position:relative;height:170px;width: 500px">
21 <div id="logo" style="position:absolute;width:300px;height:169px;left: 50px;top: 0px;">
22 <img src="http://www.ivoa.net/pub/images/IVOA_wb_300.jpg" alt="IVOA logo" /></div>
23 <div id="logo-title" style="position: absolute; width: 200px; height: 115px; left: 320px; top: 5px; font-size: 14pt; color: #005A9C; font-style: italic;">
24 <p style="position: absolute; left: 0px; top: 0px;"><span style="font-weight: bold;">I</span> nternational</p>
25 <p style="position: absolute; left: 15pt; top: 25pt;"><span style="font-weight: bold;">V</span> irtual</p>
26 <p style="position: absolute; left: 15pt; top: 50pt;"><span style="font-weight: bold;">O</span> bservatory</p>
27 <p style="position: absolute; left: 0px; top: 75pt;"><span style="font-weight: bold;">A</span> lliance</p>
28 </div>
29 </div>
30 <h1>Universal Worker Service Pattern<br clear="none" />
31 Version <span class="docversion">1.1</span></h1>
32 <h2 class="subtitle">IVOA Working Draft 30 September 2014</h2>
33 <dl><dt>Working Group:</dt><dd><a href="http://www.ivoa.net/twiki/bin/view/IVOA/IvoaGridAndWebServices" shape="rect">http://www.ivoa.net/twiki/bin/view/IVOA/IvoaGridAndWebServices</a></dd>
34 <dt><b>This version:</b></dt><dd><a href="http://www.ivoa.net/Documents/UWS/20140527/WD-UWS-1.1-20140527.html" shape="rect">http://www.ivoa.net/Documents/UWS/201405127/WD-UWS-1.1-20140527.html</a></dd>
35 <dt><b>Latest version:</b></dt><dd><a href="http://www.ivoa.net/Documents/UWS/" shape="rect">http://www.ivoa.net/Documents/UWS/</a></dd>
36 <dt><b>Previous version(s):</b></dt><dd> Proposed Recommendation v1.0, 2009-09-09<br clear="none" />
37 <a href="http://www.ivoa.net/documents/UWS/20101010/" shape="rect">Recommendation v1.0 2010-10-10</a><br clear="none" />
38 <a href="http://www.ivoa.net/documents/UWS/20140527/" shape="rect">Working Draft v1.1 2014-05-27</a><br clear="none" />
39 </dd>
40 <dt>
41 </dt>
42 <dt> <br clear="none" />
43 </dt><dd>&nbsp;</dd><dt><b>Author(s):</b></dt><dd> P.
44 Harrison, G. Rixon</dd></dl>
45
46 <h2>Abstract</h2>
47 <p>The Universal Worker Service (UWS) pattern
48 defines how to manage asynchronous execution of jobs on a
49 service. Any application of the pattern defines a family of related
50 services with a common service contract. Possible uses of the pattern are also described.</p>
51 <h2> Status of This Document</h2>
52 <p>This document is produced by
53 the GWS Working Group of the IVOA.
54 The document has been reviewed by IVOA Members and other interested parties, and has been endorsed by the IVOA Executive Committee as an IVOA Recommendation as of 04 October 2010. It is a stable document and may be used as reference material or cited as a normative reference from another document. IVOA's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability inside the Astronomical Community.</p>
55 <p> <em>A list of </em><span style="background: transparent"><a href="http://www.ivoa.net/Documents/" shape="rect"><i>current
56 IVOA Recommendations and other technical documents</i></a></span><em> can be found at http://www.ivoa.net/Documents/.</em></p>
57 <p>The words "MUST", "SHALL", "SHOULD", "MAY", "RECOMMENDED", and "OPTIONAL" (in upper or lower case) used in this document are to be interpreted as described in IETF standard, RFC 2119 <cite>[<a href="#std:rfc2119">std:rfc2119</a>]</cite>.</p>
58 <h2 class="prologue-heading-western">Acknowledgements</h2>
59 <p>The need for the UWS pattern was
60 inspired by AstroGrid’s Common Execution Architecture and
61 particularly by discussions with Noel Winstanley. The ideas about
62 statefulness are distilled from debates in the Global Grid Forum in
63 respect of the Open Grid Services Infrastructure that was the
64 fore-runner of Web Services Resource Framework. The REST binding came
65 initially from suggestions by Norman Gray. Enhancements introduced in version 1.1 were as a result of feedback from implementors, particularly Pat Dowler, Dave Morris and Petr Škoda.</p>
66 </div><h2>Contents</h2><div><!--The contents of this div are automatically generated from the following processing instruction when processed with ivoarestructure.xsl-->
67 <?toc?><div id="toc" class="toc"><ul><li><a href="#Introduction"><span class="secnum">1. </span>Introduction (informative)</a><ul><li><a href="#SynchronousStateless"><span class="secnum">1.1. </span>Synchronous, stateless services</a></li><li><a href="#AsynchronousServices"><span class="secnum">1.2. </span>Asynchronous and stateful services</a></li><li><a href="#JDL"><span class="secnum">1.3. </span>Job description language, service contracts and universality</a></li><li><a href="#IVOARCH"><span class="secnum">1.4. </span>UWS in the IVOA Architecture</a></li></ul></li><li><a href="#UWSpattern"><span class="secnum">2. </span>Universal Worker Service Pattern (normative)</a><ul><li><a href="#UWSObjects"><span class="secnum">2.1. </span>Objects within a UWS</a><ul><li><a href="#Joblist"><span class="secnum">2.1.1. </span>Job list</a></li><li><a href="#Job"><span class="secnum">2.1.2. </span>Job</a></li><li><a href="#ExecutionPhase"><span class="secnum">2.1.3. </span>Execution Phase</a></li><li><a href="#ExecutionDuration"><span class="secnum">2.1.4. </span>Execution Duration</a></li><li><a href="#DestructionTime"><span class="secnum">2.1.5. </span>Destruction Time</a></li><li><a href="#Quote"><span class="secnum">2.1.6. </span>Quote</a></li><li><a href="#Error"><span class="secnum">2.1.7. </span>Error</a></li><li><a href="#Error2"><span class="secnum">2.1.8. </span>Owner</a></li><li><a href="#Error3"><span class="secnum">2.1.9. </span>RunId</a></li><li><a href="#ResultsList"><span class="secnum">2.1.10. </span>Results List</a></li><li><a href="#ResultsList2"><span class="secnum">2.1.11. </span>Parameter List</a></li></ul></li><li><a href="#RESTbinding"><span class="secnum">2.2. </span>The REST Binding</a><ul><li><a href="#d1e834"><span class="secnum">2.2.1. </span>Resources and URIs</a><ul><li><a href="#blocking"><span class="secnum">2.2.1.1. </span>Blocking Behaviour</a></li></ul></li><li><a href="#d1e603"><span class="secnum">2.2.2. </span>Representations of resources</a><ul><li><a href="#jobList"><span class="secnum">2.2.2.1. </span>Job List</a></li><li><a href="#d1e1040"><span class="secnum">2.2.2.2. </span>Job</a></li><li><a href="#resultList"><span class="secnum">2.2.2.3. </span>Results List</a></li><li><a href="#d1e1353"><span class="secnum">2.2.2.4. </span>Parameters List</a></li><li><a href="#d1e1556"><span class="secnum">2.2.2.5. </span>Error</a></li></ul></li><li><a href="#jobcontrol"><span class="secnum">2.2.3. </span>State changing requests</a><ul><li><a href="#jobCreation"><span class="secnum">2.2.3.1. </span>Creating a Job</a><ul><li><a href="#d2e1612"><span class="secnum">2.2.3.1.1. </span>Inline Parameters</a></li></ul></li><li><a href="#d1e1390"><span class="secnum">2.2.3.2. </span>Deleting a Job</a></li><li><a href="#d1e1402"><span class="secnum">2.2.3.3. </span>Changing the Destruction Time</a></li><li><a href="#d1e1420"><span class="secnum">2.2.3.4. </span>Changing the Execution Duration</a></li><li><a href="#d1e1439"><span class="secnum">2.2.3.5. </span>Starting a Job</a></li><li><a href="#d1e1448"><span class="secnum">2.2.3.6. </span>Aborting a Job</a></li></ul></li><li><a href="#d1e708"><span class="secnum">2.2.4. </span>Message pattern</a></li></ul></li></ul></li><li><a href="#security"><span class="secnum">3. </span>Security Considerations (normative)</a></li><li><a href="#ApplicationsOfUWS"><span class="secnum">4. </span>Applications of UWS (informative)</a><ul><li><a href="#Imageservice"><span class="secnum">4.1. </span>Image service with data staging</a></li><li><a href="#ADQLservice"><span class="secnum">4.2. </span>ADQL service with cursor</a></li><li><a href="#ParameterizedApplications"><span class="secnum">4.3. </span>Parameterised applications</a></li></ul></li><li><a href="#SynchronousService"><span class="secnum">5. </span>Implementing a Synchronous Service on top of UWS (informative)</a></li><li><a href="#Updates"><span class="secnum">A. </span>Updates from previous versions</a><ul><li><a href="#d1e1112"><span class="secnum">A.1. </span>At Version 0.5</a></li><li><a href="#d1e1775"><span class="secnum">A.2. </span>At Version 1.0</a></li><li><a href="#ver11"><span class="secnum">A.3. </span>At Version 1.1</a></li></ul></li><li><a href="#UWSSchema"><span class="secnum">B. </span>UWS Schema</a></li></ul></div>
68 <!--end of autogenerated content--></div><div class="body">
69 <div class="section"><h2><a id="Introduction" shape="rect"><span class="secnum">1. </span>Introduction (informative)</a></h2>
70 <p>The Universal Worker Service (UWS)
71 pattern defines how to build <i>asynchronous</i>, <i>stateful</i>, <i>job-oriented</i> services<i> </i>(the italicised terms are defined
72 in sub-sections of this introduction). It does so in a way that
73 allows for wide-scale reuse of software and support from software
74 toolkits.</p>
75 <p>Section <span class="xref"><a href="#UWSpattern">2</a></span>
76 of this document describes
77 the pattern and lists the aspects that are common to all its
78 applications. Any such application would involve a service contract
79 that embodies the pattern and fixes the issues left undefined in the
80 pattern itself (see section <span class="xref"><a href="#JDL">1.3</a></span>). The contract might include the XML schemata which form a "job description language" or JDL for the application, or simply a description of the input parameters for the service which are conveyed via typical HTML form encodings. It is intended that each such contract
81 cover a family of related applications, such that the implementations
82 may be widely reused.</p>
83 <p>Section <a href="#ApplicationsOfUWS" shape="rect">4</a> outlines several possible
84 applications of the pattern. These use-cases may be expanded into
85 full IVOA standards that are siblings of the current document.</p>
86 <p>Section <a class="xref" href="#SynchronousService" shape="rect">5</a> describes the preferred
87 method of creating a synchronous facade to a UWS system.</p>
88 <div class="section"><h3><a id="SynchronousStateless" shape="rect"><span class="secnum">1.1. </span>Synchronous, stateless services</a></h3>
89 <p>Simple web services are <i>synchronous</i> and <i>stateless</i>. Synchronous means that the client waits for
90 each request to be fulfilled; if the client disconnects from the
91 service then the activity is abandoned. <i>Stateless</i> means that
92 the service does not remember results of a previous activity (or, at
93 least, the client cannot ask the service about them).</p>
94 <p>Synchronous, stateless services work
95 well when two criteria apply.</p>
96 <ol><li>
97 <p>The length of each activity is
98 less than the “attention span” of the connection.</p>
99 </li><li>
100 <p>The results of each activity are
101 compact enough to be easily passed back to the client via the
102 connection on which the request was made (and possibly pushed back
103 to the service as parameters of the next activity).</p>
104 </li></ol>
105 <p>There are various limits to the
106 attention span.</p>
107 <ul><li>
108 <p>HTTP assumes that the start of a
109 reply quickly follows its request, even if the body of the reply
110 takes a long time to stream. If the service takes too long to
111 compute the results and to start the reply, then HTTP times out and
112 the request is lost.</p>
113 </li><li>
114 <p>A client runs on a computer which
115 will not stay on-line indefinitely.</p>
116 </li><li>
117 <p>A network with finite
118 reliability will eventually break communications during an activity.</p>
119 </li><li>
120 <p>A service is sometimes shut down
121 for maintenance.</p>
122 </li></ul>
123 <p>Synchronous, stateless services, in
124 short, do not scale well. The following examples illustrate situations in the VO in which synchronous, stateless services are inadequate.</p>
125 <ol><li>
126 <p>An ADQL <cite>[<a href="#std:adql">std:adql</a>]</cite> service gives access
127 to a large object-catalogue. Most queries run in less than a minute,
128 but some legitimate queries involve a full-table traverse and take
129 hours or days. The service needs to run these special cases in a
130 low-priority queue.</p>
131 </li><li>
132 <p>An object-finding service runs
133 the SExtractor <cite>[<a href="#sextractor">sextractor</a>]</cite> application on a list of images. Normally, the list
134 is short and the request is quickly satisfied. Occasionally, a list
135 of 10,000 images is sent in the expectation that the work will be
136 finished over the weekend.</p>
137 </li><li>
138 <p>A cone-search <cite>[<a href="#std:scs">std:scs</a>]</cite> request on a
139 rich catalogue raises 10,000,000 rows of results, but the client is
140 connected via a slow link and cannot read all the results in a
141 reasonable time. The client needs the service to send the results
142 into storage over a faster link. This could mean sending them to
143 VOSpace <cite>[<a href="#std:vospace">std:vospace</a>]</cite>, or simply holding them temporarily at the service until the user can
144 retrieve them on a fast link. UWS provides a pattern for doing the latter.</p>
145 </li><li>
146 <p>An ADQL service allows users to
147 save query results into new tables such that they can be the target
148 of later queries. However, space is limited and the results tables
149 can only be kept for a short time. The client and service negotiate
150 the lifetime of the results tables.</p>
151 </li><li>
152 <p>A service performs image
153 stacking on a list of fields. Each field can be processed by a
154 synchronous service but the list is long and the user wants to
155 retrieve the results of the early fields before the last fields are
156 processed.</p>
157 </li></ol>
158 </div>
159 <div class="section"><h3><a id="AsynchronousServices" shape="rect"><span class="secnum">1.2. </span>Asynchronous and stateful services</a></h3>
160 <p>Services can be made to scale better
161 by making them <i>asynchronous</i> and <i>stateful</i>. Asynchronous
162 means that a client makes two or more separate requests to the
163 service in the course of one activity, and that the client and
164 service may be disconnected, possibly for days or more, in between
165 those requests. Stateful means that the service stores state
166 information about the activity and the client addresses requests to
167 this state.</p>
168 <p>Web services that are asynchronous
169 are almost always stateful. Most of the special extra arrangements for
170 asynchronous activities are actually managing the state of the
171 activity.</p>
172 <p>There is an important class of
173 stateful services where the state is peculiar to one job or session
174 and the job is “owned” by one user. These, for the purpose of
175 this document, are called <i>job-oriented</i> services. There are
176 stateful services that are not job-oriented (e.g. a service managing
177 a shared, client-writeable DB table), but UWS does not apply to
178 these.</p>
179 <p>For the purpose of this discussion,
180 let the term <i>job</i> refer to the work specified by the JDL
181 instructions and the term <i>resource</i> refer to the state of the
182 job as recorded by the service. Both have a finite duration. The <i>lifetime</i> of the resource – i.e. the time from inception
183 until the service forgets the state – is generally finite and must
184 be at least as long the duration of the job.</p>
185 </div>
186 <div class="section"><h3><a id="JDL" shape="rect"><span class="secnum">1.3. </span>Job description language, service contracts and universality</a></h3>
187 <p>Consider the web-service operation
188 that starts off a job. This operation must express what is to be done
189 in the activity: it must carry parameters in some form.</p>
190 <p>The parameters may be expressed as a
191 list. For example, a cone search service takes a list of three parameters:
192 RA, DEC, RADIUS. Alternatively, the parameters may be arranged as an
193 XML document (e.g. ADQL, CEA <cite>[<a href="#harrison05">harrison05</a>]</cite>). The rules for setting and arranging
194 the parameters for a job are called the<i> Job-Description Language </i>(JDL).</p>
195 <p>The combination of the UWS pattern, a
196 JDL and details of the job state visible to the client defines a
197 service contract. Changing the JDL changes the contract. Thus, it is not
198 meaningful to “implement UWS” in isolation; any implementation
199 standard must specify the rest of the contract.</p>
200 <p>If the JDL is very general, a single
201 service-contract can be reused for many kinds of service. AstroGrid’s
202 CEA<cite>[<a href="#harrison05">harrison05</a>]</cite>exploits this: one JDL covers all services offering parameterised
203 applications and even ADQL services. In the limit, a
204 sufficiently-general JDL turns a specialized worker service into a
205 universal worker service.</p>
206 </div>
207 <div class="section"><h3><a id="IVOARCH" shape="rect"><span class="secnum">1.4. </span>UWS in the IVOA Architecture</a></h3>
208 <p><img src="ivoaarchitecture.png" alt="ivoa architectures" /></p>
209 <p>With the IVOA Architecture above, UWS is a VO infrastructure standard, being used by other standards and services to enable the development of VO applications managing asynchronous and stateless execution of jobs on VO services. Examples of such jobs include the case where the response must be computed, and that computation time takes longer than the normal expectation in an interactive web session. Additionally the UWS pattern allows a simple form of data sharing of the results of a job that is suitable for "workflow" situations and can be used by Data Access Services (currently Table Access Protocol <cite>[<a href="#std:tap">std:tap</a>]</cite>, but potentially by other DAL standards). It utilizes IVOA standards for security <cite>[<a href="#std:ssoauth">std:ssoauth</a>]</cite> if it is desired that a non-public UWS be created. </p>
210 </div>
211 </div>
212 <div class="section"><h2><a id="UWSpattern" shape="rect"><span class="secnum">2. </span>Universal Worker Service Pattern (normative)</a></h2>
213 <div class="section"><h3><a id="UWSObjects" shape="rect"><span class="secnum">2.1. </span>Objects within a UWS</a></h3>
214 <p>A UWS consists logically of a set of
215 objects that may be read and written to in order to control jobs. The objects are represented by elements within the XML schema detailed in <span class="xref"><a href="#UWSSchema">B</a></span>. In a REST binding, these objects are addressed as distinct web-resources each with its own URI. </p>
216 <p> The following sub-sections explain the semantics of the objects. The
217 UML diagram below shows the relationships more succinctly.</p>
218 <p><img src="Class_Diagram__UWS__UWSObjects.png" alt="UWS Objects Class Diagram" width="460" height="390" id="graphics2" /></p>
219 <div class="section"><h4><a id="Joblist" shape="rect"><span class="secnum">2.1.1. </span>Job list</a></h4>
220 <p>The Job List is the outermost object:
221 it contains all the other objects in the UWS. The immediate children
222 of the job list are Job objects (see next sub-section).</p>
223 <p>The job list may be read to find the
224 extant jobs.</p>
225 <p>The job list may be updated to add a
226 new job.</p>
227 <p>The job list itself does not allow
228 jobs to be deleted. Instead, when a job is destroyed by an action on
229 its job object, then the list updates itself accordingly.</p>
230 </div>
231 <div class="section"><h4><a id="Job" shape="rect"><span class="secnum">2.1.2. </span>Job</a></h4>
232 <p>A Job object contains the state of
233 one job. The state is a collection of other objects. Each Job
234 contains:</p>
235 <ul><li>
236 <p>Exactly one Execution Phase.</p>
237 </li><li>
238 <p>Exactly one Execution Duration.</p>
239 </li><li>
240 <p>Exactly one Deletion Time</p>
241 </li><li>
242 <p>Exactly one Quote.</p>
243 </li><li>
244 <p>Exactly one Results List.</p>
245 </li><li><p>Exactly one Owner.</p></li><li>
246 <p>Zero or one Run Identifier.</p>
247 </li><li>
248 <p>Zero or one Error.</p>
249 </li></ul>
250 </div>
251 <div class="section"><h4><a id="ExecutionPhase" shape="rect"><span class="secnum">2.1.3. </span>Execution Phase</a></h4>
252 <p>The job is treated as a state machine
253 with the Execution Phase naming the state. The phases are:</p>
254 <ul><li>
255 <p>PENDING: the job is accepted by
256 the service but not yet committed for execution by the client. In
257 this state, the job quote can be read and evaluated. This is the
258 state into which a job enters when it is first created.</p>
259 </li><li>
260 <p>QUEUED: the job is committed for
261 execution by the client but the service has not yet assigned it to a
262 processor. No Results are produced in this phase.</p>
263 </li><li>
264 <p>EXECUTING: the job has been
265 assigned to a processor. Results may be produced at any time during
266 this phase.</p>
267 </li><li>
268 <p>COMPLETED: the execution of the
269 job is over. The Results may be collected.</p>
270 </li><li>
271 <p>ERROR: the job failed to
272 complete. No further work will be done nor Results produced. Results
273 may be unavailable or available but invalid; either way the Results
274 should not be trusted.</p>
275 </li><li>
276 <p>ABORTED: the job has been
277 manually aborted by the user, or the system has aborted the job due
278 to lack of or overuse of resources.</p>
279 </li><li><p>UNKNOWN: The job is in an unknown state.</p></li><li>
280 <p>HELD: The job is HELD pending execution and
281 will not automatically be executed (cf, PENDING)</p>
282 </li><li><p>SUSPENDED: The job has been suspended by the system during execution. This might be because of temporary lack of resource. The UWS will automatically resume the job into the EXECUTING phase without any intervention when resource becomes available.</p></li><li>ARCHIVED: At destruction time the results associated with a job have been deleted to free up resource, but the metadata associated with the job is retained.</li></ul>
283 <p>A successful job will normally progress through the PENDING, QUEUED, EXECUTING, COMPLETED phases in that order. At any time before the COMPLETED phase a job may either be ABORTED or may suffer an ERROR. If the UWS reports an UNKNOWN phase, then all the client can do is re-query the phase until a known phase is reported. A UWS may place a job in a HELD phase on receipt of a PHASE=RUN request if for some reason the job cannot be immediately queued - in this case it is the responsibility of the client to request PHASE=RUN again at some later time.</p>
284 <p><img src="UWSStates.png" alt="UWS state diagram" width="487" height="332" /></p>
285
286 </div>
287 <div class="section"><h4><a id="ExecutionDuration" shape="rect"><span class="secnum">2.1.4. </span>Execution Duration</a></h4>
288 <p>An Execution Duration object defines
289 the duration for which a job shall run. This represents the
290 “computation time” that a job is to be allowed, although because
291 a specific measure of CPU time may not be available in all
292 environments, this duration is defined in real clock seconds. An
293 execution duration of 0 implies unlimited execution duration.</p>
294 <p>When the execution duration has been
295 exceeded the service should automatically abort the job, which has the
296 same effect as when a manual “Abort” is requested.</p>
297 <p>Specifically, when a job is aborted:</p>
298 <ul><li>
299 <p>if the job is still executing,
300 the execution is aborted.</p>
301 </li><li>
302 <p>any previously generated results
303 of the job are retained.</p>
304 </li></ul>
305 <p>When a job is created, the service
306 sets the initial execution duration. The client may write to an
307 Execution Duration to try to change the job's cpu time allocation.
308 The service may forbid changes, or may set limits on the allowed
309 execution duration.</p>
310 </div>
311 <div class="section"><h4><a id="DestructionTime" shape="rect"><span class="secnum">2.1.5. </span>Destruction Time</a></h4>
312 <p>The Destruction Time object
313 represents the instant when the job shall be destroyed. The
314 Destruction Time is an absolute time.</p>
315 <p>Destroying a job implies:</p>
316 <ul><li>
317 <p>if the job is still executing,
318 the execution is aborted.</p>
319 </li><li>
320 <p>any results from the job are
321 destroyed and storage reclaimed.</p>
322 </li><li>
323 <p>the service forgets that
324 the job existed.</p>
325 </li></ul>
326 <p>The Destruction Time should be viewed as
327 a measure of the amount of time that a service is prepared to
328 allocate storage for a job – typically this will be a longer
329 duration that the amount of CPU time that a service would allocate.</p>
330 <p>When a job is created the service
331 sets the initial Destruction Time. The client may write to the
332 Destruction Time to try to change the life expectancy of the job. The
333 service may forbid changes, or may set limits on the allowed
334 destruction time. If there is no destruction time set by the service then this should be indicated in the job XML as a Nill element and as a null string in the returned value for the resource.</p>
335 </div>
336 <div class="section"><h4><a id="Quote" shape="rect"><span class="secnum">2.1.6. </span>Quote</a></h4>
337 <p>A Quote object predicts when the job
338 is likely to complete. The intention is that a client creates the
339 same job on several services, compares the quotes and then accepts
340 the best quote. From the server perspective it is possible to indicate that a job will not be run by specifying a Quote that is greater than the Destruction time.</p>
341 <p>Quoting for a computational job is
342 notoriously difficult. A UWS implementation must always provide a
343 quote object, in order that the two-phase committal of jobs be
344 uniform across all UWS, but it may supply a “don't know” answer
345 for the completion time, indicated by a negative value or an XML nil element in an XML representation of the quote object.</p>
346 </div>
347 <div class="section"><h4><a id="Error" shape="rect"><span class="secnum">2.1.7. </span>Error</a></h4>
348 <p>The error object gives a human-readable error message for the underlying job. This object
349 is intended to be a detailed error message, and consequently might be
350 a large piece of text such as a stack trace. When there is an error
351 running a job, a summary of the error should also be given using the
352 optional errorSummary element of the Job element.</p>
353 </div>
354 <div class="section"><h4><a id="Error2" shape="rect"><span class="secnum">2.1.8. </span>Owner</a></h4>
355 <p>The owner object represents the identifier for the creator of the job. This object will not exist for all invocations of a UWS conformant protocol, but only in cases where the access to the service is authenticated as discussed more thoroughly in section
356 <span class="xref"><a href="#security">3</a></span>. </p>
357 </div>
358 <div class="section"><h4><a id="Error3" shape="rect"><span class="secnum">2.1.9. </span>RunId</a></h4>
359 <p>The RunId object represents an identifier that the job creator uses to identify the job. Note that this is distinct from the Job Identifier that the UWS system itself assigns to each job. The UWS system should do no parsing or processing of the RunId, but merely pass back the value (if it exists) as it was passed to the UWS at job creation time. In particular it may be the case that multiple jobs have the same RunId, as this is a mechanism by which the calling process can identify jobs that belong to a particular group. The exact mechanism of setting the RunId is not specified here, but will be part of the specification of the protocol using the UWS pattern.</p>
360 </div>
361 <div class="section"><h4><a id="ResultsList" shape="rect"><span class="secnum">2.1.10. </span>Results List</a></h4>
362 <p>The Results List object is a
363 container for formal results of the job. Its children may be any
364 objects resulting from the computation that may be fetched from the
365 service when the job has completed.</p>
366 <p>Reading the Results List itself
367 enumerates the available or expected result objects.</p>
368 <p>The children of the Results List may
369 be read but not updated or deleted. The client cannot add anything
370 to the Results List.</p>
371 </div>
372 <div class="section"><h4><a id="ResultsList2" shape="rect"><span class="secnum">2.1.11. </span>Parameter List</a></h4>
373 <p>The Parameter List is an
374 enumeration of the Job parameters. The form that the parameters take will depend on the JDL of the implementing service - for instance if the JDL is expressed as a single XML document, then there would be a single "parameter" that was that XML document. For services where the JDL consists of a list of name/value pairs (typical of the standard IVOA "simple" access protocols), then these would naturally be expressed in the parameter list. Each parameter value may be expressed either directly as the content of the parameter element, or the value expressed "by reference", where there returned parameter value is a URL that points to the location where the actual parameter value is stored.</p>
375 <p>A particular implementation of UWS may choose to allow the parameters to be updated (but not created) after the initial job creation step, before the PHASE is set to the executing state. It is up to the individual implementation to specify exactly how these parameters may be updated, but good practice (in the REST binding) would be to choose one of the following options.</p>
376 <ol><li>HTTP POST an <i>application/x-www-form-urlencoded</i><b> </b>parameter name, value pair to either
377 <ol><li>/{jobs}/{job-id}</li><li>/{jobs}/{job-id}/parameters</li></ol>
378 </li><li>HTTP PUT the parameter value to /{jobs}/{job-id}/parameters/(parameter-name)</li></ol>
379 <p>Additionally a particular implementation of UWS may allow the "job control" parameters (see section <span class="xref"><a href="#jobcontrol">2.2.3</a></span>) to be specified as part of the JDL. If doing this then the implementation must document the possibility and must use the standard parameter names (which may cause a conflict with parameters in the JDL, which is one of the reasons for the two stage job creation pattern of UWS).</p>
380 </div>
381 </div>
382 <div class="section"><h3><a id="RESTbinding" shape="rect"><span class="secnum">2.2. </span>The REST Binding</a></h3>
383 <p>In order to create a usable service the objects discussed in the section above must be exposed in a particular interface which can be addressed over a particular transport mechanism - this combination is known as a "binding". In this first version of the UWS pattern only a REST (Representational State
384 Transfer) style binding <cite>[<a href="#fielding00">fielding00</a>]</cite>is presented, however, future versions of this document will add other bindings such as SOAP. <cite>[<a href="#std:soap">std:soap</a>]</cite>. It should be noted that REST is based on HTTP <cite>[<a href="#std:http">std:http</a>]</cite> and as such the REST binding inherits standard HTTP behaviours. In particular it should be noted that the REST binding makes use of HTTP status codes to control the behaviour of the client, especially the "300" class redirection codes to ensure that the client requests particular resources after state changing operations. If a request is made to a resource that does not exist (e.g. an non-existant job-id) then a 404 error should be returned, or if a request is made that is illegal for the current state of the UWS then a 403 status should be returned. If for some reason there is a complete failure in the underlying UWS machinery then a 500 "internal server error" status should be returned. However individual job failures are indicated by setting the appropriate parts of the job representation to error statuses and a request for the individual job object representation at /(jobs)/(jobid) should have a normal 200 status code response.</p>
385
386 <div class="section"><h4><a id="d1e834" shape="rect"><span class="secnum">2.2.1. </span>Resources and URIs</a></h4>
387 <p>In a REST (Representational State
388 Transfer) binding of UWS, each of the objects defined above is
389 available as a web resource with its own URI. These URIs must form a
390 hierarchy as shown in the table below:</p>
391 <table border="1" cellpadding="2" cellspacing="0">
392 <tr>
393 <th scope="col" rowspan="1" colspan="1">URI</th>
394 <th scope="col" rowspan="1" colspan="1">Description</th>
395 <th scope="col" rowspan="1" colspan="1">Representation</th>
396 </tr>
397 <tr>
398 <td rowspan="1" colspan="1">/{jobs}</td>
399 <td rowspan="1" colspan="1">the Job List</td>
400 <td rowspan="1" colspan="1">the <span class="xmlelement">&lt;jobs&gt;</span>
401 element in the UWS schema </td>
402 </tr>
403 <tr>
404 <td rowspan="1" colspan="1">/{jobs}/(job-id)</td>
405 <td rowspan="1" colspan="1">a Job</td>
406 <td rowspan="1" colspan="1"><p>
407 the <span class="xmlelement">&lt;job&gt;</span> element in the
408 UWS schema<br clear="none" />
409 </p></td>
410 </tr>
411 <tr>
412 <td rowspan="1" colspan="1">/{jobs}/(job-id)/phase</td>
413 <td rowspan="1" colspan="1">the Phase of job (job-id)</td>
414 <td rowspan="1" colspan="1">One of the fixed strings</td>
415 </tr>
416 <tr>
417 <td rowspan="1" colspan="1">/{jobs}/(job-id)/executionduration</td>
418 <td rowspan="1" colspan="1">the maximum execution duration
419 of (job-id)</td>
420 <td rowspan="1" colspan="1">Integer number of seconds.</td>
421 </tr>
422 <tr>
423 <td rowspan="1" colspan="1">/{jobs}/(job-id)/destruction</td>
424 <td rowspan="1" colspan="1">the destruction instant for
425 (job-id)</td>
426 <td rowspan="1" colspan="1"><cite>[<a href="#std:iso8601">std:iso8601</a>]</cite>. If no destruction time then return empty string.</td>
427 </tr>
428 <tr>
429 <td rowspan="1" colspan="1">/{jobs}/(job-id)/error</td>
430 <td rowspan="1" colspan="1">any error message associated
431 with (job-id)</td>
432 <td rowspan="1" colspan="1">any representation appropriate
433 to the implementing service</td>
434 </tr>
435 <tr>
436 <td rowspan="1" colspan="1">/{jobs}/(job-id)/quote</td>
437 <td rowspan="1" colspan="1">the Quote for (job-id)</td>
438 <td rowspan="1" colspan="1"><cite>[<a href="#std:iso8601">std:iso8601</a>]</cite>If no quote available then return empty string.</td>
439 </tr>
440 <tr>
441 <td rowspan="1" colspan="1">/{jobs}/(job-id)/results</td>
442 <td rowspan="1" colspan="1">any results of the job (job-id)</td>
443 <td rowspan="1" colspan="1">the <span class="xmlelement">&lt;results&gt;</span>
444 element in the UWS schema. </td>
445 </tr>
446 <tr>
447 <td rowspan="1" colspan="1">/{jobs}/(job-id)/parameters</td>
448 <td rowspan="1" colspan="1">any parameters for the job
449 (job-id)</td>
450 <td rowspan="1" colspan="1">the <span class="xmlelement">&lt;parameters&gt;</span>
451 element in the UWS schema. </td>
452 </tr>
453 <tr>
454 <td rowspan="1" colspan="1">/{jobs}/(job-id)/owner</td>
455 <td rowspan="1" colspan="1">the owner of the job (job-id)</td>
456 <td rowspan="1" colspan="1">an appropriate identifier as
457 discussed in <span class="xref"><a href="#security">3</a></span> </td>
458 </tr>
459 </table>
460 <p>The service implementer is free to
461 choose the names given in parentheses above, i.e. the root of the URI tree, and the form that the job identifier takes (though note that it should be a legal URI path element) - the other names are part
462 of the UWS standard.</p>
463 <p>The URI for the Job List, in its
464 absolute form is the root URI for the whole UWS. This URI should be
465 given as the access URL in the UWS registration.</p>
466 <div class="section"><h4><a id="blocking" shape="rect"><span class="secnum">2.2.1.1. </span>Blocking Behaviour</a></h4>
467 <p>UWS 1.1 introduces blocking behaviour where the server may not return the result of a request immediately (i.e. block) under certain circumstances. The purpose of this functionality is to allow the client to be able to do a
468 "slow poll" of the Job status whilst the job is running. The advantage for the client is that it can know almost immediately when a job has results without having to execute polling
469 with a very short timescale - this also has advantages for the server in terms of reduced nework traffic. The blocking behaviour is restricted to the <code> /{jobs}/(job-id) </code>endpoint, and is invoked by adding a <code>?WAIT</code> query parameter to the GET request to that endpoint. When the server receives such a request it should not return a response (i.e. block)
470 until there is some significant change in the job status, which means that, at a minimum, it must return when the Job Phase changes. The server, however, may block only when in one of the "active" phases (PENDING, QUEUED or EXECUTING), and otherwise must return immediately and not block, even if a blocking request is made, to avoid the possibility of a client waiting indefinitely. The <code>?WAIT</code> query parameter may be assigned an integer value e.g. <code>?WAIT=60</code> which is be interpreted as a maximum time to block in seconds - in this case the server must return after the given value of seconds whether there has been a significant change of Job status or not. A <code>?WAIT=0</code> should be interpreted as equivalent to <code>?WAIT</code> - i.e. a wait value of 0 seconds means block indefinitely until Job status change.</p>
471 <p>A client that is UWS1.1 compliant should be aware that it will receive immediate responses if it attempts to
472 perform this operation on a UWS 1.0 server.</p>
473 </div>
474 <p>&nbsp;</p>
475 </div>
476 <div class="section"><h4><a id="d1e603" shape="rect"><span class="secnum">2.2.2. </span>Representations of resources</a></h4>
477 <p>Each of the UWS objects is mapped to a resource URI as detailed in the table above, and for each URI, a HTTP GET
478 fetches a representation of that resource. In general where an object is a container for other objects (Job List, Job, Result List, Parameter List) then an XML representation of the object should be returned, otherwise for simple atomic types (Quote, Execution Duration etc.) a textual (mime type "text/plain") representation should be returned. The XML schema for the various objects described above is
479 detailed in appendix
480 <span class="xref"><a href="#UWSSchema">B</a></span>
481 of this specification. This schema is the definitive description of the exact form of the XML returned by a UWS and must not vary between implementations.</p>
482 <p>HTTP allows multiple representations
483 of a resource distinguished by their MIME types and selected by the
484 HTTP "Accept" headers of a GET request. A UWS implementation can exploit this to support both web
485 browsers and rich clients in the same tree of resources. Although the default behaviour is to return XML, a UWS could return HTML or XHTML to
486 clients that accept these types. These clients are assumed to be web
487 browsers and the UWS is generating its own user interface. The HTML
488 interface generated should allow full control of the UWS via the use
489 of HTML forms and appropriate links.</p>
490 <p>Clients which are assumed to be part
491 of remote applications that drive UWS without showing the details to
492 their users should accept only "application/xml,text/plain". A UWS must therefore
493 return XML representations of the resources in preference to the HTML representation. A technique that may be used to always return XML that modern browsers can transform on the client-side to HTML is via the <span class="xmlelement">&lt;?xml-stylesheet ?&gt;</span> processing instruction, which can be used to point to a suitable XSL resource to perform the transformation. </p>
494 <p>More detail for some of the UWS objects is provided below.</p>
495 <div class="section"><h4><a id="jobList" shape="rect"><span class="secnum">2.2.2.1. </span>Job List</a></h4>
496 <p>The representation of the Job List is
497 a list of links to extant jobs. The list may be empty if the UWS is
498 idle. The service should return a list of all the jobs (except for jobs in the "ARCHIVED" phase for backward compatibility) that the client can see in the current security context (see section <span class="xref"><a href="#security">3</a></span>) however large the number of jobs.
499 The server may respond to a request from the client to filter the jobs shown by using URL query parameter on the PHASE for example</p>
500 <pre xml:space="preserve">/{jobs}?PHASE=EXECUTING
501 </pre>
502 <p>would list only the jobs in an EXECUTING state. If the PHASE filtering parameter is repeated, then the service should list all the jobs in the union of the enumerated PHASEs.
503 The only way to list any jobs in the "ARCHIVED" phase is to use this mechanism.</p>
504 </div>
505 <div class="section"><h4><a id="d1e1040" shape="rect"><span class="secnum">2.2.2.2. </span>Job</a></h4>
506 <p>The representation of a Job is as specified by the <span class="xmlelement">&lt;job&gt;</span> element in the UWS schema as detailed in appendix <span class="xref"><a href="#UWSSchema">B</a></span>
507 an example or such a job instance is shown below</p>
508 <div><!--The contents of this div are automatically generated from the following processing instruction when processed with ivoarestructure.xsl-->
509 <?incxml href="../UWSJobInstance.xml" ?><h:div xmlns:h="http://www.w3.org/1999/xhtml" class="viewxml"><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:job</span> <span class="attribute-name">xsi:schemaLocation</span><span class="markup">=</span><span class="attribute-value">"http://www.ivoa.net/xml/UWS/v1.0 UWS.xsd "</span> <span class="attribute-name">xmlns:xml</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/XML/1998/namespace"</span> <span class="attribute-name">xmlns:uws</span><span class="markup">=</span><span class="attribute-value">"http://www.ivoa.net/xml/UWS/v1.0"</span> <span class="attribute-name">xmlns:xlink</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/1999/xlink"</span> <span class="attribute-name">xmlns:xsi</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/2001/XMLSchema-instance"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:jobId</span><span class="markup">&gt;</span><span class="text">cea-agdevel.jb.man.ac.uk-130.88.24.18-1242749568029-508182314</span><span class="markup">&lt;/</span><span class="end-tag">uws:jobId</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:ownerId</span> <span class="attribute-name">xsi:nil</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:phase</span><span class="markup">&gt;</span><span class="text">COMPLETED</span><span class="markup">&lt;/</span><span class="end-tag">uws:phase</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:startTime</span><span class="markup">&gt;</span><span class="text">2009-05-19T17:12:48.038+01:00</span><span class="markup">&lt;/</span><span class="end-tag">uws:startTime</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:endTime</span><span class="markup">&gt;</span><span class="text">2009-05-19T17:12:48.041+01:00</span><span class="markup">&lt;/</span><span class="end-tag">uws:endTime</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:executionDuration</span><span class="markup">&gt;</span><span class="text">86400</span><span class="markup">&lt;/</span><span class="end-tag">uws:executionDuration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:destruction</span><span class="markup">&gt;</span><span class="text">2009-05-29T17:12:48.035+01:00</span><span class="markup">&lt;/</span><span class="end-tag">uws:destruction</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:parameters</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:parameter</span> <span class="attribute-name">id</span><span class="markup">=</span><span class="attribute-value">"scaleFactor"</span><span class="markup">&gt;</span><span class="text">1.8</span><span class="markup">&lt;/</span><span class="end-tag">uws:parameter</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:parameter</span> <span class="attribute-name">id</span><span class="markup">=</span><span class="attribute-value">"image"</span> <span class="attribute-name">byReference</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><span class="text">
510 http://myserver.org/uws/jobs/jobid123/param/image</span><span class="markup">&lt;/</span><span class="end-tag">uws:parameter</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">uws:parameters</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:results</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:result</span> <span class="attribute-name">id</span><span class="markup">=</span><span class="attribute-value">"correctedImage"</span> <span class="attribute-name">xlink:href</span><span class="markup">=</span><span class="attribute-value">"http://myserver.org/uws/jobs/jobid123/result/image"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">uws:results</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:errorSummary</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"transient"</span> <span class="attribute-name">hasDetail</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:message</span><span class="markup">&gt;</span><span class="text">we have problem</span><span class="markup">&lt;/</span><span class="end-tag">uws:message</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">uws:errorSummary</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">uws:jobInfo</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">any</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xml</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">thatyouwant</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xml</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">any</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">uws:jobInfo</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">uws:job</span><span class="markup">&gt;</span></div></h:div>
511 <!--end of autogenerated content--></div>
512
513
514
515
516
517
518
519 <p>The <span class="xmlelement">&lt;job&gt;</span> element has placeholders of all of the standard UWS objects, and in addition there is a <span class="xmlelement">&lt;uws:jobinfo&gt;</span> element which can be used by implementations to include any extra information within the job description.</p>
520 </div>
521 <div class="section"><h4><a id="resultList" shape="rect"><span class="secnum">2.2.2.3. </span>Results List</a></h4>
522 <p>The representation of a Results List
523 is a list of links to the resources representing the results
524 element. The linked
525 resources may have any URI and any MIME type. A sensible default for
526 their URIs is to make them children of /{jobs}/(job-id)/results, but
527 this is not required. It may sometimes be easier for a service
528 implementer to point to a resource on some web server separate from
529 that running the UWS. Therefore, a client must always parse the
530 Results List to find the results. Each result in a result list must be given a unique identifier. Where a protocol applying UWS
531 specifies standard results it must do so fixing the identifier for those results and fixing the result URIs, however the UWS must still return a valid Results List at /{jobs}/(job-id)/results, even though in this case the identifiers and URIs could be precomputed by the client.</p>
532 </div>
533 <div class="section"><h4><a id="d1e1353" shape="rect"><span class="secnum">2.2.2.4. </span>Parameters List</a></h4>
534 The representation of the parameters list is a list of
535 <span class="xmlelement">&lt;parameter&gt;</span> elements. Each of these elements can either represent the value of the parameter directly, where the content of the element is a textual representation of the parameter, or in the case where the parameter value cannot be represented legally within XML (e.g. the parameter is a binary type such as a FITS file) then the content of the parameter is a URL to the parameter value - to indicate this case the attribute byReference is set to "true".</div>
536 <div class="section"><h4><a id="d1e1556" shape="rect"><span class="secnum">2.2.2.5. </span>Error</a></h4>
537 <p>When an error occurs in a job the UWS must signal this at a minimum by setting the PHASE to error. In addition the <span class="xmlelement">&lt;errorSummary&gt;</span> element, giving a brief summary of the error, should be included within the <span class="xmlelement">&lt;job&gt;</span> element. The UWS may include a more detailed error message for example an execution log or stack trace by providing such a resource at the /{jobs}/(jobid)/error URI. It is the responsibility of the implementing service to specify the form that such an error message may take.</p>
538 </div>
539 </div>
540 <div class="section"><h4><a id="jobcontrol" shape="rect"><span class="secnum">2.2.3. </span>State changing requests</a></h4>
541 <p>Certain of the UWS' resources accept
542 HTTP POST and DELETE messages to change the state of the service –
543 This is the fundamental way that a client controls the execution of a
544 job. In most of the cases where a job sub-object is set the response
545 will have a http 303 “See other” status and a Location header
546 that points back to the main job summary obtained at the <span style="font-weight: medium">/{jobs}/(job-id)
547 URI. The job summary contains the values of (or links to) all the UWS objects
548 within the returned XML (or XHTML). This mode of operation was chosen
549 (as opposed to returning only the sub-object being altered) as it
550 makes for a more natural user interface – especially in the case of
551 the XHMTL interface. A client that wants to obtain only the value of
552 a particular sub-object can at any time request that sub-object with
553 a HTTP GET.</span></p>
554 <div class="section"><h4><a id="jobCreation" shape="rect"><span class="secnum">2.2.3.1. </span>Creating a Job</a></h4>
555 <p>POSTing a request to the Job List
556 creates a new job (unless the service rejects the request). The
557 response when a job is accepted must have code 303 “See other”
558 and the Location header of the response must point to the created
559 job. The response when the job is rejected should be a HTTP 403 Forbidden status style response.</p>
560 <p>This initial POST will in most cases
561 carry parameters for the protocol that is using the UWS pattern, as
562 detailed in <span class="xref"><a href="#ApplicationsOfUWS">4</a></span>
563 .In addition for the initial post may contain job control parameters if allowed by the implementing protocol
564 (i.e. if UWS job control parameter names do not clash with the implementing protocol parameters). One use of this
565 facility might be to have the job placed into a potentially running state by adding ?PHASE=RUN query part to the job creation URL.</p>
566 <div class="section"><h4><a id="d2e1612" shape="rect"><span class="secnum">2.2.3.1.1. </span>Inline Parameters</a></h4>
567 <p>The JDL may allow parameter values to be uploaded in-line - in this case the UWS should accept the parameter content as multipart/form-data encoded in the POST with the formal value of the parameter being a "byReference" type using the special URI scheme "param" with the path part of the URI matching the name attribute of the multipart/form-data encoding content part. The content of such an in-line parameter should be made available as part of the job resource tree at /{jobs}/{job-id}/parameters/{parameter-name}, and then described as a "byReference" parameter in the <span class="xmlelement">&lt;job&gt;</span> XML description.</p>
568 </div>
569 <p>&nbsp;</p>
570 </div>
571 <div class="section"><h4><a id="d1e1390" shape="rect"><span class="secnum">2.2.3.2. </span>Deleting a Job</a></h4>
572 <p>Sending a HTTP DELETE to a Job
573 resource destroys that job, with the meaning noted in the definition
574 of the Job object, above. No other resource of the UWS may be
575 directly deleted by the client. The response to this request must
576 have code 303 “See other” and the Location header of the response
577 must point to the Job List at the /{jobs} URI.</p>
578 <p>Posting a request with a parameter
579 ACTION=DELETE to the Job also destroys the job, the response being as
580 for a deletion. This action supports web browsers which typically
581 cannot send DELETE requests.</p>
582 </div>
583 <div class="section"><h4><a id="d1e1402" shape="rect"><span class="secnum">2.2.3.3. </span>Changing the Destruction Time</a></h4>
584 <p>The Destruction Time may be changed
585 by POSTing to /{jobs}/(job-id)/destruction. In this case, the body
586 of the posted request is of type <i>application/x-www-form-urlencoded</i><b> </b><span style="font-weight: medium">and
587 contains the parameter named DESTRUCTION whose value is the new
588 destruction time in ISO8601 format; i.e. this request is what an HTML
589 form sends.</span></p>
590 <p style="font-weight: medium">The
591 response to this request must have code 303 “See other” and the
592 Location header of the response must point to the /{jobs}/(job-id)
593 URI so that the client receives the value that the service has
594 actually set the Destruction Time to within the Job summary response. The service may override the requested Destruction Time and substitute a value of its choosing e.g. a job owner may have reached his storage quota and so the service only allows further data to be stored for shorter times than requested.</p>
595 </div>
596 <div class="section"><h4><a id="d1e1420" shape="rect"><span class="secnum">2.2.3.4. </span>Changing the Execution Duration</a></h4>
597 <p>The Execution Duration may be changed
598 by POSTing to /{jobs}/(job-id)/executionduration. In this case, the body
599 of the posted request is of type <i>application/x-www-form-urlencoded</i><b> </b><span style="font-weight: medium">and
600 contains the parameter named EXECUTIONDURATION whose value is the new
601 executionduration in seconds.</span></p>
602 <p style="font-weight: medium">The
603 response to this request must have code 303 “See other” and the
604 Location header of the response must point to the
605 /{jobs}/(job-id) so that the client receives the value that the
606 service has actually set the Execution Duration to. The service may to override the request and substitute a value of its choosing</p>
607 </div>
608 <div class="section"><h4><a id="d1e1439" shape="rect"><span class="secnum">2.2.3.5. </span>Starting a Job</a></h4>
609 <p style="font-weight: medium">A
610 job may be started by POSTing to the /{jobs}/(job-id)/phase URI. The
611 POST contains a single parameter PHASE=RUN which instructs the UWS to
612 attempt to start the job. The response to this request must have code
613 303 “See other” and the Location header of the response must
614 point to the /{jobs}/(job-id) URI so that the client receives the
615 phase that the job has been set to. Typically a UWS will put a job
616 into a QUEUED state on receipt of this command, but depending on how
617 busy the server is, the job might be put almost immediately (and
618 without client intervention) into an EXECUTING state.</p>
619 </div>
620 <div class="section"><h4><a id="d1e1448" shape="rect"><span class="secnum">2.2.3.6. </span>Aborting a Job</a></h4>
621 <p style="font-weight: medium">A
622 job may be aborted by POSTing to the /{jobs}/(job-id)/phase URI. The
623 POST contains a single parameter PHASE=ABORT which instructs the UWS
624 to attempt to abort the job. Aborting a job has the effect of stopping a job executing, but the resources associated with a job remain intact. The response to this request must have
625 code 303 “See other” and the Location header of the response must
626 point to the /{jobs}/(job-id) URI so that the client receives the
627 phase that the job has been set to.</p>
628 </div>
629 </div>
630 <div class="section"><h4><a id="d1e708" shape="rect"><span class="secnum">2.2.4. </span>Message pattern</a></h4>
631 <p>The REST binding results in the
632 message pattern shown in figure 2.</p>
633 <p><i>Illustration 2:
634 Typical calling sequence for the REST binding of UWS</i></p>
635 <p><img src="Sequence_Diagram__UWS__Rest_Message_Pattern__Rest_Message_Pattern__Rest_Message_Pattern.png" width="100%" id="graphics3" alt="rest message pattern" /></p>
636 <br style="clear: both;" clear="none" />
637 </div>
638 </div>
639 </div>
640 <div class="section"><h2><a id="security" shape="rect"><span class="secnum">3. </span>Security Considerations (normative)</a></h2>
641 <p>A UWS should follow IVOA standards for security <cite>[<a href="#std:ssoauth">std:ssoauth</a>]</cite> if it is desired that a non-public UWS be created. It is possible to imagine many different authorization policies that might be employed in an authenticated UWS, where particular groups of users have different permissions to create and view different types of jobs. A full discussion of such authorization policies is beyond the scope of this document, but a UWS should behave as described in section <span class="xref"><a href="#RESTbinding">2.2</a></span>
642 for any individual authenticated user, although it is clear that a user without sufficient privileges might only obtain a restricted list of jobs within the joblist at /{jobs}. Any attempt to retrieve a job for which the user does not have sufficient privilege should result in a 403 Forbidden HTTP status being returned.</p>
643 <p>When an authentication mechanism is used in the UWS then the implementation should set the owner object to the identity obtained by the authentication. </p>
644 </div>
645 <div class="section"><h2><a id="ApplicationsOfUWS" shape="rect"><span class="secnum">4. </span>Applications of UWS (informative)</a></h2>
646 <p>The UWS pattern leaves undefined two
647 essential parts of the service contract: the content that must be
648 posted to create a job; and the pattern of results made available by
649 a completed job. An application of UWS completes a service contract
650 by defining these matters.</p>
651 <p>There follow some use cases applying
652 the UWS pattern. The descriptions are neither formal nor complete.
653 The intention is to show a range of ways that the pattern can be
654 applied without burdening the reader with the level of detail needed
655 for a standard implementation.</p>
656 <p>Any of these cases could be worked up
657 into a full IVOA standard by formalizing the description, adding
658 detail and generally making the specification more
659 exact and complete.</p>
660 <div class="section"><h3><a id="Imageservice" shape="rect"><span class="secnum">4.1. </span>Image service with data staging</a></h3>
661 <p>Consider a service that computes
662 images from archive data. The computation takes significant time, so
663 the service is asynchronous. The service keeps the computed images in
664 its own storage until the user downloads them; this is essentially
665 the model of SIAP <cite>[<a href="#std:siap">std:siap</a>]</cite>.</p>
666 <p>The asynchronous image-service is a
667 logical extension of a synchronous SIA service. Therefore it uses the
668 REST binding of UWS.</p>
669 <p>The parameters for posting a new job
670 are as for SIAP 1.0:</p>
671 <ul><li>
672 <p>POS, the position on the sky to
673 be searched.</p>
674 </li><li>
675 <p>SIZE, the size of the search
676 box.</p>
677 </li><li>
678 <p>FORMAT: the type of images to be
679 computed.</p>
680 </li></ul>
681 <p>Particular implementations are free
682 to add extra parameters.</p>
683 <p>These parameters are posted in a
684 document of type <i>application/x-www-form-urlencoded</i><span style="font-style: normal">:
685 i.e. they can be sent from an HTML form.</span></p>
686 <p style="font-style: normal">The
687 images generated by the job are accessible as results. Each
688 image has its own URI and can be downloaded over HTTP at any time
689 until the destruction time of the job. The URIs for the images may be
690 discovered from the Results List in the normal UWS way.</p>
691 <p style="font-style: normal">SIAP
692 1.0 produces, for each query, a table of metadata describing the
693 images. The asynchronous image-service produces a table to the same
694 schema as a result with a fixed identifier, called “table”.</p>
695 <p><span style="font-style: normal">Image
696 results are added to the results list, and to the “table” result,
697 as they are generated. Hence, a client that polls the service can
698 discover, download and use some of the images before the job is
699 finished. </span>If the client is satisfied with
700 these early images, the client can cancel the rest of the job by
701 destroying the job. However, destroying the job deletes the cached
702 images so the client has to download them <i>first</i>.</p>
703 </div>
704 <div class="section"><h3><a id="ADQLservice" shape="rect"><span class="secnum">4.2. </span>ADQL service with cursor</a></h3>
705 <p>ADQL [1] can serve as a JDL. Consider
706 an ADQL service that supports long-running queries as asynchronous
707 operations. In general, the results of the query may be a large set
708 of data. They may be too large to download comfortably. We might like
709 to cache these results on the service and to operate a cursor,
710 drawing down from the resource a few rows of the table at a time.</p>
711 <p>The parameters of a job are as
712 follows:</p>
713 <ul><li>
714 <p>ADQL: the query text</p>
715 </li><li>
716 <p>FORMAT: the format for the
717 results</p>
718 </li></ul>
719 <p>These parameters are posted in a
720 document of type <i>application/x-www-form-urlencoded</i><span style="font-style: normal">:
721 i.e. they can be sent from an HTML form.</span></p>
722 <p style="font-style: normal">A
723 successful query generates the following results:</p>
724 <ul><li>
725 <p style="font-style: normal"><i>table</i>:
726 the whole result set as one file resource.</p>
727 </li><li>
728 <p style="font-style: normal"><i>header</i>:
729 the metadata for the output table.</p>
730 </li><li>
731 <p style="font-style: normal"><i>cursor</i>:
732 a selection of rows of output.</p>
733 </li></ul>
734 <p>The <i>cursor</i> result is
735 parameterised by the query parameters FIRST and LAST in the query
736 string of its URI: these parameters state the index of the first and
737 last row to be returned; e.g.</p>
738 <p> http://whatever.org/adlqService/results/cursor?FIRST=1&amp;LAST=100</p>
739 <p>If the parameters are missing, the
740 service decides which rows to return.</p>
741 </div>
742 <div class="section"><h3><a id="ParameterizedApplications" shape="rect"><span class="secnum">4.3. </span>Parameterised applications</a></h3>
743 <p>There is a class of applications on
744 which a job may be defined by a list of simple parameters. “Simple”
745 here means unstructured: a scalar value such as a number, a string of
746 text or a boolean value. If the parameters are allowed to be file name,
747 so that structured data are passed indirectly, then the class of
748 applications is very large indeed. Almost any non-interactive
749 application can be driven in this way.</p>
750 <p>Turning each application of choice
751 into a service (with or without UWS semantics) would be onerous.
752 However, if the application’s interface is entirely characterized,
753 through the JDL, in terms of typed input and output parameters, then
754 one service contract will work for all the applications and a single
755 implementation of the contract can be reused for all cases.</p>
756 <p>AstroGrid’s Common Execution
757 Architecture (CEA) <cite>[<a href="#harrison05">harrison05</a>]</cite> works in this way. It has just one service
758 contract for all applications (including ADQL services; the ADQL
759 query is passed in the list of parameters). It has four
760 implementations, one for each of the possible interfaces between the
761 service and a kind of job (jobs can be implemented with Java classes,
762 command-line applications, HTTP-get services or JDBC databases). CEA
763 also specifies stateful, asynchronous services and makes use of
764 VOSpace.</p>
765 <p>Consider a CEA reworked to use the
766 UWS pattern for consistency with other (future) IVOA standards. Call
767 it CEA v2 to distinguish it from CEA v1 as currently maintained by
768 AstroGrid. For this example, consider the particular kind of CEA
769 service that runs applications supplied as executable binaries.</p>
770 <p>A binary application-server has a
771 library of applications co-located with its service and defined in
772 the service configuration set by the service provider. It does not
773 accept code from the client for local execution.</p>
774 <p>The JDL in CEA v2 is similar to that
775 in CEA v1 It is a formal, XML vocabulary for expressing choice
776 of application and parameter lists <cite>[<a href="#std:vocea">std:vocea</a>]</cite>. Parameters may be inputs or
777 outputs of the job.</p>
778 <p>To start a job, a document in this
779 JDL is posted to the UWS. The document is sent in its native
780 MIME-type, application/xml, so this is not an interface that can be
781 driven directly from an HTML form, although it can be driven from the
782 emerging XForms technology<cite>[<a href="#std:xform">std:xform</a>]</cite>.</p>
783 <p>The results of the job depend on the
784 choice of application. They are all results whose identifiers and
785 types are defined in the definition of the application. That
786 application-definition is registered, so the client knows before
787 running the job what results to expect.</p>
788 <p>CEA input-parameters may be indirect:
789 i.e. they may refer to data in on-line storage. In this case, the JDL
790 document contains the URIs for those data objects Alternatively, the
791 parameters may be direct, in which case the JDL contains the actual
792 value of the parameters.</p>
793 <p>Similarly, CEA results may be made
794 indirect. In this case, the results are named as parameters in the
795 JDL where the values are the URIs to which the results are delivered.
796 The application server can then stream the results to the specified
797 destination as they become available and need not cache them locally.
798 If a job result is indirect, then the server can choose whether or
799 not to keep a local copy. If it chooses not to cache locally, then
800 the result URI in the UWS is set to the external location named in
801 the URI.</p>
802 </div>
803 </div>
804 <div class="section"><h2><a id="SynchronousService" shape="rect"><span class="secnum">5. </span>Implementing a Synchronous Service on top of UWS (informative)</a></h2>
805 <p>Whilst the provision of synchronous
806 services is not one of the design aims of the UWS pattern, there is
807 clearly a desire in second generation IVOA services still to allow a
808 simple synchronous calling pattern to be available to simple clients.
809 What follows is a recommended recipe for putting a synchronous facade
810 on UWS;</p>
811 <p>It is assumed that the core of the
812 service does provide a true UWS compliant set of endpoints rooted at
813 /async (equivalent to the /{jobs} endpoint in the nomenclature used
814 above). The desired synchronous service is to be rooted at /sync.</p>
815 <ol><li>
816 <p>The job is started by either a
817 GET (for compatibility with existing IVOA standards) or a POST
818 (preferably) of form encoded parameters to the /sync endpoint.</p>
819 </li><li>
820 <p>Internally the service creates a
821 job in the standard UWS system with the given parameters and sets
822 the PHASE to RUN, noting the returned job identifier which we will
823 call {job-id}. The /sync endpoint then responds with a STATUS 303
824 (redirection) response to the URL /sync/{job-id}.</p>
825 </li><li>
826 <p>The /sync/{job-id} endpoint then
827 blocks until it detects that the underlying job has finished at
828 which point it responds with a STATUS 303 (redirection) to the
829 /{jobs}/{job-id}/results/mainresult URL, where “mainresult” is
830 the name of the primary result of the job.</p>
831 </li></ol>
832 <p>In this way the service appears to be
833 a synchronous to the original client – assuming it obeys standard
834 HTTP redirection semantics, so a simple client like a web browser
835 could obtain the result with a single “click”. At the same time a
836 more sophisticated, UWS aware, client could control the same job from
837 the standard /{jobs} endpoint – indeed if the synchronous call
838 timed out for some reason, then it would be possible for the original
839 client to retrieve the results by looking at the /{jobs}/{job-id} URL
840 tree, because it could make the association of the job-Id from the
841 URL it receives in step 2 above.</p>
842 <p>The purely synchronous client is
843 restricted compared with the full UWS pattern in that there can only
844 be one result directly returned to the client, as noted in stage 3
845 above. This is usually not a problem for compatibility with existing
846 version 1.0 DAL services as they typically return a single VOTable
847 containing references to the desired data.</p>
848 </div>
849
850 <div class="appendices"><h2><a name="Appendices" id="Appendices" shape="rect"></a>Appendices</h2>
851
852 <div class="section"><h2><a id="Updates" shape="rect"><span class="secnum">A. </span>Updates from previous versions</a></h2>
853 <div class="section"><h3><a id="d1e1112" shape="rect"><span class="secnum">A.1. </span>At Version 0.5</a></h3>
854 <ul><li>
855 changed the POST parameter names
856 to be the same as the resource paths.
857 </li><li>
858 added synchronous section.
859 </li><li>
860 updated SOAP binding section
861 </li></ul>
862 </div>
863 <div class="section"><h3><a id="d1e1775" shape="rect"><span class="secnum">A.2. </span>At Version 1.0</a></h3>
864 <ul><li>Removed all SOAP binding - deferred to later version.</li><li>Added parameterList</li><li>Added ownerId and jobId as subsidiary job object</li></ul>
865 </div>
866 <div class="section"><h3><a id="ver11" shape="rect"><span class="secnum">A.3. </span>At Version 1.1</a></h3>
867 <p>This version is intended to clarify use, and add a small number of facilities that should not break existing 1.0 clients.
868 The Enhancements that have been added are</p>
869 <ul><li>Informative section on how to start a job in a
870 running state <span class="xref"><a href="#jobCreation">2.2.3.1</a></span>
871 </li><li>Added the ability to filter on the job list <span class="xref"><a href="#jobList">2.2.2.1</a></span></li><li>Added a new phase "ARCHIVED" <span class="xref"><a href="#ExecutionPhase">2.1.3</a></span> and <span class="xref"><a href="#jobList">2.2.2.1</a></span></li>
872 <li>Added blocking behaviour to allow "slow poll" <span class="xref"><a href="#blocking">2.2.1.1</a></span>.</li>
873 </ul>
874 </div>
875 </div>
876
877 <div class="section"><h2><a id="UWSSchema" shape="rect"><span class="secnum">B. </span>UWS Schema</a></h2>
878 <p>Note that this schema can be found on-line at <a href="http://www.ivoa.net/xml/UWS/v1.0" shape="rect">http://www.ivoa.net/xml/UWS/v1.0</a> (i.e. the target namespace
879 can also be used as a URL for the schema.) This location should
880 represent the definitive source, the schema is reproduced below only for
881 completeness of this document.</p>
882 <div><!--The contents of this div are automatically generated from the following processing instruction when processed with ivoarestructure.xsl-->
883 <?incxml href="../UWS.xsd"?><h:div xmlns:h="http://www.w3.org/1999/xhtml" class="viewxml"><div class="comment">&lt;!-- $Revision$ $Date$ $HeadURL$ --&gt;</div><div class="comment">&lt;!-- UWS schema - Paul Harrison May 2008 --&gt;</div><div class="comment">&lt;!--
884 $Log: UWS.xsd,v $
885 Revision 1.1.2.1 2010/02/25 11:33:41 pah
886 updates as used in the UWS 1.0 PR
887
888 Revision 1.1 2009/06/15 15:30:32 pah
889 made some of the global element defintions for job subobjects just local again
890 added runid, ownerid
891 added ParamList
892 changed some element names to be consistent with the uris
893 Revision 1.6 2008/10/01 11:54:02 pah fix up cvs
894 header Revision 1.5 2008/09/25 00:22:35 pah change termination
895 time to execution duration
896 --&gt;</div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:schema</span> <span class="attribute-name">targetNamespace</span><span class="markup">=</span><span class="attribute-value">"http://www.ivoa.net/xml/UWS/v1.0"</span> <span class="attribute-name">elementFormDefault</span><span class="markup">=</span><span class="attribute-value">"qualified"</span> <span class="attribute-name">attributeFormDefault</span><span class="markup">=</span><span class="attribute-value">"unqualified"</span> <span class="attribute-name">xmlns:xml</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/XML/1998/namespace"</span> <span class="attribute-name">xmlns:xs</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/2001/XMLSchema"</span> <span class="attribute-name">xmlns:uws</span><span class="markup">=</span><span class="attribute-value">"http://www.ivoa.net/xml/UWS/v1.0"</span> <span class="attribute-name">xmlns:xlink</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/1999/xlink"</span><span class="markup">&gt;</span><div class="indent"><div class="comment">&lt;!--
897 &lt;xs:import namespace="http://www.w3.org/1999/xlink"
898 schemaLocation="../../../stc/STC/v1.30/XLINK.xsd" /&gt;
899 --&gt;</div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:import</span> <span class="attribute-name">namespace</span><span class="markup">=</span><span class="attribute-value">"http://www.w3.org/1999/xlink"</span> <span class="attribute-name">schemaLocation</span><span class="markup">=</span><span class="attribute-value">"http://www.ivoa.net/xml/Xlink/xlink.xsd"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ShortJobDescription"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"phase"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ExecutionPhase"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> the execution phase - returned at
900 /(jobs)/(jobid)/phase</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"id"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:JobIdentifier"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"required"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attributeGroup</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"uws:reference"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attributeGroup</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"reference"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">standard xlink references
901 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"xlink:type"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"optional"</span> <span class="attribute-name">default</span><span class="markup">=</span><span class="attribute-value">"simple"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"xlink:href"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"optional"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:attributeGroup</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:simpleType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ExecutionPhase"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
902 Enumeration of possible phases of job execution
903 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:restriction</span> <span class="attribute-name">base</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"PENDING"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
904 The first phase a job is entered into - this is where
905 a job is being set up but no request to run has
906 occurred.
907 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"QUEUED"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
908 An job has been accepted for execution but is waiting
909 in a queue
910 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"EXECUTING"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">An job is running</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"COMPLETED"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
911 An job has completed successfully
912 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"ERROR"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
913 Some form of error has occurred
914 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"UNKNOWN"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
915 The job is in an unknown state.
916 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"HELD"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
917 The job is HELD pending execution and will not
918 automatically be executed - can occur after a
919 PHASE=RUN request has been made (cf PENDING).
920 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"SUSPENDED"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
921 The job has been suspended by the system during
922 execution
923 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"ABORTED"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
924 The job has been aborted, either by user request or by
925 the server because of lack or overuse of resources.
926 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"ARCHIVED"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
927 The job has been archived by the server at destruction time. An archived job
928 may have deleted the results to reclaim resources, but must have job metadata preserved.
929 This is an alternative that the server may choose in contrast to completely destroying all record of the job.
930 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:enumeration</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:restriction</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:simpleType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"JobSummary"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">The complete representation of the state
931 of a job</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"jobId"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:JobIdentifier"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"runId"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"1"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> this is a client supplied identifier -
932 the UWS system does nothing other than to return it as
933 part of the description of the job</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ownerId"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">the owner (creator) of the job -
934 this should be expressed as a string that can be
935 parsed in accordance with IVOA security standards. If
936 there was no authenticated job creator then this
937 should be set to NULL.</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"phase"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ExecutionPhase"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> the execution phase - returned at
938 /(jobs)/(jobid)/phase</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"quote"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:dateTime"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"true"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"1"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> A Quote predicts when the job is likely to complete - returned at /(jobs)/(jobid)/quote
939 "don't know" is encoded by setting to the XML null value xsi:nil="true"</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"startTime"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:dateTime"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">The instant at which the job started execution.</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"endTime"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:dateTime"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">The instant at which the job finished execution</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"executionDuration"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:int"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"false"</span><span class="markup">&gt;</span><div class="indent"><div class="comment">&lt;!-- TODO look if xs:duration here has any benefits --&gt;</div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> The duration (in seconds) for which
940 the job should be allowed to run - a value of 0 is
941 intended to mean unlimited - returned at
942 /(jobs)/(jobid)/executionduration</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"destruction"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:dateTime"</span> <span class="attribute-name">nillable</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> The time at which the whole job +
943 records + results will be destroyed. returned at
944 /(jobs)/(jobid)/destruction</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"uws:parameters"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"1"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">The parameters to the job (where appropriate)
945 can also be retrieved at /(jobs)/(jobid)/parameters</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"uws:results"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">The results for the job - can also be retrieved at /(jobs)/(jobid)/results</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"errorSummary"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ErrorSummary"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"1"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">&gt;</span><span class="text">
946 </span><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"jobInfo"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"1"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> This is arbitrary information that can
947 be added to the job description by the UWS
948 implementation.</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:any</span> <span class="attribute-name">namespace</span><span class="markup">=</span><span class="attribute-value">"##any"</span> <span class="attribute-name">processContents</span><span class="markup">=</span><span class="attribute-value">"lax"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"unbounded"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:simpleType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"JobIdentifier"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> The identifier for the job
949 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:restriction</span> <span class="attribute-name">base</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:simpleType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"job"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:JobSummary"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> This is the information that is returned
950 when a GET is made for a single job resource - i.e.
951 /(jobs)/(jobid)</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"jobs"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> The list of job references returned at
952 /(jobs)</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> ISSUE - do we want to have any sort of
953 paging or selection mechanism in case the job list gets
954 very large? Or is that an unnecessary complication...
955 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"jobref"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ShortJobDescription"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"unbounded"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ResultReference"</span> <span class="attribute-name">mixed</span><span class="markup">=</span><span class="attribute-value">"false"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> A reference to a UWS result. If the
956 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"id"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"required"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attributeGroup</span> <span class="attribute-name">ref</span><span class="markup">=</span><span class="attribute-value">"uws:reference"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"results"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> The element returned for
957 /(jobs)/(jobid)/results</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"result"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ResultReference"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"unbounded"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ErrorSummary"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
958 A short summary of an error - a fuller representation of the
959 error may be retrieved from /(jobs)/(jobid)/error
960 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"message"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"type"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:ErrorType"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"required"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">
961 characterization of the type of the error
962 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:attribute</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"hasDetail"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:boolean"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"required"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text">if true then there is a more detailed error message available at /(jobs)/(jobid)/error</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:attribute</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:simpleType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"ErrorType"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:restriction</span> <span class="attribute-name">base</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"transient"</span><span class="markup">/&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:enumeration</span> <span class="attribute-name">value</span><span class="markup">=</span><span class="attribute-value">"fatal"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:restriction</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:simpleType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"Parameter"</span> <span class="attribute-name">mixed</span><span class="markup">=</span><span class="attribute-value">"true"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> the list of input parameters to the job - if
963 the job description language does not naturally have
964 parameters, then this list should contain one element which
965 is the content of the original POST that created the job.
966 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"byReference"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:boolean"</span> <span class="attribute-name">default</span><span class="markup">=</span><span class="attribute-value">"false"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> if this attribute is true then the
967 content of the parameter represents a URL to retrieve the
968 actual parameter value.</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> It is up to the implementation to decide
969 if a parameter value cannot be returned directly as the
970 content - the basic rule is that the representation of
971 the parameter must allow the whole job element to be
972 valid XML. If this cannot be achieved then the parameter
973 value must be returned by reference.</span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:attribute</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"id"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:string"</span> <span class="attribute-name">use</span><span class="markup">=</span><span class="attribute-value">"required"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:annotation</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:documentation</span><span class="markup">&gt;</span><span class="text"> the identifier for the parameter
974 </span><span class="markup">&lt;/</span><span class="end-tag">xs:documentation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:annotation</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:attribute</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:attribute</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"isPost"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"xs:boolean"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"parameters"</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:complexType</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:sequence</span><span class="markup">&gt;</span><div class="indent"><div class="element"><span class="markup">&lt;</span><span class="start-tag">xs:element</span> <span class="attribute-name">name</span><span class="markup">=</span><span class="attribute-value">"parameter"</span> <span class="attribute-name">type</span><span class="markup">=</span><span class="attribute-value">"uws:Parameter"</span> <span class="attribute-name">maxOccurs</span><span class="markup">=</span><span class="attribute-value">"unbounded"</span> <span class="attribute-name">minOccurs</span><span class="markup">=</span><span class="attribute-value">"0"</span><span class="markup">/&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:sequence</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:complexType</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:element</span><span class="markup">&gt;</span></div></div><span class="markup">&lt;/</span><span class="end-tag">xs:schema</span><span class="markup">&gt;</span></div><div class="comment">&lt;!-- --&gt;</div></h:div>
975 <!--end of autogenerated content--></div>
976
977
978
979
980
981
982
983 </div>
984 </div>
985 <div class="section-nonum'"><h2><a name="References" id="References" shape="rect"></a>References</h2>
986 <div>
987 <!-- <?bibliography ivoadoc/refs.bib ?> -->
988
989
990 <dl><dt><a name="std:rfc2119" id="std:rfc2119" shape="rect">[std:rfc2119] Bradner, S. </a></dt><dd>
991 <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">Key words for use in RFCs to Indicate Requirement Levels</a>, IETF RFC 2119, 1997</dd><dt><a name="std:xform" id="std:xform" shape="rect">[std:xform] John M. Boyer, editor.</a></dt><dd>
992 <a href="http://www.w3.org/TR/xforms11/" shape="rect">Xforms 1.1</a>, 2007.
993 </dd><dt><a name="std:http" id="std:http" shape="rect">[std:http] R. Fielding, J. Gettys, J. Mogul, H. Frystyk,
994 L. Masinter, P. Leach, and T. Berners-Lee.</a></dt><dd>
995 <a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html" shape="rect">Hypertext
996 transfer protocol -- http/1.1</a>.
997 {rfc2616}, June 1999.
998 </dd><dt><a name="std:vospace" id="std:vospace" shape="rect">[std:vospace] Matthew Graham, Dave Morris, and Guy
999 Rixon.</a></dt><dd> <a href="http://www.ivoa.net/Documents/VOSpace/" shape="rect">Vospace specification</a>.
1000 {IVOA Recommendation}, 2009. </dd><dt><a name="std:tap" id="std:tap" shape="rect">[std:tap] Patrick Dowler, Guy Rixon, Doug Tody.</a></dt><dd> <a href="http://www.ivoa.net/Documents/VOSpace/" shape="rect">Table Access Protocol</a>.
1001 {IVOA Recommendation}, 2010. </dd><dt>&nbsp;</dt><dt><a name="fielding00" id="fielding00" shape="rect">[fielding00] Roy Thomas Fielding.</a></dt><dd>
1002 <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm" shape="rect"><em>Architectural Styles and the Design of Network-based Software
1003 Architectures</em></a>.
1004 PhD thesis, University of California, Irvine, 2000.
1005 </dd><dt><a name="std:soap" id="std:soap" shape="rect">[std:soap] Don Box, David Ehnebuske, Gopal Kakivaya,
1006 Andrew Layman, Noah Mendelsohn, Henrik Frystyk Nielsen, Satish Thatte, and
1007 Dave Winer.</a></dt><dd>
1008 <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/" shape="rect">Simple object access
1009 protocol (soap) 1.1</a>, 2000.
1010 </dd><dt><a name="std:iso8601" id="std:iso8601" shape="rect">[std:iso8601] ISO 8601:2004 Data elements and interchange formats - Information interchange - Representation of dates and times</a></dt><dd>
1011 International Organization for
1012 Standardization, 2004.
1013 </dd><dt><a name="std:ssoauth" id="std:ssoauth" shape="rect">[std:ssoauth] {Grid and Web Services Working Group},
1014 Guy Rixon and Matthew Graham, editors.</a></dt><dd>
1015 <a href="http://www.ivoa.net/Documents/latest/SSOAuthMech.html" shape="rect">Ivoa
1016 single-sign-on profile: Authentication mechanisms version 1.01</a>, 2008.
1017 </dd><dt><a name="harrison05" id="harrison05" shape="rect">[harrison05] P. Harrison.</a></dt><dd>
1018 <a href="http://www.ivoa.net/Documents/latest/CEA.html" shape="rect">A proposal for a
1019 common execution architecture</a>.
1020 {IVOA Note}, May 2005.
1021 </dd><dt><a name="std:vocea" id="std:vocea" shape="rect">[std:vocea] Paul Harrison.</a></dt><dd>
1022 VOCEA - an xml schema for registering cea.</dd><dt><a name="sextractor" id="sextractor" shape="rect">[sextractor]
1023 http://astromatic.iap.fr/software/sextractor/.</a></dt><dd>
1024 <a href="http://astromatic.iap.fr/software/sextractor/" shape="rect">Sextractor</a>.
1025 [Online].
1026 </dd><dt><a name="std:adql" id="std:adql" shape="rect">[std:adql] Iñaki Ortiz, Jeff Lusted, Pat Dowler,
1027 Alexander Szalay, Yuji Shirasaki, Maria A. Nieto-Santisteba, Masatoshi
1028 Ohishi, William O'Mullane, Pedro Osuna, the VOQL-TEG, and the VOQL
1029 Working Group, Pedro Osuna and Iñaki Ortiz, editors.</a></dt><dd>
1030 <a href="http://www.ivoa.net/Documents/latest/ConeSearch.html" shape="rect">Ivoa
1031 astronomical data query language</a>.
1032 {IVOA Recommendation}, 2008.
1033 </dd><dt><a name="std:siap" id="std:siap" shape="rect">[std:siap] Doug Tody and Ray Plant, Paul Harrison,
1034 editor.</a></dt><dd>
1035 <a href="http://www.ivoa.net/Documents/latest/SIA.html" shape="rect">Simple image access
1036 specification</a>.
1037 {IVOA Recommendation}, 2009.
1038 </dd><dt><a name="std:scs" id="std:scs" shape="rect">[std:scs] Roy Williams, Robert Hanisch, Alex Szalay, and
1039 Raymond Plante, Raymond Plante, editor.</a></dt><dd>
1040 <a href="http://www.ivoa.net/Documents/latest/ConeSearch.html" shape="rect">Simple cone
1041 search</a>.
1042 {IVOA Recommendation}, 2008.
1043 </dd></dl>
1044 </div>
1045 </div>
1046 </div><p style="text-align: right; font-size: x-small; color: #888;">
1047 $Revision$ $Date$ $HeadURL$</p></body></html>

Properties

Name Value
svn:keywords LastChangedDate LastChangedRevision HeadURL Id
svn:mime-type application/xhtml+xml

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26