The name of the Member Section shall be the OASIS Open Composite Services Architecture Member Section (Open CSA MS).
The Open CSA MS facilitates the execution of the Open CSA program of work, as described in the Member Section’s Work Plan, over an extended period of time requiring the coordination of multiple Technical Committees (TCs) and various adoption and marketing activities it may choose to undertake.
The Open CSA MS will support the process of gathering requirements, developing specifications, coordinating the work of its affiliated Technical Committees, and provide the governance structure to accept and manage funds to serve its work. As standards in this area mature, the Member Section may also support adoption and implementation efforts including development of test cases, testing procedures, and interoperability testing and demonstrations.
The initial focus of the work will be the Service Component Architecture and Service Data Objects family of specifications that will be contributed to the Member Section’s TCs. Technical work products created and approved by Open CSA MS TCs shall be referred to as "Open CSA MS Technical Committee Specifications" or "Open CSA MS" , as appropriate.
The SC shall consist of seven at-large positions determined by elections among all the Qualified Electors serving two-year terms; staggered so that four (4) expire one year and the other three (3) expire the next.
The maximum number of SC members shall be seven (7). The number of SC members may be reduced by the unanimous approval of every SC Member or as allowed by the Member Section Policy.
The initial Steering Committee shall consist of one member from each of BEA, IBM, Oracle, and SAP each having an initial term of two years. The remaining three (vacant) one-year terms shall be filled by an election to be held no later than two months following the establishment of the Member Section.
There shall not be any dues allocation by OASIS Members associated with this Member Section. The Steering Committee may choose to take advantage of other funding mechanisms (such as sponsorships, grants, etc.) as provided by the Member Section Policy to support marketing, testing, and interoperability activities.
All Technical Committees affiliated with this Member Section will operate under the OASIS Royalty Free on Limited Terms IPR Policy.
All Technical Committees affiliated with this Member Section that have normative specifications as their deliverables shall have Charters that require them to:
The Open CSA SC will maintain a Work Plan document that provides details of current and contemplated work. The Work Plan document may be modified by a MS Special Majority vote.
The Open CSA SC will be responsible for ensuring that the work of its affiliated Technical Committees is coordinated and that the work output maintains coherence by careful evaluation of Charter proposal, TC affiliation, and requests to advance to OASIS specification.
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC will be put before the OASIS general membership for consideration as "OASIS Standards".
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC may be submitted to another organization in accordance with the OASIS Liaison Policy.
This version approved by the OASIS Board of Directors 15 November 2012
___________________________________________________________________________
1) The Name of the Member Section
The name of the Member Section shall be the OASIS Open Composite Services Architecture Member Section (Open CSA MS).
2) The Member Section Statement of Work
The Open CSA MS facilitates the execution of the Open CSA program of work, as described in the Member Section’s Work Plan, over an extended period of time requiring the coordination of multiple Technical Committees (TCs) and various adoption and marketing activities it may choose to undertake.
The Open CSA MS will support the process of gathering requirements, developing specifications, coordinating the work of its affiliated Technical Committees, and provide the governance structure to accept and manage funds to serve its work. As standards in this area mature, the Member Section may also support adoption and implementation efforts including development of test cases, testing procedures, and interoperability testing and demonstrations.
The initial focus of the work will be the Service Component Architecture and Service Data Objects family of specifications that will be contributed to the Member Section’s TCs.
Technical work products created and approved by Open CSA MS TCs shall be referred to as “Open CSA MS Technical Committee Specifications” or “Open CSA MS documents", as appropriate.
3) The Rules for Electing Steering Committee Members
The SC shall consist of seven (7) members with two-year terms, staggered so that four (4) expire one year and the other three (3) expire the next.
A Member Section Supporting Entity may not be represented by more than one Steering Committee Member. A maximum of one Member Section Member per unique Member Section Supporting Entity may run for election. In the event of a job change, merger, or acquisition which results in two Steering Committee Members representing one Member Section Supporting Entity, one of the Steering Committee Members shall immediately resign.
4) Initial Makeup of Member Section Steering Committee
The initial Steering Committee shall consist of one member from each of BEA, IBM, Oracle, and SAP each having an initial term of two years. The remaining three (vacant) one-year terms shall be filled by an election to be held no later than two months following the establishment of the Member Section.
5) Process for Changing the Number of Steering Committee Members
The maximum number of SC members shall be seven (7). The number of SC members may be reduced only by the unanimous approval of every SC Member.
6) Funding Model for the Member Section
There shall not be any dues allocation by OASIS Members associated with this Member Section.
The Steering Committee may choose to take advantage of other funding mechanisms (such as sponsorships, grants, etc.) as provided by the Member Section Policy to support marketing, testing, and interoperability activities.
7) Provisions that Apply to Affiliated Technical Committees
All Technical Committees affiliated with this Member Section will operate under the OASIS Royalty Free on Limited Terms IPR Policy.
All Technical Committees affiliated with this Member Section that have normative specifications as their deliverables shall have Charters that require them to:
8) Other Provisions
The Open CSA SC will maintain a Work Plan document that provides details of current and contemplated work. The Work Plan document may be modified by a MS Special Majority vote.
The Open CSA SC will be responsible for ensuring that the work of its affiliated Technical Committees is coordinated and that the work output maintains coherence by careful evaluation of Charter proposal, TC affiliation, and requests to advance to OASIS specification.
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC will be put before the OASIS general membership for consideration as “OASIS Standards”.
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC may be submitted to another organization in accordance with the OASIS Liaison Policy.
___________________________________________________________________
1) The Name of the Member Section
The name of the Member Section shall be the OASIS Open Composite Services Architecture Member Section (Open CSA MS).
2) The Member Section Statement of Work
The Open CSA MS facilitates the execution of the Open CSA program of work, as described in the Member Section’s Work Plan, over an extended period of time requiring the coordination of multiple Technical Committees (TCs) and various adoption and marketing activities it may choose to undertake.
The Open CSA MS will support the process of gathering requirements, developing specifications, coordinating the work of its affiliated Technical Committees, and provide the governance structure to accept and manage funds to serve its work. As standards in this area mature, the Member Section may also support adoption and implementation efforts including development of test cases, testing procedures, and interoperability testing and demonstrations.
The initial focus of the work will be the Service Component Architecture and Service Data Objects family of specifications that will be contributed to the Member Section’s TCs. Technical work products created and approved by Open CSA MS TCs shall be referred to as “Open CSA MS Technical Committee Specifications” or “Open CSA MS" , as appropriate.
3) The Rules for Electing Steering Committee Members
The SC shall consist of seven (7) members with two-year terms, staggered so that four (4) expire one year and the other three (3) expire the next.
A Member Section Supporting Entity may not be represented by more than one Steering Committee Member. A maximum of one Member Section Member per unique Member Section Supporting Entity may run for election. In the event of a job change, merger, or acquisition which results in two Steering Committee Members representing one Member Section Supporting Entity, one of the Steering Committee Members shall immediately resign.
Each Member Section Supporting Entity shall be entitled to have one Member Section Qualified Elector. The Member Section Qualified Elector shall be the Supporting Entity's Primary or other Member Section Member of said Supporting Entity as designated by the Primary Representative.
4) Initial Makeup of Member Section Steering Committee
The initial Steering Committee shall consist of one member from each of BEA, IBM, Oracle, and SAP each having an initial term of two years. The remaining three (vacant) one-year terms shall be filled by an election to be held no later than two months following the establishment of the Member Section.
5) Process for Changing the Number of Steering Committee Members
The maximum number of SC members shall be seven (7). The number of SC members may be reduced only by the unanimous approval of every SC Member.
6) Funding Model for the Member Section
There shall not be any dues allocation by OASIS Members associated with this Member Section.
The Steering Committee may choose to take advantage of other funding mechanisms (such as sponsorships, grants, etc.) as provided by the Member Section Policy to support marketing, testing, and interoperability activities.
7) Provisions that Apply to Affiliated Technical Committees
All Technical Committees affiliated with this Member Section will operate under the OASIS Royalty Free on Limited Terms IPR Policy.
All Technical Committees affiliated with this Member Section that have normative specifications as their deliverables shall have Charters that require them to:
8) Other Provisions
The Open CSA SC will maintain a Work Plan document that provides details of current and contemplated work. The Work Plan document may be modified by a MS Special Majority vote.
The Open CSA SC will be responsible for ensuring that the work of its affiliated Technical Committees is coordinated and that the work output maintains coherence by careful evaluation of Charter proposal, TC affiliation, and requests to advance to OASIS specification.
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC will be put before the OASIS general membership for consideration as “OASIS Standards”.
Only Open CSA MS Technical Committee Specifications approved by a Special Majority vote of the Open CSA MS SC may be submitted to another organization in accordance with the OASIS Liaison Policy.