[jsdl-wg] Proposed Extension draft document

[Andreas Savva]

After a quick look I am curious about
- the meaning, if any, of the initial values of any elements that will
be replaced by the 'sweep' declarations in the jsdl document. Should
these be left empty, should they be the first invocation, etc?
- more interesting substitutions, e.g., how to generate output filenames
specific for each iteration. A fairly common approach is to add a suffix
from the iteration counter. How would it work with 'sweep'? What about
the n-dimensional case when you'd probably want to combine values from
the nested 'sweep's?
- the explanation of the difference between 'embedded' and 'embracing'
- the example. I think a small set of simpler examples would probably be
better at this point.

Also, not specific to this proposal, we should talk about whether we
want to encourage people to define their own outermost tags
(ParameterSweep) that encapsulate JobDefinition; or whether we want to
define a generic 'ComplexJobDefinition' (or some such element) that
encapsulates (possibly multiple) JobDefinition elements together with
this kind of extensions; or whether to encourage people to put stuff
inside JobDefinition (and after JobDescription).

I've seen people do all of the above, so some statement on what is
preferable might help all around.

Andreas

Michel Drescher wrote:
> Folks,
> 
> here's a write-up of the parameter sweep extension.
> 
> If possible, I'd like to have a discussion about it on the upcoming call.
> 
> Cheers,
> Michel
> 

-- 
Andreas Savva
Fujitsu Laboratories Ltd