We have a number of use cases and stakeholders asking for multi-jobs, e.g. parameter sweep and meta-computing 
applications. This may actually be a problem for JSDL. One option is to capture this was our own argument wrapper for 
the CreateActivityFromJSDL operation. There are a number of things we might want to include (optionally) and it might 
just be simpler to take this document style approach rather than the procedural model currently in the spec.

Things that could optionally go into this wrapper are:

1) One of more JSDL documents with VERY simple work flow semantics.

2) The subscription request

3) The start in suspended state vector

4) The non-itempotentent job id.

5) ????