Hi Moreno,

Now, I do not fully understand the meaning of having a DataStaging element without jsdl:Source nor jsdl:Target. How should we interpret this situation?

Since there is no specific statement about this in the specification you should interpret it using the existing rules. - There is no jsdl:Source so you don't stage in - There is no jsdl:Target so you don't stage out - If jsdl:DeleteOnTermination exists then use it, otherwise do nothing This actually allows for the fringe (from our perspective) case of just cleaning up a file from a host. Thanks, good question. We should probably add explanation in a future version of the spec. PS. At GGF17 I promised Chris Smith to start a tracker for this kind of clarifications and I will upload this when I set it up. -- Andreas Savva Moreno Marzolla wrote:

Hello,

I'm writing a JSDL->classad-based JDL converter, and I have a question related to the interpretation of the jsdl:DataStaging element. According to the definition, the jsdl:DataStaging element may have two child elements (both of which are optional) jsdl:Source and jsdl:Target. As I understand:

- if only the jsdl:Source child is given, the DataStaging element refers to a request to copy files TO the execution node; - if only the jsdl:Target child is given, the DataStaging element refers to a request to copy files FROM the execution node, upon job termination; - if both jsdl:Source AND jsdl:Target children are given, then the previous two cases are combined (first the file is staged in, and upon job termination is staged out).

Now, I do not fully understand the meaning of having a DataStaging element without jsdl:Source nor jsdl:Target. How should we interpret this situation?

Thanks in advance,

Moreno.

-- Andreas Savva Fujitsu Laboratories Ltd