Breakout on enactment engines and workflow languages
We propose that this breakout develops a classification scheme for the workflow oriented systems that are in place, or are needed, in eScience.
This will allow us to better compare and contrast what we've all done and what we still need to do. The result will hopefully allow us to better collaborate and share of our experiences, i.e. we can better identify who's done what to avoid reinventing the wheel and we can identify who could work together on common problems.
The proposal is not to use the meeting to actually classify what he have at the moment, but rather to brainstorm and agree upon a simple classification schema.
There are obviously many ways to look at workflow and enactment engines. Aspects include: what can be expressed in the different workflow languages; engine implementations and invocation mechanisms; exception handling, reliability, scalability; current and planned tool support including availability and licensing; use of standards; and what are the application domains.
Some existing work is below which we could use as a starting point.
