OASIS Electronic Business Service Oriented Architecture Technical Committee (ebSOA TC)

OASIS TC Call for Participation: ebSOA TC

Date:      Fri, 20 Feb 2004 13:12:16 -0500
From:      Karl F. Best <karl.best@oasis-open.org>
To:        members@lists.oasis-open.org, tc-announce@lists.oasis-open.org,
           xml-dev@lists.xml.org, ebsoa@lists.oasis-open.org
Subject:   OASIS TC Call for Participation: ebSOA TC

A new OASIS technical committee is being formed. The OASIS Electronic Business Service Oriented Architecture Technical Committee (ebSOA TC) has been proposed by the following members of OASIS: Duane Nickull and Matt Mackenzie, Adobe Systems; Joseph Chuisano, Booz Allen Hamilton; David Burdett, Commerce One; Dale Moberg, Cyclone Commerce; Steve Ross-Talbot, Enigmatic Corporation; Ron Schuldt, Lockheed Martin; Tim Mathews, LMI; and Paul Spencer and Ravi Panja, Individual Members.

The proposal for a new TC meets the requirements of the OASIS TC Process (see http://oasis-open.org/committees/process.shtml), and is appended to this message. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's charter. The TC Process allows these items to be clarified (revised); such clarifications (revisions), as well as submissions of technology for consideration by the TC and the beginning of technical discussions, may occur no sooner than the TC's first meeting.

As specified by the OASIS TC Process, the requirements for becoming a member of the TC at the first meeting are that you must 1) be an employee of an OASIS member organization or an Individual member of OASIS; 2) notify the TC chair of your intent to participate at least 15 days prior to the first meeting; and 3) attend the first meeting of the TC. For OASIS members, to register for the TC using the OASIS collaborative tools, go to the TC's public web page at http://www.oasis-open.org/committees/ebsoa and click on the button for "Join This TC" at the top of the page. You may add yourself to the roster of the TC either as a Prospective Member (if you intend to become a member of the TC) or an Observer. A notice will automatically be sent to the TC chair, which fulfills requirement #2 above.

OASIS members may also join the TC after the first meeting. Note that membership in OASIS TCs is by individual, and not by organization.

Non-OASIS members may read the TC's mail list archive, view the TC's web page, and send comments to the TC using a web form available on the TC's web page; click the "Send A Comment" button. The archives of the TC's mail list and public comments are visible at http://lists.oasis-open.org/archives/

-Karl

Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206
mobile +1 978.761.1648
karl.best@oasis-open.org
http://www.oasis-open.org

ebSOA Technical Committee Charter

The following items will be part of the normative TC charter:

The Name of the TC

OASIS Electronic Business Service Oriented Architecture Technical Committee.

Purpose

A statement of purpose, including a definition of the problem to be solved:

Continue work on the ebXML Technical Architecture to bring it from v1.04 to a more current architecture that takes into account both subsequent releases of the ebXML specifications and other Web Services and service-oriented architecture works including the work of the W3C Web Services Architecture WG. There are no current efforts on the ebXML Technical Architecture and that specification (currently in v1.04) needs to be updated to reflect changes within several of the other ebXML and Web Services specifications. See the "Identification of similar or applicable work" section below for a partial list.

Scope

The scope of the work of the TC. The TC will:

Assess the subsequent and related works noted herein and the implementation experience of the existing ebXML and Web Services specifications.
Update the descriptive and normative statements of existing ebXML and Web Services specifications in an updated Technical Architecture document(s) to reflect the subsequent approved versions, and the other developments and implementation experiences described here.
Assess the implementability and interoperability of the multiple ebXML and Web Services specifications, provide comments and suggestions to the TCs managing the individual specifications, and identify gaps or future work (if any) needed or desirable for useful complete implementations.
Assess the implementability and interoperability of other relevant approved e-business and web services standards with one or more existing ebXML specifications, provide comments and suggestions (if any) to the TCs and other panels managing the relevant individual specifications, and (if the TC requests) provide non-normative examples or suggestions for useful combinations and extensions of the various specifications.
Adhere to the requirements of the ebXML Requirements Specification (v1.06) and/or later revisions.
Provide an opportunity for each TC that manages an individual ebXML and/or Web Service(s) specifications to comment on and correct any descriptions or characterizations of those specifications before they are incorporated into any work approved by this TC.

The TC will not publish normative public guidance about an existing ebXML specification that contradicts the approved text. Suggestions for change or extension should be welcome and recorded, but expressed in a manner that does not undermine the approved specifications as the primary source of ebXML technical guidance.

In no event shall this Technical Committee finalize or approve any technical specification if it believes that the use, distribution, or implementation of such specification would necessarily require the unauthorized infringement of any third party rights known to the Technical Committee, and such third party has not agreed to provide necessary license rights on perpetual, royalty-free, non-discriminatory terms.

Deliverables

A list of deliverables, with completion dates:

1. An eBusiness Service Oriented Architecture Technical Specification — completion date in eighteen months from formation of this TC, with incremental drafts published on a regular basis in advance of completion.

2. A Service Oriented Architecture (including ebXML and Web Services) Best Practices Document (first version) — a non prescriptive (illustrative) guide to help implement a modern SOA. Completion date is twelve months after the completion of the architecture above.

Audience

The anticipated audience or users of the work:

All OASIS ebXML and Web Service TCs, non-OASIS ebXML and Web Service standards groups and SOA implementers, vendors, eGovernment personnel and users are the primary audience. The work should be of interest to anyone involved with Service Oriented Architectures (SOAs) regardless of the standards body under which the work is sanctioned.

Language

The language in which the TC will conduct business:

English. The TC may elect to form subcommittees that will produce localized documentation of the TC's work in additional languages.

Additional Information

The following is informational only for the purposes of starting the TC, and will not be part of the TC's charter.

Similar Work

Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations.

All ebXML and Web Services groups are the primary target of this architecture. Liaisons will be decided by team consensus based on needs.

It is anticipated that liaisons will be needed for all ebXML and Web Services Technical Committees and may be necessary or useful for the following organizations. Note that this is a non-exhaustive list.

OASIS ebXML BP TC
OASIS ebXML CPP/A TC
OASIS ebXML Messaging TC
OASIS ebXML Registry TC
OASIS UBL TC
OASIS UDDI TC
OASIS WSBPEL TC
OASIS WS-CAF TC
OASIS WSRM TC
UN/CEFACT teams with ebXML-related work
W3C WS Choreography Working Group
W3C WS Description Working Group
W3C XML Protocol Working Group

Contributions

Optionally, a list of contributions of existing technical work that the proposers anticipate will be made to this TC.

The ebXML Technical Architecture v1.04
The ebXML Requirements document v1.06

First Meeting

The date and time of the first meeting, whether it will be held in person or by phone, and who will sponsor this first meeting.

Date: 29 April 2004
Time: 1-5pm CT
Face to Face at the OASIS Symposium, New Orleans
Meeting Sponsor: OASIS

Meeting Schedule

The projected on-going meeting schedule for the year following the formation of the TC, or until the projected date of the final deliverable, whichever comes first, and who will be expected to sponsor these meetings.

Meeting schedule will be monthly conference calls as well as quarterly Face to Face meetings pending approval and adoption by the TC. Sponsor: Adobe Systems Inc. (TBD - pending approval by new TC)

Proposers

The names, electronic mail addresses, and membership affiliations of at least three Eligible Persons who support this proposal and are committed to the charter and projected meeting schedule.

Duane Nickull, dnickull@adobe.com, Adobe Systems
Matt Mackenzie, mattm@adobe.com, Adobe Systems
Joseph Chuisano, chiusano_joseph@bah.com, Booz Allen Hamilton
David Burdett, david.burdett@commerceone.com, Commerce One
Dale Moberg, dmoberg@cyclonecommerce.com, Cyclone Commerce
Steve Ross-Talbot, steve@enigmatec.net, Enigmatic Corporation
Ron Schuldt, ron.l.schuldt@lmco.com, Lockheed Martin
Tim Mathews, tmathews@lmi.org, LMI
Ravi Panja, rpanja@insyncinfo.com, Individual Member
Paul Spencer, paul.spencer@boynings.co.uk, Individual Member

TC Convenor

The name and email address of the TC Convenor.

Duane Nickull, dnickull@adobe.com

Proposed TC Chair(s)

The name(s) and email address(es) of the proposed TC chair or co-chairs.

Duane Nickull (dnickull@adobe.com), Proposed Chair

Prepared by Robin Cover for The XML Cover Pages archive. See other details in the news item "OASIS Members Form Electronic Business Service Oriented Architecture TC."

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	OASIS Electronic Business Service Oriented Architecture Technical Committee (ebSOA TC) OASIS TC Call for Participation: ebSOA TC Date: Fri, 20 Feb 2004 13:12:16 -0500 From: Karl F. Best <karl.best@oasis-open.org> To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org, xml-dev@lists.xml.org, ebsoa@lists.oasis-open.org Subject: OASIS TC Call for Participation: ebSOA TC A new OASIS technical committee is being formed. The OASIS Electronic Business Service Oriented Architecture Technical Committee (ebSOA TC) has been proposed by the following members of OASIS: Duane Nickull and Matt Mackenzie, Adobe Systems; Joseph Chuisano, Booz Allen Hamilton; David Burdett, Commerce One; Dale Moberg, Cyclone Commerce; Steve Ross-Talbot, Enigmatic Corporation; Ron Schuldt, Lockheed Martin; Tim Mathews, LMI; and Paul Spencer and Ravi Panja, Individual Members. The proposal for a new TC meets the requirements of the OASIS TC Process (see http://oasis-open.org/committees/process.shtml), and is appended to this message. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's charter. The TC Process allows these items to be clarified (revised); such clarifications (revisions), as well as submissions of technology for consideration by the TC and the beginning of technical discussions, may occur no sooner than the TC's first meeting. As specified by the OASIS TC Process, the requirements for becoming a member of the TC at the first meeting are that you must 1) be an employee of an OASIS member organization or an Individual member of OASIS; 2) notify the TC chair of your intent to participate at least 15 days prior to the first meeting; and 3) attend the first meeting of the TC. For OASIS members, to register for the TC using the OASIS collaborative tools, go to the TC's public web page at http://www.oasis-open.org/committees/ebsoa and click on the button for "Join This TC" at the top of the page. You may add yourself to the roster of the TC either as a Prospective Member (if you intend to become a member of the TC) or an Observer. A notice will automatically be sent to the TC chair, which fulfills requirement #2 above. OASIS members may also join the TC after the first meeting. Note that membership in OASIS TCs is by individual, and not by organization. Non-OASIS members may read the TC's mail list archive, view the TC's web page, and send comments to the TC using a web form available on the TC's web page; click the "Send A Comment" button. The archives of the TC's mail list and public comments are visible at http://lists.oasis-open.org/archives/ -Karl Karl F. Best Vice President, OASIS office +1 978.667.5115 x206 mobile +1 978.761.1648 karl.best@oasis-open.org http://www.oasis-open.org ebSOA Technical Committee Charter The following items will be part of the normative TC charter: The Name of the TC OASIS Electronic Business Service Oriented Architecture Technical Committee. Purpose A statement of purpose, including a definition of the problem to be solved: Continue work on the ebXML Technical Architecture to bring it from v1.04 to a more current architecture that takes into account both subsequent releases of the ebXML specifications and other Web Services and service-oriented architecture works including the work of the W3C Web Services Architecture WG. There are no current efforts on the ebXML Technical Architecture and that specification (currently in v1.04) needs to be updated to reflect changes within several of the other ebXML and Web Services specifications. See the "Identification of similar or applicable work" section below for a partial list. Scope The scope of the work of the TC. The TC will: Assess the subsequent and related works noted herein and the implementation experience of the existing ebXML and Web Services specifications. Update the descriptive and normative statements of existing ebXML and Web Services specifications in an updated Technical Architecture document(s) to reflect the subsequent approved versions, and the other developments and implementation experiences described here. Assess the implementability and interoperability of the multiple ebXML and Web Services specifications, provide comments and suggestions to the TCs managing the individual specifications, and identify gaps or future work (if any) needed or desirable for useful complete implementations. Assess the implementability and interoperability of other relevant approved e-business and web services standards with one or more existing ebXML specifications, provide comments and suggestions (if any) to the TCs and other panels managing the relevant individual specifications, and (if the TC requests) provide non-normative examples or suggestions for useful combinations and extensions of the various specifications. Adhere to the requirements of the ebXML Requirements Specification (v1.06) and/or later revisions. Provide an opportunity for each TC that manages an individual ebXML and/or Web Service(s) specifications to comment on and correct any descriptions or characterizations of those specifications before they are incorporated into any work approved by this TC. The TC will not publish normative public guidance about an existing ebXML specification that contradicts the approved text. Suggestions for change or extension should be welcome and recorded, but expressed in a manner that does not undermine the approved specifications as the primary source of ebXML technical guidance. In no event shall this Technical Committee finalize or approve any technical specification if it believes that the use, distribution, or implementation of such specification would necessarily require the unauthorized infringement of any third party rights known to the Technical Committee, and such third party has not agreed to provide necessary license rights on perpetual, royalty-free, non-discriminatory terms. Deliverables A list of deliverables, with completion dates: 1. An eBusiness Service Oriented Architecture Technical Specification — completion date in eighteen months from formation of this TC, with incremental drafts published on a regular basis in advance of completion. 2. A Service Oriented Architecture (including ebXML and Web Services) Best Practices Document (first version) — a non prescriptive (illustrative) guide to help implement a modern SOA. Completion date is twelve months after the completion of the architecture above. Audience The anticipated audience or users of the work: All OASIS ebXML and Web Service TCs, non-OASIS ebXML and Web Service standards groups and SOA implementers, vendors, eGovernment personnel and users are the primary audience. The work should be of interest to anyone involved with Service Oriented Architectures (SOAs) regardless of the standards body under which the work is sanctioned. Language The language in which the TC will conduct business: English. The TC may elect to form subcommittees that will produce localized documentation of the TC's work in additional languages. Additional Information The following is informational only for the purposes of starting the TC, and will not be part of the TC's charter. Similar Work Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations. All ebXML and Web Services groups are the primary target of this architecture. Liaisons will be decided by team consensus based on needs. It is anticipated that liaisons will be needed for all ebXML and Web Services Technical Committees and may be necessary or useful for the following organizations. Note that this is a non-exhaustive list. OASIS ebXML BP TC OASIS ebXML CPP/A TC OASIS ebXML Messaging TC OASIS ebXML Registry TC OASIS UBL TC OASIS UDDI TC OASIS WSBPEL TC OASIS WS-CAF TC OASIS WSRM TC UN/CEFACT teams with ebXML-related work W3C WS Choreography Working Group W3C WS Description Working Group W3C XML Protocol Working Group Contributions Optionally, a list of contributions of existing technical work that the proposers anticipate will be made to this TC. The ebXML Technical Architecture v1.04 The ebXML Requirements document v1.06 First Meeting The date and time of the first meeting, whether it will be held in person or by phone, and who will sponsor this first meeting. Date: 29 April 2004 Time: 1-5pm CT Face to Face at the OASIS Symposium, New Orleans Meeting Sponsor: OASIS Meeting Schedule The projected on-going meeting schedule for the year following the formation of the TC, or until the projected date of the final deliverable, whichever comes first, and who will be expected to sponsor these meetings. Meeting schedule will be monthly conference calls as well as quarterly Face to Face meetings pending approval and adoption by the TC. Sponsor: Adobe Systems Inc. (TBD - pending approval by new TC) Proposers The names, electronic mail addresses, and membership affiliations of at least three Eligible Persons who support this proposal and are committed to the charter and projected meeting schedule. Duane Nickull, dnickull@adobe.com, Adobe Systems Matt Mackenzie, mattm@adobe.com, Adobe Systems Joseph Chuisano, chiusano_joseph@bah.com, Booz Allen Hamilton David Burdett, david.burdett@commerceone.com, Commerce One Dale Moberg, dmoberg@cyclonecommerce.com, Cyclone Commerce Steve Ross-Talbot, steve@enigmatec.net, Enigmatic Corporation Ron Schuldt, ron.l.schuldt@lmco.com, Lockheed Martin Tim Mathews, tmathews@lmi.org, LMI Ravi Panja, rpanja@insyncinfo.com, Individual Member Paul Spencer, paul.spencer@boynings.co.uk, Individual Member TC Convenor The name and email address of the TC Convenor. Duane Nickull, dnickull@adobe.com Proposed TC Chair(s) The name(s) and email address(es) of the proposed TC chair or co-chairs. Duane Nickull (dnickull@adobe.com), Proposed Chair Prepared by Robin Cover for The XML Cover Pages archive. See other details in the news item "OASIS Members Form Electronic Business Service Oriented Architecture TC."