Etienne Urbah on 2010-03-17

• Propose requirement with title  'Each Service MUST publish its static properties (Name, Type, Endpoints, ...) to the Information Service in conformance with GLUE recommendations'

Etienne Urbah's position on 2010-04-13

• In order to read the static properties of a Service (Name, Type, Endpoints, ...), Clients MUST NOT be required to implement a Service specific interface, but MUST be able to use a standard GLUE client interface
• Therefore, each Service MUST publish these properties to the Information Service in conformance with GLUE recommendations (probably as an Information Provider)
• This does NOT forbid the Service to publish the same information through its own specific interface
• I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• Suggested to be dropped (rejected), because it is unknown what an information service is

Etienne Urbah's retry on 2010-04-21

• There is perhaps NO Information Service, but there MUST be an robust Information functionality
• Requirement IS2.1 about publication of Endpoint properties could be merged with the current requirement
• So, provide following improved title :  'Each Service MUST publish its properties (Name, Type, Endpoints, ...) and the properties of its Endpoints in conformance with GLUE recommendations'
• Change the requirement status from 'Rejected (Bad prerequisite on Information Service)' to 'Re-proposed'

Amsterdam meeting on 2010-04-28

• Spreadsheet ID = 163
• Open (still unclear)

PGI telcon on 2010-05-20

• Dropped (Duplicate of IS3)

Etienne Urbah's position on 2010-11-17

• Requirement IS3 does NOT explicitly mention conformance with GLUE recommendations
• Therefore, requirement IS1.1 is NOT really a duplicate, and re-propose it