All,

It has been brought to my attention that the BES spec is mute on how long information about the status of an activity is kept around once it has transitioned to cancelled, finished, or failed. (This is a problem with many queuing systems as well.) I propose that I add a sentence explicitly stating that it is undefined how long status information will persist once an activity enters one of those three states.

Thoughts?

A

Andrew Grimshaw

Professor of Computer Science

University of Virginia

434-982-2204

grimshaw@cs.virginia.edu