Fwd: vos:group vs. uws:JobInfo

[Matthew Graham]

Hi,

I posted this to the VOSpace mailing list (vospace at ivoa.net) after the last Interop and have gotten no responses so far so let's try the main GWS list.

	Cheers,

	Matthew

Begin forwarded message:

> From: Matthew Graham <mjg at cacr.caltech.edu>
> Date: May 24, 2010 10:28:04 PM PDT
> To: vospace at ivoa.net
> Subject: vos:group vs. uws:JobInfo
> 
> Hi,
> 
> As mentioned last week, this remains the outstanding issue with VOSpace 2.0.
> 
> When multiple protocols are specified, we may need to associate a particular protocolEndpoint parameter with its respective protocol parameter (pushFromVoSpace) but in UWS these are all uws:parameters:
> 
> <uws:parameters>
>   <uws:parameter id="protocol">ivo://ivoa.net/vospace/core#httpput</uws:parameter>
>   <uws:parameter id="protocolEndpoint">http://some.server.com/put/the/data/here</uws:parameter>
>   <uws:parameter id="protocol">ivo://ivoa.net/vospace/core#ftpput</uws:parameter>
>   <uws:parameter id="protocolEndpoint">ftp://some.other.server.com/put/the/data/here</uws:parameter>
> </uws:parameters>
> 
> To handle this, we have added a parameter vos:group to the UWS Job representation so that groups of parameters can be tagged. The attribute should appear on all parameters and have the same value for a particular group, in this case, a particular protocol - protocolEndpoint pairing:
> 
> <uws:parameters>
>   <uws:parameter id="protocol" vos:group="protocol1">ivo://ivoa.net/vospace/core#httpput</uws:parameter>
>   <uws:parameter id="protocolEndpoint" vos:group="protocol1">http://some.server.com/put/the/data/here</uws:parameter>
>   <uws:parameter id="protocol" vos:group="protocol2">ivo://ivoa.net/vospace/core#ftpput</uws:parameter>
>   <uws:parameter id="protocolEndpoint" vos:group="protocol2">ftp://some.other.server.com/put/the/data/here</uws:parameter>
> </uws:parameters>
> 
> The alternate solution is that the protocol information for a transfer job does not appear in uws:parameters but in uws:jobInfo which can take arbitrary XML (as the spec says: The <job> element has placeholders of all of the standard UWS objects, and in addition there is a <uws:jobinfo> element which can be used by implementations to include any extra information within the job description.):
> 
> <uws:job>
>   ...
>   <uws:parameters>
>      ...
>   </uws:parameters>
>   ...
>   <uws:jobinfo>
>     <vos:protocol id="ivo://ivoa.net/vospace/core#httppput>
>       <vos:endpoint>http://some.server.com/put/the/data/here</vos:endpoint>
>     <vos:protocol>
>     <vos:protocol id="ivo://ivoa.net/vospace/core#ftpput">
>       <vos:endpoint>ftp://some.other.server.com/put/the/data/here</vos:endpoint>
>     <vos:protocol>
> </uws:job>
> 
> My only concern with this is that my reading of the UWS spec was that uws:jobInfo was something that the implementation used to provide extra information after a job has been specified and that it was not for additional UWS job specification material. All the information for a job should be in the uws:parameters section.
> 
> Thoughts, view, comments, etc. please.
> 
> 	Cheers,
> 
> 	Matthew
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/grid/attachments/20100812/3202e611/attachment.html>