BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061023T220000Z DTEND:20061024T000000Z TRANSP:OPAQUE SEQUENCE:2 UID:040000008200E00074C5B7101A82E00800000000908183F164ECC6010000000000000000100 0000076824268C7E4DB45977CBD7092D2808F DTSTAMP:20061023T025306Z DESCRIPTION:When: 2006年10月24日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1023\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (if available)\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F update (20 min)\n\n3) HPC cluster usecase for EGA reference model (Paul and Hiro\, 60 min)\n In order to clarify relationship between OGSA architecture\n and EGA reference model\, design team is trying to write-up\n HPC cluster usecase for EGA reference model assuming that\n OGSA is SOA and Web-service based instantiation of EGA\n reference model.\n\n Hiro's draft slides:\n - https://forge.gridforum.org/sf/go/doc13939\n Meeting minutes from Oct. 9th:\n - https://forge.gridforum.org/sf/go/doc13942\n\n> AI-1009a: Review slide 6 again and clarify what the problem is\n> (Reference Model Design Team)\n> AI-1009b: Review the Reference Model 'Manage Job' in more\n> detail. Specifically look at it from the perspective of\n> an enterprise application (e.g.\, a 3-tier app) (Reference\n> Model Design Team)\n> AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n> - Perspective of submitter vs platform provider and the\n> hierarchical model connection\n\n Design team will bring revised slides to the call.\n\n4) Glossary discussion (Jem Treadwell\, 20 min)\n\nJem's email:\n> Per discussion on the October 9th meeting\, I've now posted a discussion\n> document for the Glossary. The primary objective is to converge the EGA\n> Reference Model glossary and the OGSA glossary\, and the target for\n> completion is OGF19.\n> \n> The discussion document is posted in the gridforge Glossary folder at\n> http://tinyurl.com/yzwt4c\, along with the current draft of the Glossary.\n> \n> I received some initial comments from Olegario Hernandez\, who has been a\n> regular contributer to each version of the OGSA Glossary. These\n> comments are posted in tracker 5617 - there's a link to the tracker in\n> the discussion document. \n> \n> I believe we had agreed that we would discuss the terms initially by\n> e-mail and with discussions as needed bi-weekly on the regular Monday\n> OGSA calls. I propose that we begin with a discussion on next Monday's\n> call\, as the last agenda item to minimize the pain :0) For anyone who\n> wants to get a head start\, I propose to look at "enterprise" and related\n> terms first (and\, from his comments\, I think Olegario would second that\n> proposal!). \n\n3) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 26 (Thu): EMS scenarios\, Security\nOct. 30 (Mon): DMTF work register\, OGSA roadmap\nNov. 2 (Thu): Information/data modeling\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\nNov. 9 (Thu): F2F prep\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Oct. 9 call.\n AI-1009a: Review slide 6 again and clarify what the problem is\n (Reference Model Design Team)\n AI-1009b: Review the Reference Model 'Manage Job' in more\n detail. Specifically look at it from the perspective of\n an enterprise application (e.g.\, a 3-tier app) (Reference\n Model Design Team)\n AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n - Perspective of submitter vs platform provider and the\n hierarchical model connection\n\n > From Oct. 5 call.\n AI-1005a: Alan Sill willing to take responsibility for pushing\n the process for getting a charter ready (by Oct. 26)\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 26)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 25 call.\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next EMS call (Oct. 26):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR