Munich meeting on 2010-03-20

• Propose requirement with title  'The vector limits for each of the vector operations might be exposed in an Information Service.'

Etienne Urbah's position on 2010-04-13

• This requirement can be achieved using extensions of the 'Capability_t' list of the 'Capability' attribute of the 'Endpoint' entity of the GLUE model, and requirement IS2.2
• For clarity, I suggest to change the original title to
  'If the Execution Service provides vector functionalities, then it MUST publish the vector limits according to the GLUE model.
  If these vector functionalities have different vector limits, then they MUST be grouped inside separate Endpoints having each a homogeneous vector limit.'
• Anyway, I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• Source = Draft Spec
• Bad prerequisite on Information Service
• Therefore, change title to  'The vector limits for each of the vector operations SHOULD be exposed'
• Spreadsheet ID = 8

Etienne Urbah's addition on 2010-04-21

• Today's title change was decided WITHOUT looking at the current page, which already proposed an improved title, and I propose it again :
  'If the Execution Service provides vector functionalities, then it MUST publish the vector limits as properties of GLUE Endpoints.
  If these vector functionalities have different vector limits, then they MUST be grouped inside separate GLUE Endpoints entities having each a homogeneous vector limit.'
• Anyway, I confirm my vote FOR this requirement

Amsterdam meeting on 2010-04-28

• Add comment  'Problem GLUE2 space, for example: createQuickActivity[1000], createValidatedActivity[10] - this information must be exposed when they have limits'
• Agreed YES