| I'll try to be there on time but a meeting that was due to start 15 minutes ago hasn't so I may be later. Apologies.
Mark.
On 10 Nov 2009, at 19:21, David Burke wrote: Hi Mike and all TIBCO is changing providers for conference call service. We can discuss in our next meeting, and plan on using a new number in December. (We can use the existing number and passcode for the November call) Regards, David
From: Mike Kaiser [mailto:mkaiser@us.ibm.com]
Sent: Friday, October 09, 2009 6:34 AM
To: OpenCSA Member Section
Subject: [opencsa-ms] Proposed - OpenCSA Steering Committee (StC) Proposed Agenda - 09 October 2009
PROPOSED AGENDA - OpenCSA Steering Committee (StC) Proposed Agenda - 9 October 2009 9:00 AM PST Call-In Information: (PLEASE NOTE THE NEW PASSCODE BELOW) Participant passcode: 677139 <--- 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. 0. Agenda bashing and Roll 1. Minutes Approval - 11 September 2009: http://www.oasis-open.org/apps/org/workgroup/opencsa-ms/download.php/34176/Open_CSA_SC_20090911_Draft.txt 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. Agenda for next item. AI20090814-001 - Mike to get the status of SDO for the next Steering Committee call. STATUS: Not done. AI20090911-001- - Sanjay to provide an initial skeleton draft for a statement describing what a non-SCA OASIS solution would need to achieve. - Bob to insert IPR terms and review - Mike to assist in proposal review and post for next meeting's discussion/review. STATUS: Not done. 3. Overall TC Milestones Status as discussed by LSC: The following represents the current state of each TC relative to Public Reviews * = PR 04/24 - 06/23 & = PR 06/08 - 08/07 ? = PR 08/08 - 10/07 - = Schedule not available at this time. (lower priority) SCA-Assembly TC Specifications (V1.1) * SCA Assembly Model Specification SCA-Policy TC Specifications (V1.1) * SCA Policy Framework 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 SCA-Bindings TC Specifications (V1.1) ? SCA Web Services Binding Specification ? SCA JMS Binding Specification ? SCA JCA Binding Specification - SCA HTTP Binding Specification SDO TC Specifications (V3.0) - Service Data Objects Specification - Service Data Objects for Java Where are we on the Test Suite progress for each? (i.e. Test Cases, Test Assertions) For each - When is TC final review scheduled? - When is vote for PR scheduled? - When is Submission to TC Admin for PR scheduled? - When is PR targeted? Public Review dates for Test Suites (Assertions/Test Cases) 08/18 - 10/17 SCA-Assembly ??/?? - ??/?? SCA-Policy ??/?? - ??/?? SCA-Bindings ??/?? - ??/?? SCA-BPEL ??/?? - ??/?? SCA-C/C++ ??/?? - ??/?? SCA-J ??/?? - ??/?? SDO Where do we stand on CD status with the specs with "-" in the list above? -Spring Binding CD was expected to have completed by end of August/first week of Sept. Status? 4. Compliant implementation plans Discussion on hold until a TC votes a CS. 5. Response to Microsoft and Siemens SCA-Assembly Public Review comments. Microsoft and Siemens (and other internal SCA members) have raised the question around which of the two following paths should be taken for claiming SCA Compliance (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 What is the Steering Committee position? Additionally, Siemens has challenged the notion that c) should also not be included in the compliancy requirement. What is the Steering Committee position? At the last meeting we discussed the possibility of trying to use the OASIS feedback channel to have parties submit their test suites, conformance claims, interface descriptions, etc... (i.e. test materials) to the OASIS server. StC and LSC would review these submissions and make a call before posting approval and making submitted data available via a public facing OASIS web page. (details TBD). This would solve some of the fundamental characteristics which desired, including: - must have some type of document that describes, and - must have a reasonable test suite, and - must have RF IP aspects equivalent/similar to the OASIS RF IPR, and - must be freely available (downloadable/accessible) to the public 7. Discussion around new Steering Committee Secretary 8. Any Other Business? 9. Future SC Agenda Topics? None 10. Next Meeting - The next regular teleconference is scheduled for FRIDAY November 13th, 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
--- Mark Little
JBoss, by Red Hat Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and Brendan Lane (Ireland).
|