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
• This does NOT forbid the Execution Service to publish the same information through its own specific interface
• Depending on what the Execution Service publishes to the Information Service, the Activity attributes MAY contains less information than Activity Status directly queried from the Execution Service
• This requirement is restricted on NOT yet finished Activities.  For already finished Activities, see IS9.
• 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

• This requirement was proposed on 2010-03-26
• 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 = 164
• Open (still unclear)