-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mark, thanks for the scenario description. As we talked earlier, I managed to resolve your issue, but I would like the JSDL WG to participate in that progress: In summary, you describe the following scenario: a) Legacy application that expects fixed names for input and output, i.e. "wing.dat" and "output.dat" b) The application also expects a second input data set residing in a particular directory, which is named "engine.dat". c) The input data and output data are structured so that explicit command line parameter manipulation cannot be used, i.e. the input contains 3D construction parameters for the wing and engine of an aeroplane. d) The parameter sweep then consists of providing the application with the appropriate input sets, and collecting the output using different names in a shared directory for later comparison. This scenario can be accomplished using the current draft for Parameter Sweeps. The presentation I gave was unfortunately of quire executive nature, so I left out probably important information. The current draft expects XPath 2.0 expressions to select affected parameters. The presentation obviously concentrated on the use case of command lime parameter manipulation. However, as XPath 2.0 is employed, one can select *any* element or even particle (sub-element of an XML element or attribute value) of that document. As the current parameter sweep proposal is intended to be embedded in a JSDL document, it is allowed (and in fact, encouraged) to select appropriate elements or particles of the DataStaging sub elements so that the data staging element actually carries out the parameter sweep functionality. If there is a need expressed, I will assemble an example to illustrate this. Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCDhUk0lMZTNKw4QRAtRIAKCaxu/dEJ6ti3QsfqignzyQvPjc1ACdERdF 0J2JQ8NtusjAhED7wmEe8s0= =x1IH -----END PGP SIGNATURE-----