Hi all,

The following is a proposed agenda for OGSA-WG telecon on <DATE>
Thursday from 8:30am - 10:30am  (CDT).

Dial-in numbers for Thursday:
   Free: +1-888-452-0308
   Intl/Toll: +1-484-644-0505
   PIN:  71815

Screen share service will be provided.
   URL:         http://ogsa.glance.net
   Session key: 0824
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 (Aug. 21st)
         https://forge.gridforum.org/sf/go/doc13750?nav=1
         Action Items status review (see the bottom of this email)
         Agenda bashing

2) OGSA F2F meeting agenda discussion (20 min)
         Establish F2F agenda on Sep. 14 (Thur) and 15 (Fri)
         https://forge.gridforum.org/sf/go/wiki1555?nav=1

3) CDDLM joint discussion #1 (40 min)
         Follow-up discussion on August 3rd.

(3-1)
>> PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in
>>              CDL documents
> 
>   - Jun thinks that this is not a good idea because ID must be unique
>     in the document and CDL inheritance may break this guarantee by
>     creating duplicate IDs in the resulting document. CDL has a
>     mechanism based on non-unique ids.
> 
>   AI-0803e: Jun will provide an example of the CDL mechanism and why
>             using ID/IDREF is not a good idea.

(3-2)
>> PROPOSAL 2: Eliminate the EnvironmentVariable concept from the
>>             PosixComponent (CDL plugin)
>> 
>> * Proposal 2 is specific to the OGSA EMS scenarios document.
> 
>   Agreed that this is a reasonable resolution for resolving the
>   problem with the PosixComponent and is sufficient for the EMS
>   Scenarios document.
> 
>   AI-0803f: Jun will update the CDL document to remove the Environment
>             variables

(3-3)
>   - A normative definition of PosixComponent 
>     - At the moment there is no such definition; there are only some
>       examples.
>     - Agreed that a normative definition is necessary and that it is
>       not part of CDL version 1.0. Also it is probably too late to
>       leave it for CDL version 2.0---since it is not scheduled yet.
>      - Tentative agreement that this should be a work item for
>        CDDLM-WG between these two document release
>      - Dejan and Jun with discuss this in the CDDLM-WG and seek
>        approval as a work item after CDL 1.0.

4) CDDLM joint discussion #2 (20 min)
        OGSA-WG and EGA Reference Model WG started to identify
        similarities and differences between current works.
        EGA Ref Model's Dependency Graph and Life Cycle of Grid
        Components looks very relevant to CDDLM-WG's work.

        http://www.gridalliance.org/en/WorkGroups/ReferenceModel.asp

        OGSA-WG will have a GGF18 session on Tuesday 4-5:30pm for this
        discussion.

        https://forge.gridforum.org/sf/go/wiki1560?nav=1

5) Wrap up (10 min)
         AOB

<*NEXT CALL*>
https://forge.gridforum.org/sf/go/wiki1477?nav=1

   Aug. 28 (Mon): Security (Takuya and Frank)
   Aug. 31 (Thu): EMS scenarios (Andreas and Steven)
                  EMS & Data joint scenario (Allen, Dave Barry, Steven,
                  and Andreas)
   Sep. 4  (Mon): No call (Labor Day)
   Sep. 7  (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro)

<*ACTION ITEMS*>
https://forge.gridforum.org/sf/go/wiki1569?nav=1

 > From Aug. 21 call
   AI-0821a: Hiro to talk to Jun and CDDLM group about EGA & CDDLM
             comparison proposal.
   AI-0821b: Hiro to talk to Jem about EGA & OGSA glossary comparison

 > 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,?)
   AI-0817b: Stephen Davey will do a cut down parameter sweep scenario
             focusing on the JSDL+BES+Data Transfer/Staging service

 > From Aug. 10 call
   AI-0810a: Donal to look into the relation of the EPS and CDL
             (retrieval, update, etc). (Eventually this should probably
             become a separate scenario.)

 > From Aug. 3 call
   AI-0803e: Jun will provide an example of the CDL mechanism and why
             using ID/IDREF is not a good idea.
   AI-0803f: Jun will update the CDL document to remove the Environment
             variables

 > > 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>
- Steve McGough & Andreas to do a mapping from the current JSDL
   elements / terminology into the new information model structure
   (Proposed split into Description and Requirements)
   (from July 18th F2F, By GGF18 as original discussed.)
----
Hiro Kishimoto