Next in thread →
Next in month →
RE: [sca-policy] Inter-SCA TC Liaison Committee Charter - FINAL
On Oct 25th, the SCA
BPELTC elected the
chairs, Anish Karmarkar
and Sanjay Patil, to be their
representatives to the Inter-SCA TC Liaison
Committee.
Thanks,
Sanjay
Patil
SCA BPEL TC
Co-Chair
From: Graham Barber
[mailto:]
Sent: Friday, Oct 19, 2007 10:24
AM
To: ;
; ;
; ;
Cc:
Subject: [sca-policy] Inter-SCA TC
Liaison Committee Charter - FINAL
Dear SCA Technical
Committees
The OpenCSA Steering
Committee (SC) has approved the charter of an Inter-SCA TC Liaison Committee
(LC) as the official forum for discussion of common issues that cross SCA TC
boundaries. The full text of the charter is below. On behalf of the Steering
Committee, can I request that each SCA TC nominates at least one
representative to serve on the LC by next Friday, October 26th. The SC will
also appoint a representative by that date and he will convene the inaugural
meeting as soon as practical. Please send your nominated name(s) to the
<opencsa-ms> mailing list.
Graham J Barber,
OASIS OpenCSA Steering Committee Secretary
& Vice-Chair
Program Director, SOA
Partnerships,
Graham Barber@IBMGB
Phone:
Internal:
245702, External: +44 (0)1962 815702
Secretary (Yulia):
247672,
+44 (0)1962 817672
Cellphone (Worldwide):
+44 (0)7880 734005
----- Forwarded by Graham Barber/UK/IBM
on 19/10/2007 18:11 -----
Jeff Mischkinsky
<>
19/10/2007 17:56
To
cc
Subject
[opencsa-ms] Inter-SCA TC Liaison
Committee Charter - FINAL
OpenCSA Inter-SCA TC Liaison Committee (LC) 2007-19-2007
The
OpenCSA Inter-SCA TC Liaison Committee is chartered to provide an
official forum for the discussion by the TCs of common issues that
cross SCA TC boundaries. Its membership shall consist of
representatives from each SCA TC (at least one from each TC),
OpenCSA
Steering Committee members, and possibly other invited TC
members.
The OpenCSA SC shall appoint the members for one-year
renewable
terms. Each SCA TC shall recommend to the SC at least one
member to
represent itself on the LC.
The actual composition
and number is flexible in order to accommodate
changing needs and
requirements. However each SCA TC should have at
least one TC member
to represent its interests and to assure reliable
communications. It
is also contemplated that the SC should also have
at least one of
its members serving to ensure a reliable
communication channel
between the SC and the Committee.
All of the Committee's work shall be
visible to the public (i.e. all
documents, email archives, agenda,
discussions, shall be publicly
viewable). The Committee, as its
first order of business shall elect
a Chair. In the absence of such
an elected Chair the SC member shall
serve as a pro tem chair until
such time as the Committee can elect
one. LC meetings,
(teleconference and/or face to face) shall be
posted in advance. The
meetings shall be open to other MS and TC
members as observers.
Observers may participate in meetings at the
discretion of the
chair. Any eligible OASIS member may subscribe to
the LC mail list
and post to it. The LC may use whatever tools seem
appropriate to
organizing its work, provided they meet the above
criteria of public
visibility and are approved by OASIS.
The purpose of the LC is to
provide a forum for the discussion of
common issues that cut across
the SCA TCs. The LC is not a decision
making body in the sense that
is only empowered to make
recommendations to the appropriate TCs or
SC. All of its
recommendations are non-binding and advisory. The LC
must not
disenfranchise the role and responsibilities of the TCs in
technical
discussions.
The LC will not discuss issues which
are the sole purview of any
single TC. The LC will only work on
issues passed to it by requests
made to it by the SC or other TCs
with the view towards making timely
recommendations. The LC may
re-discuss an issue should a
recommendation be rejected by one or
more TCs.
The kinds of activities within its scope are:
the discussion of common process issues,
the tracking
(not resolution of) of cross TC technical issues to
make sure the
designated TC liaisons are aware of them and that the
relevant TCs
take appropriate action,
the making recommendations to the SC
of other actions it might
take to improve coordination of the work
of the OpenCSA TCs.
Contemplated areas where liaison will
almost certainly be
required are exemplified by start-up issues
(naming, versioning,
logistics), test suite issues that cross TCs,
logistics (e.g.
scheduling face-to-face meetings), and close-down
issues (scheduling,
exit criteria,
etc.)
--
Unless stated otherwise above:
IBM
United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
Next in thread →
Next in month →