JSDL General session at OGF 24
==============================

16 September 2008

Agenda
------
1. JSDL WG status and sessions
2. JSDL "Optional Elements"
3. New topics to work on


1. JSDL WG status and sessions
------------------------------
- Andreas presents the WG status and session schedule at OGF24
- Brief discussion about the various published documents and
  necessary process documents (experience doc etc.)
- Need a call for implementors for SPMD extension to produce
  experience doc
- Parameer Sweep extension doc will be submitted to the 
  Editor pipeline on 19 September
- Short update on the efforts on the XQuery extension to JSDL
  -- Currently no critical mass to proceed further

2. JSDL Optional Elements
-------------------------
- Steve McGough introduces the audience to the issue
- Currently, JSDL requires all elements (even optional in the 
  XML document) to be understood or to fail
- Too restrictive approach, and an alternatve is necessary
- Example use case of a parallel MPI job
  -- *If* Infiniband is installed, use it as my that job 
     supports it
  -- *Do not* use Infiniband even if installed as it tends to 
     crash my job
- Pass-though JSDL
  -- From a Condor ClassAd description, a JSDL doc is created.
  -- That JSDL doc may contain optional ClassAd information
  -- The receiving BES container may happily ignore all 
     optional ClassAd elements
  -- If the receiving BES is backed by Condor ClassAd it may
     make use of all optional ClassAd elements in the JSDL doc
- Discussion about details of the proposal
  -- How about existing extensions?
     --- Could prove difficult for example for SPMD
  -- How about future extensions?
- Discussions about existing specifications that do not provide
  for Schema extension for elements of attributes
- Both semantic and syntactic compatibility problems occur
  -- Semantic: Older systems implemented *before* this effort will 
     inevitabily fail if the "may ignore" attribute is present
  -- Syntactic: Existing specifications and extensions may not be
     suitable as they may not provide for general extensibility
     for attributes of elements
- Discussion about the direction this leads JSDL to
  -- Abstract job descriptions that need incarnation/grounding 
     to local batch system configurations
  -- User preferences, batch system preferences, broker preferences
  -- Flexible requirements descriptions using XQuery etc.

3. New topics to work on
------------------------
- Collection of issues
  -- SPMD Extension experience document write-up
  -- How to relate/combine with GLUE 2?
  -- How to add XQuery into the game?