Hi Laurence, I really like this definitions. But just two small things: at the university here, they define a service as a functionality, that is provided to a customer/user/consumer (in that case a virtual organisation) by using resources. It has a service access point, which is the interface. So, I agree with your definitions, except that I believe that the functionality is provided by the service, not by the resource. This could be important for the paperwork, but should not influence the relationships you outlined. The other thing is, that I miss a relationship between two or more services. just in case this could be useful, Timo
Service: The service is the interface at the site boundary that maps from a generic grid interface to the local system. As the service provides the interface between the grid and a local system, there is a relationship between the service and the site. In addition there is also a relationship between the service and the virtual organization. Services also have to ensure the adherence to agreed common polices, eg access logs, accounting and auditing etc.
Resource: A resource is the functionality that the user would like to use. As the resource is local to the site, there is a relationship between the resource and the site. As the service gives access to the resource there is also a relationship between a resource and a service.
_______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
-- ======================================================================== Dipl.-Inf. Timo Baur Email: timo.baur@lrz-muenchen.de Leibniz-Rechenzentrum Kommunikationsnetze, Netzplanung, D-Grid ------------------------------------------------------------------------ Raum I.2.099 Boltzmannstrasse 1, 85748 Garching Telefon: +49 89 35831-8729 Fax: +49 89 35831-9700