Draft minutes of Feb 19 LSC conf-call

Title: Draft minutes of Feb 19 LSC conf-call

Draft Minutes of the OpenCSA LSC Conf-call 

Feb 19, 2009 - 10 AM Pacific

1. Roll Call 

MartinC, DaveB, Anish, Jeff, Sanjay

[SCA Assembly, SCA Policy, SCA Java, SCA Bindings, SCA BPEL]

2. Scribe Assignment 

Sanjay

3. Agenda Bashing 

Approved

4. Approval of transcript of Feb 5, 2009

    http://lists.oasis-open.org/archives/opencsa-liaison/200902/msg00003.html

Approved

5. Action Items

   a> Anish to ensure feedback from SCA-Bindings TC for conformance dependency

Done

   b> Sanjay to capture the feedback from all TCs and summarize

Open

6. OpenCSA Project Management

a> Approval process for testing material

Test artifacts can have an independent life cycle than that of the covered specifications. Test assertion documents can be standalone documents with pointers to the specifications they cover and also pointers to the test cases that are maintained separately (say in OASIS subversion).

Conformant implementations are required to conform to the 2119 statements in the concerned specifications and it is assumed that such conformant implementations will also conform to the associated test assertions. However currently there is no explicit statement that conformant implementations should conform to the test assertions. There is also no statement about whether the conformant implementations should pass the TC defined test cases covering the concerned specifications.

b> Verify the new schedule  

Spec Work:

End Feb – Assembly and Policy TC to start 1st Public Review (60 day)

Mid March – Other TCs to start 1st Public Review (60 day)

End June – Finish all the work 

End  July – Submit specs to OASIS for OS vote

Testing:

Assembly Test Assertions complete         30/01/2009

Assembly TestCases complete                 27/02/2009

Public review draft ready                 17/03/2009

1st Public review complete                 29/05/2009

Other TCs trailing behind by 1 month

It is possible that some of the TCs may have to adjust their PR schedule by few weeks. It is desirable to have all the SCA specifications reaching the CS/OS status around the same time such that implementers can be provided with a single, integrated set of SCA specifications. With this expectation, the individual SCA TCs can stagger their PR cycles with a reasonable time apart from each other. For example, if the SCA-BPEL TC gets ready for PR a few weeks earlier than the SCA-J TC, SCA-BPEL TC could go ahead with their PR cycle.

Action: Sanjay to create a schedule document and upload it to the LSC kavi

7. New Issues

   a> Removing the complexity of merging the derived component types with sidefiles

       http://lists.oasis-open.org/archives/opencsa-liaison/200902/msg00006.html

LSC resolved to send out the recommendation made by the BPEL TC to all the SCA TCs.

8. Issue Discussion

LIAISON-5 http://osoa.org/jira/browse/LIAISON-5

        Each spec to define conformance dependencies

        SCA-Assembly: http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00010.html

        SCA-Policy: http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00007.html

        SCA-Bindings: ??

        SCA-J: http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00006.html

        SCA-BPEL: http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00011.html

        SCA-C-C++: http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00008.html

        

Feedback from all the TCs about conformance dependencies has been received. Sanjay to compile the feedback together into the JIRA as resolution of the issue.

Motion by Martin to close this issue. Seconded by Anish. Carried unanimously.

b>      LIAISON-6  http://osoa.org/jira/browse/LIAISON-6

What does it mean to conform to SCA ?

Assembly TC currently has a place holder issue for tracking this topic which is expected to be resolved before the Assembly spec goes PR.

    

9. Next conf-call 

Mar 5th, 2009 – 10 AM Pacific

10. AOB

None