----------------------
 general requirements
----------------------

R001a:
Description of the (initial) requirements of an activity, i.e. the description template the activity has been initially created from. Maybe the requirements (aka. JSDL) record also needs a history for tracking changes to the template.

R001b:
Pointers to dependent activities in order to be able to track the state of (sub)-activities, e.g. in the workflow use case.

R002:
Timestamped state record(s) of the activity (e.g. as defined by the BES state model), i.e. the last change of the state that has been recorded. The last known state is not required to be online, and may differ from the real "current" state.

R003:
Timestamped "provenance" record(s) which tracks the responsibility for the activity. Again, the last known provenance is not required to be online.

R007:
Resource consumption as part of the final activity record.

R008a:
The ability to seal an activity that has been completed.

R008b:
Handling of security and access control policies for activities

R019:
Timestamped job attribute (?) changes for the entire lifecycle.

R020:
Resource usage tracking during runtime.

R022:
Tracking of exceptional states with timestamp and reason.

xR023:
Checkpointing information for a job, given as a pointer to another location.

xR024:
Address of the executing service (presumably BES) of the activity.

xR025:
Data locations used by each activity (?).

xR026:
Status of each sub-activity