Hi all,

The following is a proposed agenda for OGSA-WG telecon on
Monday from 4pm to 6pm (CST).

The dial-in number for Monday;
   US:    +1 718 3541071 (New York) or
          +1 408 9616509 (San Jose)
   UK:    +44 (0)207 3655269 (London)
   Japan: +81 (0)3 3570 8225 (Tokyo)
   PIN:  4371991
   See more information:
   - https://forge.gridforum.org/sf/go/wiki1477

Screen share service will be provided.
   URL:         http://ogsa.glance.net
   Session key: 0122
   See more explanation:
   https://forge.gridforum.org/sf/go/wiki1584

1) Early discussion (20 min)
         Note taker assignment
         Roll call
         Telecon minutes approval (Jan. 18)
         - http://forge.gridforum.org/sf/go/doc14099
         OGF19 and March F2F update
         Action Items status review (see the bottom of this email)
         Agenda bashing

2) EGA reference model discussion (Paul and Hiro, 30 min)
         Session plan (detailed agenda and invitees) for OGF19
         reference model session (4-5:30pm, Monday).

 >   AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case
 >             slides and make appropriate changes to indicate where the
 >             CIM Profile would fit in and how it would link into the
 >             Reference Model.
 >   AI-1023d: Paul will add more items to list on slide 6 of the HPC
 >             Cluster use case
 >   AI-1023g: Hiro will look at other parts of slide 5 and identify
 >             further possible refinements of this use case.

         Reference Model WG's charter draft (BoF at 6-7:30pm, Thursday)

3) OGSA Glossary discussion (Jem Treadwell, 20 min)

4) OGSA information/data modeling discussion (if Tom is available)

5) OGSA roadmap document status (if Chris Jordan is available)

6) Wrap up (10 min)
         AOB

<*NEXT CALL*>
https://forge.gridforum.org/sf/go/wiki1477

Jan. 25 (Thu) OGF19 prep (Tom and Hiro)
               OGSA info/data modeling (Tom and Ellen)

<*ACTION ITEMS*>
https://forge.gridforum.org/sf/go/wiki1569

 > From Jan. 18 call

 > From Jan. 15 call

   AI-0115a: Ellen will send out the link to a DMTF feedback
             template form.

   AI-0115b: Ellen will summarize the review of the DMTF documents and
             review the text at a future call.

 > From Nov. 30 call
     AI-11.30a: Michel to talk with Tom and Ellen on how to go about
                documenting his current proof of concept in the Info
                model Arch doc.

 > From Nov. 9 pm F2F.
     AI.11.09.pm-a: Ellen and Tom to write up a "Information Model
                    profile document: BES Container"
     AI.11.09.pm-c: Andrew to produce a document drafting the definition
                    of QoS
     AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future
                    involvement to create profile(s) on, e.g. BES, JSDL
                    etc.

 > From Sept. 15 OGSA F2F
   AI-0915d: Tom will post BP base faults issue to tracker

 > From Aug. 17 call
   AI-0817a: Dave Berry and Jay Unger will approach groups (GIN,
              Globus, etc) that have implemented practical grids and
              start a discussion on how they handle data:
              - how data is treated as a resource that can be scheduled
              - how transfers are modeled
              - how files are advertised
              - how applications find files (query, by knowledge,?)
              (Due Oct. 9)

 > From July 20 F2F
- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to
      contribute use cases.
- Andreas to go through the minutes and formulate a reply mail to
      Geoffrey on each artifact covered in these minutes.

Postponed:
Until next reference model call (Jan. 22nd):
   AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case
             slides and make appropriate changes to indicate where the
             CIM Profile would fit in and how it would link into the
             Reference Model.
   AI-1023d: Paul will add more items to list on slide 6 of the HPC
             Cluster use case
   AI-1023g: Hiro will look at other parts of slide 5 and identify
             further possible refinements of this use case.
----
Hiro Kishimoto