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