[cddlm] Proposed agenda for Aug. 3rd call

2 Aug 2006

      Hi all,

The following is a proposed agenda for OGSA-WG telecon on Aug. 3rd
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: 0803
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 (July 31)
         - https://forge.gridforum.org/sf/go/doc13712?nav=1
         Action Items status review (see the bottom of this email)
         Agenda bashing

2) July F2F meeting approval (Hiro and Andreas, 20 min)
         Materials and minutes are available at meeting folder
https://forge.gridforum.org/sf/docman/do/listDocuments/projects.ogsa-wg/docman.root.meeting_materials_and_minutes.interim_meetings.2006_summer_interim

         Approve minutes 20060720-am-{1,2,3} and of
         the Joint Mgmt committee meeting.

3) CDDLM joint discussion (Jun, Dejan, and Hiro, 60 min)
         minutes from OGSA F2F meeting on July 20.
> PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document 
>  	     and the CDL components
> PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in
>     	     CDL documents
> 
> * Proposals 1a and 1b are recommendations for the further development of CDDLM
> 
> PROPOSAL 2: Eliminate the EnvironmentVariable concept from the PosixComponent
> 	    (CDL plugin)
> 
> * Proposal 2 is specific to the OGSA EMS scenarios document.

        See attached minutes.

4) Wrap up (10 min)
         AOB

<*NEXT CALL*>
Aug.  7 (Mon): Security (Takuya and Frank)
Aug. 10 (Thu): EMS scenarios (Andreas and Steven)
Aug. 14 (Mon): Roadmap (Chris)
Aug. 17 (Thu): Info/data model (Ellen and Fred),
                EMS and data joint scenarios (Allen and Steven)
Aug. 21 (Mon):
Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro)
Aug. 28 (Mon): Security (Takuya and Frank)
Aug. 31 (Thu): EMS scenarios (Andreas and Steven)
Sept. 4 (Mon): No call (Labor Day)
Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro)

<*ACTION ITEMS*>

 > From July 31 call
- Ellen to send an email to Chris Jordan with the information
   needed to add these two documents to the OGSA Roadmap
- Hiro Schedule a joint call with OGSA-Data to explain the
   Information model work before GGF18.
   + This could be one agenda item on the joing EMS/Data call
     already being schedule.

 > From July 20 F2F
- Andreas and Hiro to revise the EMS scenario document (i.e. examples)
   so that proposal 2 is fulfilled
   + Andreas will merge Hiro's updates into the next draft
- Jun to feed back proposals 1a and 1b to the CDDLM Working Group,
   i.e. pass back the minutes to the WG. Ask Michel in case of any
   questions related to these proposals.
- 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.

 > From July 17 F2F
- BES-WG chairs to ask the data group to define the
   filesystems as their work product

- 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, postpone until Aug. 17)
-- 
Hiro Kishimoto

** Participants **

David Snelling, Fujitsu
Hiro Kishimooto, Fujitsu
Andreas Savva, Fujitsu
Michel Drescher, Fujitsu
Jay Unger, IBM
Jun Tatemura, NEC (via phone)

* Jun walks the group through the document "Designing a POSIX component in CDL"
  written by Jun and with latest edits from Hiro.

* Hiro asks Jun to correct his edits while walking through the document.
  - The newly added elements "cmp:CodeBase" and "bcp:ArchiveType" are 
    effectively the same as "bcp:Binary".
    * An example in the document is provided how to use these elemeents.

* Andreas asks whether the "cdl:ArchiveTye" element is a global element, or an 
  anonmous sub-element of "cdl:PosixApplication". 

* bcp:PosixApplication is a base type. It is extended to e.g. define
  the BLAST appplication ddescription for a CDDLM system.

* [example XML document] Andreas asks whether the name of a declared file
  system can be a child element instead of being part of the element name 
  itself.
  - Yes, this is possible, as given in a proposal later in this document.

* Andreas asks whether there is a way to define that the value of an element 
  comes from another element in that CDL document, or whether that is out of 
  scope of CDDLM.
  - It is not defined by either CDL language spec or component model spec.
    It should be part of the BasicPosixComponent spec.

* Hiro proposes to remove the Environment Variable concept from CDDLM.
  - Because components can give predefined information that otherwise
    would have to be encoded in Environment Variables.
  - The Environment Variables concept os too general to transport such 
    semantically special information like cdl:Hostname (where the applicaiton
    is to be deployed to).

* The group discusses the Environment Variable cconcept, particularly the 
  possibility that, through CDL, the values of certain environment variables
  can be retrieved from the target deployment system. The group shows 
  consensus that the CDL document needs to carry enviroment variables that
  must be set on the target system so that the configured application can run.

* The group discusses the relationships between "cdl:FileSystem" declarations 
  and the definition of "lazy environment variables". In particular, the group
  is wondering about the exact mechanismms how the operation that provides the
  provisioning of the requested FileSystem feeds back the moint point of that
  file system into the appropriate environment variable

PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document 
 	     and the CDL components
PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in
    	     CDL documents

* Proposals 1a and 1b are recommendations for the further development of CDDLM

PROPOSAL 2: Eliminate the EnvironmentVariable concept from the PosixComponent
	    (CDL plugin)

* Proposal 2 is specific to the OGSA EMS scenarios document.

** Action Items **

1) Revise the scenario document (i.e. examples) so that proposal 2 is fulfilled
   (Andreas, Hiro)

2) Feed back proposals 1a and 1b to the CDDLM Working Group, i.e. pass back 
   the minutes to the WG. Ask Michel in case of any questions related to these 
   proposals.
   (Jun)