<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi,<div><br></div><div>Paul Harrison reported (<a href="http://www.ivoa.net/internal/IVOA/AsynchronousHome/ImplementingUWS-0.1.pdf">http://www.ivoa.net/internal/IVOA/AsynchronousHome/ImplementingUWS-0.1.pdf</a>) on a UWS-0.3 implementation and suggested some changes to the UWS pattern. Here are some responses.</div><div><br></div><div><b>Change the way a job is committed for excution to "post to phase resource".</b> I accept the advantage of the client not addressing the quote object. Would it be better to allow the client to HTTP-put the phase resource? Or HTTP-post with phase=run to the job resource itself?</div><div><br></div><div><b>Extra job state "ABORTED".</b> Yes we could add this. Is there a particular use case that needs it?</div><div><br></div><div><b>Distinguish termination time from destruction time. </b>This could work, but is it really needed? For setting the times, HTTP-put would be preferred.</div><div><br></div><div><b>Error object.</b> I concur. Since the error has its own resource, I guess the service could use an HTML representation if the client accepted such.</div><div><br></div><div><b>Require action=DELETE on job-destruction posts.</b> Accepted; it's a good safeguard.</div><div><br></div><div><b>Composite metadata.</b> I agree with the principle. We need to look very closely at the implementation.</div><div><br></div><div><b>XML and HTML representations. </b>UWS 0.2 did use the stylesheet link to transform in the browser as Paul suggests. I went to the other technique for 0.3 partly to get a comparison and partly to work around some J2EE issues in a quick implementation. I'm happy to go back to client-side transformation for the next draft.</div><div><br></div><div><b>"Reload later" (503) response</b>. I'm not clear when this is to be used. Is it instead of a 404 when an output isn't ready?</div><div> </div></body></html>