OGSA-EMS Information Services – Wednesday 6:00-6:45

The OGSA-EMS architecture was sketched out over three years ago. Since then the lowest level components, e.g., OGSA-BES, OGSA-ByteIO, RNS,  have been developed, and higher level components, e.g., RSS, are under development. At this point it is time to tackle the OGSA “information services” problem. BES containers and other services have “resource properties”, “metadata”, “attributes”, or whatever you want to call them. What is needed is a standard place and mechanism to query over the attribute space. For example, services such as MDS in Globus, Collections in Legion, etc. In this session we will begin the discussion of how to attack this problem. We invite others, e.g., Info-D group members, to attend.

Proposed Agenda

            Agenda bashing

            Use case and requirements (e.g., I want to schedule a job described by a JSDL document – how do I go about finding resources.)

            Existing schemes and specifications

is a simple XML database sufficient

push versus pull

            Discussion

            Action items