Etienne Urbah on 2010-03-26

• Propose requirement with title  'For already finished Activities, the Information Service SHOULD accept requests querying the Activity Status, but MAY return an error'

Etienne Urbah's position on 2010-04-14

• The GLUE model clearly states that Activities are grid entities
• Therefore, the Information Service MUST provide an interface for Clients to read attributes of any Activity on which they are authorized, in particular its Status, and optional Status extensions
• But providing the Status of ALREADY FINISHED Activities requires management of persistent information, which is better achieved by a dedicated Logging and Bookkeeping Service (see LB8).
  Therefore, the Information Service MAY be unable to handle ALREADY FINISHED Activities, and MAY then return an error.
• This requirement is within scope for the Information Service, and should be out of scope for the Execution Service
• Anyway, it is better to keep that clearly written down, so I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• Dropped (rejected), because of unclarity of information service

Etienne Urbah's retry on 2010-04-21

• There is perhaps NO Information Service, but there MUST be an robust Information functionality
• So, inside the title, replace 'Information Service' by 'Information functionality'
• Change the requirement status from 'Rejected (Bad prerequisite on Information Service)' to 'Re-proposed'

Amsterdam meeting on 2010-04-28

• Spreadsheet ID = 165
• Open (still unclear)

PGI telcon on 2010-05-20

• Agreed YES