[ogsa-wg] Proposed agenda for June 12th call

Hi all,

The following is a proposed agenda for OGSA-WG telecon on June 12th
Monday from 5pm to 7pm (CDT).

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


Screen share service will be provided.
   URL:         http://ogsa.glance.net
   Session key: 0612
See more explanation:
http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html

1) Early discussion (20 min)
         Note taker assignment
         Roll call
         Telecon minutes approval (June 8th)
https://forge.gridforum.org/sf/go/doc13592?nav=1
         July F2F update (if any)
         Action Items status review (see the bottom of this email)
         Agenda bashing

2) CDDLM & EMS (Jun and Hiro, 40 min)
         Review CDDLM-WG's feedback on Andreas' CDDLM scenario.

         Jun and Hiro to provide a CDL document example.

> Last week on the ogsa call we reviewed the EMS scenario (posix
> application) that includes a simple interaction between JSDL and CDL
> documents. The major missing piece at the moment is the CDL document,
> as an actual XML document. Can I ask you to write up such a document?
> I am only interested in the 'top level' (sorry for using perhaps the
> wrong terminology) CDL BLAST document. I think it only has to
> highlight
> 1) hostname as lazy (so that we can show how the JM may choose to
>    provide that value)
> 2) BLAST binary deployment
>
> Last time we talked about it (April F2F) I think this discussion got
> somewhat sidetracked by, among other things, the observation that a
> general posix application component also had to be defined to support
> the 'top level' CDL BLAST document. For this EMS scenario I think it
> is *not* necessary to have such a general component defined as long as
> there is sufficient explanation accompanying the BLAST CDL document on
> what underlying definitions are assumed.

3) Wrap up (10 min)
         AOB

<*NEXT CALL*>
June 15 (Thu): Security & BSP Public Comments review (Frank and Takuya)
                Architecture & Glossary 1.5 (Andreas and Jem)
June 19 (Mon): Information model (Ellen and Fred)
                Roadmap 1.1 (Hiro, ChrisJ, and Jem)
June 22 (Thu): EMS scenarios (Steven and Andreas)
June 26 (Mon): Security & BSP Public Comments review (Frank and Takuya)
                CDDLM & EMS (Jun and Hiro)

<*ACTION ITEMS*>
 From June 8 call
- EMS team to review data staging scenario (section 5 of
   https://forge.gridforum.org/sf/go/doc13591?nav=1 )
- Add sequence diagrams to the scenarios:
     - Andreas will do the "Install application" scenario (3.1)
     - Mike will do the "Install application using ACS" scenario (3.3)
     - Other volunteers welcome. (Andreas will ask Donal for the EPS
       scenario)
- Andreas will merge draft scenarios and sequence diagrams to the
   "EMS Architecture Scenarios" document

>From May 22 call
- Jay will contact Platform (Chris Smith) and Condor (Miron Livny)
   to get feedback on pros / cons of the two rendering approaches
- Darren/Andreas will take the Modeling position paper and
   discuss it within the JSDL-WG as well

>From April 5 F2F meeting
- Marvin to send e-mail that explains concerns on compliance suite
   by GGF & EGA.

Deferred
- Frank to write up and send to the list a one page summary of
   the authorization call-out proposal.
   (April 24 call, postpone until June 14)
- Jay check and find out relatively small funding to Globus
   to develop document on their security work (April 6 F2F)
- Hiro to schedule a discussion in the OGSA F2F after the
   converged specs drafts are released to discuss which sets of
   specs to use within OGSA.  (April 4 F2F)
-- 
Hiro Kishimoto