Activity Instance Document Schema BoF
======================================

Issue: Decide how to proceed; whether it will be a new WG or a part of
       JSDL-WG

- "Activity is a unit of work..." as model can it be hierarchical and
  made up of activities?
  - UDAP Activity can be made up of links to other activities (this
    did not seem to fully answer the question)

- "ActivityId as a unique identifier". It is an EPR in the NEXTGRID
  implementation, but could be WS-Naming instead

- Dependency definition is not clear

- Activity describes an instance

- Most elements are defined as xsd:any and profiled for specific use
  cases

- Proposal: Do this more specifically for certain specs and allow
  extensibility; rather than leaving it open-ended and profiling it
  for specific specs.

- Proposal: Review how JSDL is used in practice and formalize that,
  rather than a big new effort from scratch.

- This could be the instance document describing the Activity instead
  of a 'reified' JSDL (return from bes in some implementations)

- BES implementators (in the room) are not using the Activity element
  to put in other stuff; they are putting things in the JSDL document
  instead

- A more concrete description of an Activity document is shown by the
  unicore presentation

- There is intest for both a snapshot of the 'state' and for the
  complete history
  - It is useful to have complete history record ... for debugging etc