PGI-WG working session 1
Balazs opening
Morris talk:
PGI reference model
Introduction
Outline:
Planned documents
10 min for the roadmap and structure of the document
Define: 
Production Grid
David: 
Key note from the Italian Bank – large production Grid presented, maybe we should get them in
OGF is open, welcome all
An drew:
Limit ourselves to web services
Aleks:
Data transfer through web service??
Andrew:
Limit scope!
Otherwise we don’t get anything out
All agreed:
Another section: scope

Glossary:
Desktop Grids, Service Grids  Glossary
Etienne:
Good definition of restriction

Delegation  Glossary

Use cases:
PGI: bottom up approach
OGSA: top down approach
Andrew: 
OGSA also use-case driven

Balazs:
Create an OGSA section?
Morris:
Use cases:
SRM – SRD interoperability
Use cases also driving the GIN group
Oxana:
Use cases in table for people to fill out?`
Balazs:
In Glue got a lot of use cases. One has to define which one is useable
Morris:
Use cases:
1 page worth or could refer to GIN?
David:
Concretely say why
Andrew:
Hard to find optimums

Use case: dynamic load balancing, completely independent which Grid
Balazs:
Brokering, load balancing out of scope
Morris:
Use use cases of GIN  skip section 3.1

Have to explain why use cases are important – Cross Grids
Morris:
More data driven in the future

Define context of cross Grids
Andrew:
In one Grid: no need to federate but it’s whole point!!!
Steven:
Work on details of basic use cases!! do not expand on other details!!
Etienne:
User not always fetches data but sometimes only gets access
Balazs:
Concentrate on data staging
Andrew:
Try to define what to be done: the goal!!
Steven:
Define the gaps
Oxana:
No production Grid implements the standards because they are not happy with the specs
Andrew:
Possible to discuss multiple things at once
WSI-BSP, WS-trust, ByteIO, RNS
Many want to stage data with different methods
If you select the intersection you get the emty set
Morris:
This is not true
PGI: get overlap working
Andrew:
Does not believe that this is the way forward
Not expect all resources to implement the same things
Morris:
Current basic use case of e.g. just submit can be nailed down
But maybe not a full view
Steven:
First: foundation of standards
PGI: find out core basic infrastructrure
Balazs:
Limited set of specs on start
Etienne:
Has the will to do the plumbings.
Oxana:
First: JSDL/BES/GLUE
Then: went on to security because it’s important
Plans for the ongoing sessions?!