1. OGSA-WG charter discussion Dec. 3, 2003 F2F meeting at ANL

2. We need re-charter Current formal WG charter –Approved September 24, 2002 and posted on GridForge –Very obsolete Assuming WG charter –Agreed at 2 nd interim meeting 2003/2 (?) –OGSA document Chapter 2 –Need some update and add milestones Revised charter for GFSG submission –Proposal: Make out and agreed at this meeting Next step –Formal re-charter approval process

3. Current formal WG charter: Purpose The purpose of the OGSA Working Group is to achieve an integrated approach to future OGSA service development via the documentation of requirements, functionalites, priorities, and interrelationships for OGSA services. Topic areas that we expect to scope and discretize early are common resource model and service domain mechanisms, but the precise set to be addressed will be determined in early discussions. The output of this WG will be an OGSA architecture roadmap document that defines, scopes, and outlines requirements for key services. It is expected that the development of detailed specifications for specific services will occur in other WGs (existing or new). When this document is produced, the WG will consult internally and with the GFSG to determine whether to close or, alternatively, to work to produce a second edition.

4. Current formal WG charter: Milestones GGF5 (July 2002): –BOF to propose working group GGF6 (October 2002): –First draft of OGSA architecture document GGF7 (March 2003): –Second draft of OGSA architecture document. GGF8 (June 2003): –Final draft OGSA architecture document GGF9 GGF10? GGF11?

5. Assuming WG charter 1.To produce and document the use cases that drive the definition and prioritization of OGSA components, as well as document the rationale for our choices. 2.To identify and outline requirements for, and a prioritization of, OGSA services and components. 3.To identify and outline requirements for, and a prioritization of, hosting environment and protocol bindings that are required for deployment of portable, interoperable OGSA implementations. 4.To identify and outline requirements for, and a prioritization of, models for resources and other important entities. 5.To identify, outline, and prioritize interoperability requirements for the various OGSA components. 6.To define standard OGSA profiles, i.e., sets of OGSA components that meet specific requirements. 7.To define relationships between GGF and other standards bodies activities such as W3C, OASIS, and WSI whose work touches upon OGSA-related issues.

6. New Charter: Scope 1.document the use cases Proposal: Yes, we will do this 2.OGSA services and components Proposal: Yes, we will do this 3.hosting environment and protocol bindings We have no text now 4.models for resources and other important entities Proposal: Yes, but we should refine the text 5.interoperability requirements We have no text now 6.standard OGSA profiles We have no text now 7.relationships between GGF and other standards bodies activities Proposal: Yes, we will do this

7. New Charter: Milestones OGSA usecase –Final draft to editor at GGF10 (feasible?) OGSA document –Major update at GGF19 –Final draft to editor at GGF11 –2 nd version for hosting environment, interoperability, and profile? OGSA roadmap –First draft at GGF11 (feasible?)

8. New Charter: It is expected that the development of detailed specifications for specific services will occur in other WGs (existing or new)

9. Next step Formal re-charter approval process