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