* It may be useful to provide an additional property (we may call it “CommandList”) representing the list of all commands issued for a given job.
What do you mean by "command"? Typically there is only one executable, so if that's what you mean I don't quite follow you.
Well, we were using the term "command" to indicate the Job Interface Operations described in Section 5.2. Basically, for administrative purposes it could be useful if the sequence of operations performed on each job is logged and could be accessed in some way. But probably this operation is not strictly related to job submission and should be considered in a separate interface.
Ok. I personally can't come up with a use case, but that doesn't mean one doesn't exist. Care to elaborate why this is useful? Do you not trust that the service will do what you tell it to do? Peter