We will start the call soon... Some detail in agenda below: Keisuke Fukui wrote:
Folks,
Here is an agenda for the call tomorrow. See you there!
### Proposed Agenda
1. Agenda bashing, role call, note taker & time keeper. (10min) 2. Planning for the face-to-face. (30 min) I attached proposed time table at the end. To decide: Starting time, relevancy of the agenda items, addition or subtraction for the time allocation, owner of the item, etc... 3. Updates (10 min) Issues List, Research on CDDLM, security, etc. 4. Wrap up. (5 min)
### Logistics for the call Date & Time: May 18 Wed 20:00 EDT/May 19 Thu 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111
------------------------------------------------------------------------
Proposed Timetable for the face-to-face meeting on May 23 and 24
*** DAY 1 *** 1. Agenda bashing, role call, note taker & time keeper. (10min) 2. OASIS SDD TC updates (1 hour) - history - plan and milestones - relationship to GGF CDDLM-WG - collaboration with ACS-WG; scope, participation ... 3. ACS issues list overview (1 hour) - Itemization - Use of the tracker in gridforge. 4. Interface between ACS and CDDLM. (1 hour) - Summary report on CDDLM component model. - "addFile" in CDDLM deployment API. There are two possible mapping (relationship) between them and ACS/ARI. 5. Security (1 hour) - General understanding on the range of the security topics in ACS. - Minimum requirements on ACS spec. - (There are multiple and extensive topics and issues in security area. To what extent, we need to address those. Authentication, authorization, encription, digital signiture, etc..) 6. Other items in issues list (0.5 hour) - Specification on the data transport to be used with ACS. - WSDM management interface in ACS. - Updates on OGSA naming activity.
7. New use cases (1 hour) - Shipping - Federation
8. Interoperability Goal (1 hour) - Target systems. - Range or scope.
*** DAY 2 *** 9. NAREGI integration (1 hour) - Use case description in the WG draft. - ACS interface example to NAREGI type of deployment engine. - Requirements 1: multiple compiled binaries in ACS. - Requirements 2: data caching in ACS.
10. WG draft writing plan. (1 hour) - Review of the table of contents. - Editorial work. - Drafting additional contents, for example, new use cases, security requirements, ARI interface detail including WSDL, AAF in detail.
11. GGF14 session plan (1 hour) - Deadlines Draft document deadline: May 27, 2005 Session request deadline: June 3, 2005 - Chairs update - critical updates and training: Monday, 27 June 2005
12. Management and/or strategy in the ACS activity. (1 hour) - Regular teleconference - Recruiting in the European Grid community.
13. OGSA roadmap report and SCRM collaboration (1 hour)