vos:group vs. uws:JobInfo
Paul.Harrison at manchester.ac.uk
Mon Aug 16 04:37:35 PDT 2010
On 2010-08 -13, at 18:50, Matthew Graham wrote:
> Hi Paul,
> Thanks for the swift response - this certainly helps the discussion.
> Is it your recommendation that any service which uses UWS specifically states what its JDL is? Is there a suitable format for this for validation, etc? In VOSpace 2.0, I have assumed that the <uws:parameters> define the job since there is no initial POST - what is posted is the full XML representation of the Job resource, e.g.:
OK - now I see what you are doing - As far as the UWS specification goes, I think that the initial POST can be anything, and I guess that the using the a document conforming to the uws:job schema is ok, though I think a rather confusing, and possibly limiting choice. I would personally use a specific vospace schema that does what you want directly as the JDL, rather than trying to squeeze this into the allowable spaces in the UWS job description (and incidentally the schema "any" definition in the UWS schema does mean that any <vos:transfer> needs to be in a <uws:jobInfo> element).
> <uws:job xsi:schemaLocation="http://www.ivoa.net/xml/UWS/v1.0
> UWS.xsd "
> http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <uws:ownerId xsi:nil="true"/>
> <uws:startTime xsi:nil="true"/>
> <uws:endTime xsi:nil="true"/>
> <uws:destruction xsi:nil="true"/>
> <uws:parameter id="target">vos://nvo.caltech!vospace/mydata1</uws:parameter>
> <uws:parameter id="direction">vos://nvo.caltech!vospace/mydata2</uws:parameter>
> <uws:parameter id="keepBytes">false</uws:parameter>
> or have I misread UWS?
More information about the grid