opencsa-liaison — archive

[Sanjay Patil]

Minutes of the SCA SC Liaison Subcommittee Conf-Call
Dec 11, 2008 10 AM Pacific


1. Roll Call


   Present - Jeff, Anish, Dave, Sanjay, Martin, MikeE
   (Policy, SCA-J, Bindings, BPEL, Assembly)


2. Scribe Assignment


   Sanjay


3. Agenda Bashing


   Approved


4. Approval of transcript of Dec 4, 2008
   http://lists.oasis-open.org/archives/opencsa-liaison/200812/msg00003.html


   Approved


5. New Issues
  a> Cross SCA TC Conformance
     http://lists.oasis-open.org/archives/opencsa-liaison/200812/msg00006.html
     Submitter: Martin Chapman
     Email discussion: http://lists.oasis-open.org/archives/opencsa-liaison/200812/msg00008.html
 
    
     Logged as http://osoa.org/jira/browse/LIAISON-4
     Need to separate out the two topics in this issue:


Dependency of SCA specifications on each other e.g. Compliance with Binding spec needs compliance with Assembly and Policy specs. It will be useful for LSC to make recommendations to the various SCA TCs regarding expression of their dependencies.

Each specification could identify and spell out its dependencies.



Branding: What does it mean to be compliant with the SCA brand? Does SCA compliance indicate compliance with a certain set of SCA specifications?

The main question is – what specific SCA specifications can we agree to be part of the umbrella SCA brand? The question about where to define this umbrella SCA brand can be handled separately (SCA Assembly specification being a likely answer).

   
AI for Martin – Raise two separate issues for the above two topics.



6. OpenCSA Project Management
  a> Schedule Review

Sep 15, 2008 - Raise the bar for opening new issues (for all TCs)

Sep 29, 2008 - Incorporate RFC 2119 language

Nov 15, 2008 - Detailed design for testing work

Jan 23, 2009 - Assembly TC to start 1st Public Review (60 day)

Feb 23, 2009 - Other TCs to start 1st Public Review (60 day)

May 31, 2009 - Finish all the work

July 4, 2009 - Submit specs to OASIS for OS vote


AI for Anish/Mike - Get back to LSC with schedule for testing work. Anish plans to put the question on next testing subcommittee’s call.

Anish posted a question to the testing subcommittee - http://lists.oasis-open.org/archives/sca-assembly-testing/200812/msg00001.html.

Mike agrees to bring up the question for discussion on the next conf-call (since Anish may not be present on that call). AI remains open

AI for Dave - to get back to LSC after having a SCA-J TC discussion about the possible schedule
  Dave posted an update to LSC - http://www.oasis-open.org/apps/org/workgroup/opencsa-liaison/email/archives/200812/msg00005.html

   SCA-J TC has decided to raise the bar for opening new issues - new issues must be accompanied with proposals.   Currently open issues are getting assigned aggressively.

   Schedule discussion to continue in the SCA-J TC.
   AI remains open.


AI for Bryan - to get back to LSC with anticipated schedule for the SDO TC
  Bryan not present on the call.
  AI remains open.
   
   b> Requirement of 2 compliant implementations
        All the SCA TCs are likely to face the issue of not having 2 compliant implementation (a criteria for declaring completion of the TC’s work). LSC can acknowledge and raise this issue to SC but can not resolve on its own.

     LSC decided to raise this issue to SC.


   c> Any other blocker issues?
      None brought up.


7. Next conf-call
        Dec 18, 2008


8. AOB
        None.