JSDL General Session
====================

* Agenda Bashing
  
  Agreed to parameter sweep discussion first

* Parameter Sweep

  Overview presentation by Steve McGough and Q&A session

  - Is it possible to match on part of the element content; so as to
    replace for example an argument fragment? Example use case: log.$1
    - XPath can do this but it is not spelled out in the specification

  Issue: Add explanation to the spec on partial matching.

  Issue: How do you match the output files or results with the
         parameter sweep indexes?

  - In the case of a trivial implementation might have to expand to
    the equivalent number of individual JSDL document; and so get
    potentially huge number of documents.

  - Functionality of the extension seems to be a superset of what
    Platform, SGE have.
  - How does it match with what's in other tools: glite, globus etc?
  - What are the use cases this extension is designed for?

  - Was XPath profiled for this extension?
  - Would XSLT be a better match?
    - This is a simple way for writing parameter sweep. 
    - XSLT would be more complex in representation. XSLT could be used
      to implement this extension

  - What are the high-level use case for this extension?
    - Description submitted to a tool, that will process it.

  Issue: Need to make the use cases it addresses clear

  - Is it a simpler solution to modify JSDL to accomodate this
    functionality? 
    - That would break compatibility with JSDL 1.0

  - What are the semantics for this: single activity or multiple; what
    happens if some fail?
  - Would have to also define a BES extension to define how to tackle
    such cases

  Issue: For BES or some other group to consider semantics on managing
         parameter sweep jobs

  - Is it allowed to modify the sweep as it executes, i.e.,
    self-modifying code
    - Should not be able to do; and need to disallow in the
      specification

  Issue: Explicitly disallow self-modifying sweeps in the
         specification

  - Should the extension be inside the JSDL document or not?
  - Would it be possible to have this spec independent of JSDL?
    - If it is outside then have to specify the context for the XPath
      extension in some other way.

  Issue: Consider alternative packaging approaches and how to specify
         the XPath context in such cases

  - What happens if such a document is submitted to an endpoint that
    does not understand it?
    - If you don't understand it fault

  - Agreed that it seems ok as general direction; will take issues
    against on the current draft and continue discussion on teleconfs
  - Action: Andreas will upload identified issues for discussion

* JSDL overview

  Overview presentation by Andreas