OGF23 JSDL Session II - Activity Schema 
=======================================

* Philipp presented the current use case document with requirement
  list. Notes/changes also taken in the document directly.

* Additional use cases:
** Activity interface use case: Computational steering with potentially
   multiple actors on activity and access control issues

  Action: Donal to chase up use case owner for visualization and
          steering

** Action: Philipp to do NEXTGRID use case

** Action: Fred (Philipp) to complete the "Give me a title, please"
           use case

* Is the main usage case for this work the retrieval of static
  (archival) information; or dynamic information (e.g., the document
  returned by BES for an in-progress activity)?
  - Still undecided, something to be determined from the use
    cases/requirements analysis. Use cases seem to point more towards
    static content but there is no decision yet.

* [terminology] change of management state (provenance state)

* Is the Activity just a BES Activity or not? An ID that persists
  between BES submissions or tracking multiple activity IDs (e.g.,in
  case of failure/restart) seems to imply something broader than the
  BES model
  - The scope is still not clear; use cases are still fairly (and
    intentionally) broad. Will scope down to a tractable set before
    attempting a specification