opencsa-ms message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Proposed - OpenCSA Steering Committee (StC) Proposed Agenda - 05 June 2009
- From: Mike Kaiser <mkaiser@us.ibm.com>
- To: "OpenCSA Member Section" <opencsa-ms@lists.oasis-open.org>
- Date: Thu, 4 Jun 2009 21:00:59 -0400
PROPOSED AGENDA - OpenCSA Steering Committee (StC)
Proposed Agenda - 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.
0. Agenda bashing and Roll
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
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. Do we want to leave open or close?
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 similar 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?
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.
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.
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.
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
8. Any Other Business?
9. Future SC Agenda Topics?
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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]