standard xlink references Enumeration of possible phases of job execution The first phase a job is entered into - this is where a job is being set up but no request to run has occurred. An job has been accepted for execution but is waiting in a queue An job is running An job has completed successfully Some form of error has occurred The job is in an unknown state The job is HELD pending execution and will not automatically be executed (cf pending) The job has been suspended by the system during execution The job has been aborted, either by user request or by the server because of lack or overuse of resources. The identifier for the job This is the information that is returned when a GET is made for a single job resource - i.e. /(jobs)/(jobid) the execution phase - returned at /(jobs)/(jobid)/phase A Quote predicts when the job is likely to complete - returned at /(jobs)/(jobid)/quote TODO - how to encode "don't know" The duration (in seconds) for which the job should be allowed to run - a value of 0 is intended to mean unlimited - returned at /(jobs)/(jobid)/executionduration The time at which the whole job + records + results will be destroyed. returned at /(jobs)/(jobid)/destruction The list of job references returned at /(jobs) ISSUE - do we want to have any sort of paging or selection mechanism in case the job list gets very large? Or is that an unnecessary complication... A reference to a UWS result The element returned for /(jobs)/(jobid)/results A short summary of the error characterization of the type of the error