Etienne Urbah on 2010-03-26

• Propose requirement with title  'For requests querying Activity Status, the Information Service SHOULD support query languages'

Etienne Urbah's position on 2010-04-14

• This requirement introduces complexity inside the Information Service
• Therefore, this requirement is NOT likely to be achievable by a grid service having already performance requirements
• 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.
• Supporting Xpath 1.0 is one thing, and I vote FOR it
• But supporting additional query languages looks like a framework accepting plug-ins, and I am afraid of such great complexity (do we really need that ?)

Morris, Balazs and Etienne on 2010-04-21

• Dropped (rejected), because of information service unclarity

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'
• Also, remove the specific list of query languages, like in requirement LB7
• Change the requirement status from 'Rejected (Bad prerequisite on Information Service)' to 'Re-proposed'

Amsterdam meeting on 2010-04-28

• Spreadsheet ID = 166
• Open (still unclear)

PGI telcon on 2010-05-20

• Agreed YES