6c)     3.9 Status

"This property represents the completion status of the job" and goes on to say that "it must support the following values:

a)      completed

b)      failed
c)      aborted
d)      held
e)      queued
f)      started
g)      suspended"
 
This is a rather batch system specific approach. In a grid usage record we are talking about 'final' or completion status of a grid job. In this sense differentiating between "held, queued, started, suspended" has not much relevance. It would be better to merge these 4 active states into one "unfinished" state.
 
BTW, NorduGrid uses the Finished, Failed, Killed, Deleted labels for completed job states. The NorduGrid "Finish, Failed, Killed" corresponds to the GGF "completed, failed, aborted", respectively while the NorduGrid "Deleted" does not exists in th GGF states (see page 26 about nordugrid-job-status in [3])
 

The statement "This property must contain data of type integer" implies that the proposed job states above also should carry an associated number, in this case.

Evaluation: Text and definition will be changed to user tokens for status. A base set will be defined, but the comprehensive set of values will be extensible.

9)      The appended schema mandates the inclusion of the ?status? field.  This is described as a must in section 3.9 but is not specifically included as a must in section 10.6.  Further the allowed values in 10.6 are not enforced in the Schema (this might be okay as other values are allowed).  Suggest that this is removed as a mandatory record as it is not applicable in the general case (what about data records?)

Evaluation: Status should be a token (see above) and should be optional.