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

Properties

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

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