opencsa-ms message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Draft Minutes for today's OpenCSA Steering Committee - 2009-05-08
- From: Mike Kaiser <mkaiser@us.ibm.com>
- To: opencsa-ms@lists.oasis-open.org
- Date: Fri, 8 May 2009 17:09:54 -0400
DRAFT AGENDA - OpenCSA Steering Committee (StC) Draft
Agenda - 08 May 2009 9:00 AM PST
Call-In Information:
Participant passcode
370491
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
NEW ACTION ITEMS:
None
0. Agenda bashing and Roll
Attending:
Voting Members (X
= Attended)
X David Burke
X Bob Freund
X Anil Gurnani
X Mike Kaiser
(Secretary/Vice-Chair)
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.
- Public Review
Comment by Microsoft. The gist of that comment...
1. Minutes Approval
- 13 March 2009:
http://www.oasis-open.org/apps/org/workgroup/opencsa-ms/download.php/31656/Open_CSA_SC_20090313_Draft.txt
Motion to approve
made and seconded.
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.
AI20090313-002
- Jeff to talk with mary to make
the request to group SCA PR announcements.
STATUS: COMPLETE - Should now be closed.
Jeff send the following e-mail to Mary on March 13,
2009.
http://www.oasis-open.org/apps/org/workgroup/opencsa-ms/email/archives/200903/msg00005.html
Subsequent communications with Mary were done
to inform her that Assembly and Policy specs should
go
first. Any others that are ready at the same
time should
also go, but Assembly nor Policy should be held up
waiting
for another TC.
Will remove from future agendas.
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 and SDO TC specs?
Where do each
of these stand wrt Test Assertion and Test Case PR's?
DISCUSSION:
Hat's off to the
team on this and a special hat's off to
Mike Edward's
efforts on this.
SCA-Java TC has
now approved approval docs and the package
which includes
the following is being completed for
PR.
SCA Java Common Annotations and APIs Specification
SCA Java Component Implementation Specification
Other specs will
follow later (as was the plan).
SCA-Bindings TC
is still about two weeks away from first
review of first
targeted specs.
SDO is still pretty
far away. We need to get a timeline for
this. While
it should plan to deliver sooner rather than
later, it is not
critical to the other TC's work timelines.
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:
Continue to leave
this on the agenda for future meetings.
Tuscany and Fabric
3 still look to be the best compliancy
implementation
options, but until more of the Test Suite
deliveries are
done, this should remain on hold as far as
the Steering Committee
is concerned.
5. StC Elections
Three of the 7
Steering Committee positions (currently held
by Sanjay, Jeff
and Anil) are targeted for balloting
May 13th - May
27th.
Nominations will
be accepted until Tuesday May 12th.
CURRENT STEERING
COMMITTEE
Steering Committee
Next Election
Member
Affiliation for
Seat
-------------------
----------- -----------
David Burke
TIBCO
May 2010
Bob Freund
Hitachi
May 2010
Anil Gurnani
CSC
May 2009
Mike Kaiser
IBM
May 2010 Vice-Chair/Secretary
Mark Little
Red Hat
May 2010
Jeff Mischkinsky
Oracle
May 2009 Chair
Sanjay Patil
SAP
May 2009
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.
Are there any
further actions that the StC members need to
take?
DISCUSSION:
Per business as
usual, any bio's for accepted nominations
will be placed
in the 2009 Steering Committee Candidates
documents folder.
All nominees (even if self nominated)
need to submit
the acceptance letter per process (i.e.
indicate that
they have the time, submit background
material for bio's
etc..). At this point there are
three nominations
in process, but not all have submitted
all the required
pieces.
6. Any Other Business?
DISCUSSION:
Microsoft has
submitted a Public Review for the SCA-Asscembly
specification.
This comment, though it needs to be responded
to by the Assembly
TC merits discussion at the Steering
Committee since
it seeks to change the rules of what it means
to be SCA compliant.
After much discussion,
this boils down to which of the following
two definitions
of compliancy is appropriate to best serve the
SCA community.
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
There are pro's
and con's to each argument. In the end the Steering
Committee needs
to leave this discussion on the agenda but allow
the discussion
to occur within the Assembly TC. Ultimately it is
the Assembly TC
which must respond formally. There is time to
allow this discussion
to happen in the open environment around
the pro's and
con's of each side of the argument.
7. Future SC Agenda Topics?
DISCUSSION:
None.
8. Next Meeting
-
The next regular teleconference is scheduled for June 12th, 2009
9:00am PST, 12:00pm EST, 5:00pm UK
(OpenCSA Steering
Committee calls are scheduled for the second Friday
of each month.)
DISCUSSION:
It appears that
there June 12th meeting may have conflicts with a
number of Steering
Committee members' schedules. Kaiser will work
via e-mail to
validate with members of the Steering Committee that
the prior week,
June 5th provides a better alternative
9. Adjourn
Adjourned.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]