Etienne Urbah's position on 2010-03-18

• 'Client-directed processing of submitted Activities' is contrary to the principle of 'Full Automation of Processing'
• 'Manual Data Staging' can easily been replaced by 'Data Pre-Staging' and 'Data Post-Stating' to and from Storage Resources (GLUE StorageService), occurring OUTSIDE the life time of the Activity, plus Automatic Data Staging specified inside the JSDL
• IT experience shows that 'Execution of Activity' is only a little part of 'Data processing', which must begin with careful 'Data Management'
• So I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-23

• Original title of this requirement dated 2010-03-18 was :
  'In order to apply the principle of 'Full Automation of Processing' and to prevent too much complexity inside the Job State Model, specifications will NOT take into account 'Hold' points for Jobs'
• Change the title to 'In order to apply the principle of 'Full Automation of Processing', the Activity State Model SHOULD NOT have 'Hold' States'
• Spreadsheet ID = 75

Etienne Urbah's position on 2010-04-26

• In fact, if the Job State Model is too complex, then the Execution Service will be a mammoth with implementation problems and NO interoperability at the end
• Therefore, preventing too much complexity inside the Job State Model is really important
• So, I suggest to reintroduce prevention of complexity, with following title :
  'In order to apply the principle of 'Full Automation of Processing' and to prevent too much complexity inside the Job State Model, this Activity State Model SHOULD NOT have 'Hold' States'
• Anyway, I still vote FOR this requirement