DRAFT - OpenCSA Steering Committee (StC) Draft Minutes - 05 June 2009 9:00 AM PST Call-In Information: *********************************** **** ******* **** ******* ****NOTE NEW PASSCODE BELOW ******* **** ******* **** ******* *********************************** Participant passcode: 784631 <<-- NEW PASSCODE. <--****************** North America Toll free 1-888-240-4148 Toll/International +1-719-234-0214 London, UK, Local +44 (0) 20 7663 2217 UK toll free 0 800 051 6872 *6 mute/un-mute, *0 operator, *1 help Our thanks to David Burke and TIBCO for hosting the teleconference number. NEW ACTION ITEMS: AI20090605-001 Mike to agenda the following for the July 10th Steering Committee meeting: a) further discussion around the 2 compliance validation prior to CS, and b) discussion regarding the SCA implementation language requirement. AI20090605-002 David to set up new moderator call for future steering committee meetings. 0. Agenda bashing and Roll Attending: Voting Members (X = Attended) X David Burke Bob Freund Anil Gurnani X Mike Kaiser (Secretary/Vice-Chair) X Mark Little X Jeff Mischkinsky X Sanjay Patil Apologies: OASIS Staff: Robin Cover Jane Harnad Scott McGrath Mary McRae Dee Schur Identified Observers: None Notes: Mike Kaiser NO CHANGES TO AGENDA. 1. Minutes Approval - 08 May 2009: http://www.oasis-open.org/apps/org/workgroup/opencsa-ms/download.php/32466/Open_CSA_SC_20090508_Draft.txt Motion to approve made (Mark) and seconded (Mike). APPROVED without objection unanimously. 2. Open Action Item Review and Discussion AI20081212-001 - Coordinate an effort with Assembly TC to produce an SCA primer as the specs approach standardization (in review). STATUS: On Hold until we get closer to standardization. Keep on hold. AI20090313-001 Jeff to send the following recommendation to the TC's. Recommendation: Steering Committee Recommends inclusion of the completed test suite with the main package for the initial CS vote. STATUS: Still open. Jeff will do this. Leave as open. 3. Overall TC Milestones Status as discussed by LSC: Tentative dates for key milestones: On Feb 5, 2009 conf-call [A], the LSC discussed the following as the new anticipated schedule for the OpenCSA TCs: 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 ASSEMBLY ONLY (now about a month behind schedule on testing work resulting in the following [B]) End Feb Test Assertion complete End March Test Case complete Mid April for Assembly TC only End June - 1st Public Review complete Recommendation that all other TC's set a similiar schedule for for about one month later. [A] http://lists.oasis-open.org/archives/opencsa-liaison/200902/msg00003.html [B] http://lists.oasis-open.org/archives/opencsa-liaison/200901/msg00013.html The following represents the current state of each TC relative to Public Reviews * = PR 04/24 - 06/23 SCA-Assembly TC Specifications (V1.1) * SCA Assembly Model Specification SCA-Policy TC Specifications (V1.1) * SCA Policy Framework SCA-Bindings TC Specifications (V1.1) ? SCA Web Services Binding Specification ? SCA JMS Binding Specification ? SCA JCA Binding Specification - SCA HTTP Binding Specification SCA-BPEL TC Specifications (V1.1) * SCA WS-BPEL Client and Implementation Specification SCA-C/C++ TC Specifications (V1.1) * SCA Client and Implementation Model Specification for C * SCA Client and Implementation Model Specification for C++ SCA-J TC Specifications (V1.1) ? SCA Java Common Annotations and APIs Specification ? SCA Java Component Implementation Specification - SCA EJB Session Bean Binding Specification - SCA Spring Component Implementation Specification - SCA JEE Integration Specification SDO TC Specifications (V3.0) - Service Data Objects Specification - Service Data Objects for Java What is the outlook for SCA-Binding, SCA-J CA&A and CI specs? Where do each of these stand wrt Test Assertion and Test Case PR's? DISCUSSION: SCA Binding Status: According to Simon Holdsworth, WS, JMS and JCA bindings are now going through their last issues/revisions prior to a release for PR vote within the TC. It is hoped that the TC will vote on these three binding specs on June 18th. The HTTP binding spec has been at a lower priority and won't go out for a while. SCA Java Status: Java CA&A and Java CI have both been submitted to the TC Admin and are in process for PR. PR announcement is imminent. Testing work hasn't started yet. Spring and EJB are the next things in the priority queue. Spring is being worked but doesn't have a schedule yet. Both are anticipated about a month or so later. Other specs, will be lower priority and won't be released for PR anytime soon. 4. Compliant implementation plans We know that we need something about mid year. There are several companies working this but implementation timing is unknown. Open Source (Apache Tuscany, looks to be one source for at least some of the TC's. Fabric3 may be another). Each TC will have to make it's own decision on what compliant implementations they are going to use based on what's available in the timeframe of standardization and what their test plan looks like. The SC must eventually resolve the question of "how it will make approval decisions" and communicate this to the TC's. It is expected that the Testing Plans for each TC will incorporate implementation/testing aspects which encompass the broader "SCA" picture. We must address the following core questions: Are we all in agreement that the exit criteria in each charter applies to Member Submission for vote and not for Committee Specification approval? At this stage, what (if any) compliant applications are the likely candidates which the SC will likely generally accept? If there are no updates, then continue to hold on agenda for discussion at the next meeting. DISCUSSION: There is some debate as to whether the exit criteria requiring spec validation by two implementations is necessary prior to Committee Specification or not. (A) One camp argues that CS is defined by OASIS process as a final deliverable and therefore is subject to the exit criteria. The CS is a standard of sorts, it is just not one which has been approved by the entire OASIS Membership. Many (maybe 70%) of the OASIS specs are in this state without intent to gain OASIS Membership standardization status. Because of this CS status should not be granted until there is validation of at least 2 implementations. we shouldn't have final deliverables which haven't been fully debugged using the 2 implementation compliance rule. (B) The other camp argues that public perception is that CS's are not OASIS standards. Perception is that they do represent a level of specification which is stable enough that Vendors and customers can implement with some assurances that the OASIS Member Standard is likely to have little if any change. This level of specification is used by some as the tipping point to make resource/dollar/timing decisions around formal implementations. Therefore, CS status should be granted to encourage implementations to formally validate against. Due to time constraints, further discussion was deferred for continuation at the next meeting (July 10th). ACTION: AI20090605-001 Mike to agenda continuation of this discussion at next meeting. 5. StC Elections Balloting closed for three of the 7 Steering Committee positions on May 27th. Congratulations to Anil Gurnani, Jeff Mischkinsky and Sanjay Patil for their successful re-election to the Steering Committee. CURRENT STEERING COMMITTEE (as of June 21st, 2009) Steering Committee Next Election Member Affiliation for Seat ------------------- ----------- ----------- David Burke TIBCO May 2010 Bob Freund Hitachi May 2010 Anil Gurnani CSC May 2011 Mike Kaiser IBM May 2010 Vice-Chair/Secretary Mark Little Red Hat May 2010 Jeff Mischkinsky Oracle May 2011 Chair Sanjay Patil SAP May 2011 The Chair, Vice-Chair and Secretary elected positions are in force August 1st 2008, through July 31, 2009. Seats elected in May are in effect beginning June 1st. DISCUSSION: Congratulations!!! 6. New Teleconference Passcode A new passcode was required for this meeting due to potential fraudulent use of the teleconference number. We need to discuss whether there are some other actions the Steering Committee can take to minimize the exposure for this in the future. DISCUSSION: The company found it published somewhere unexpected on the web. So they investigated and thought there was fraudulent use. ACTION: AI 20090605-002 David will set up a moderator code which will be protected prior to the next meeting July 10th. 7. Response to Microsoft SCA-Assembly Public Review comment. SCA-Assembly responded to Microsoft's review comments. Do we have consensus on which of the following paths should be pursued across the board (i.e. A or B)? A) SCA Compliant extensions must be compliant with all of the following: a) SCA Assembly, b) SCA Policy, c) SCA Binding, and d) at least one of the SCA Implementation Types (currently Java, BPEL, C or C++ ) B) SCA Compliant extensions must be compliant with all of the following: a) SCA Assembly, b) SCA Policy and c) SCA Binding DISCUSSION: ACTION: AI20090605-001 (continued) Mike to schedule discussion for this at the next Steering Committee meeting. 8. Any Other Business? None. 9. Future SC Agenda Topics? None 10. Next Meeting - The next regular teleconference is scheduled for July 10th, 2009 9:00am PST, 12:00pm EST, 5:00pm UK (OpenCSA Steering Committee calls are scheduled for the second Friday of each month.) 11. Adjourn