Copyright © 2003-2004 by The Web Services-Interoperability Organization (WS-I) and Certain of its Members. All Rights Reserved.
This document defines the process for submitting scenarios to the WS-I Requirements Gathering Working Group for its consideration as it attempts to identify requirements for Web services interoperability.
This document is a WS-I Document approved for publication by the WS-I Board.
The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or WS-I. The material contained herein is provided on an "AS IS" basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and WS-I hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL.
IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR WS-I BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
The Web Services-Interoperability Organization (WS-I) would like to receive input, suggestions and other feedback ("Feedback") on this work from a wide variety of industry participants to improve its quality over time.
By sending email, or otherwise communicating with WS-I, you (on behalf of yourself if you are an individual, and your company if you are providing Feedback on behalf of the company) will be deemed to have granted to WS-I, the members of WS-I, and other parties that have access to your Feedback, a non-exclusive, non-transferable, worldwide, perpetual, irrevocable, royalty-free license to use, disclose, copy, license, modify, sublicense or otherwise distribute and exploit in any manner whatsoever the Feedback you provide regarding the work. You acknowledge that you have no expectation of confidentiality with respect to any Feedback you provide. You represent and warrant that you have rights to provide this Feedback, and if you are providing Feedback on behalf of a company, you represent and warrant that you have the rights to provide Feedback on behalf of your company. You also acknowledge that WS-I is not required to review, discuss, use, consider or in any way incorporate your Feedback into future versions of its work. If WS-I does incorporate some or all of your Feedback in a future version of the work, it may, but is not obligated to include your name (or, if you are identified as acting on behalf of your company, the name of your company) on a list of contributors to the work. If the foregoing is not acceptable to you and any company on whose behalf you are acting, please do not provide any Feedback.
Feedback on this document should be directed to submitting_scenarios_comments@ws-i.org.
1. Introduction
Appendix I: Glossary
Appendix II: Referenced Material
Appendix III: Acknowledgements
The WS-I Requirements Gathering Working Group is chartered to identify requirements for Web services interoperability, which will be used to help define potential future profiles and other kinds of work within WS-I. In order to ensure that potential future profiles address the interoperability needs of the users of its profiles, WS-I is collecting scenarios and use cases which describe interoperability requirements. A scenario can be either a "business scenario", which is defined as a description of a current business problem or new business opportunity from a business person's / business process point of view, or a "technical scenario", which is defined as a description of an application or a system from a development or system administration point of view. Similarly, a "use case" is defined as an application specific course of events describing the interactions between actors, roles, and the system under consideration.
The WS-I Requirements Gathering Working Group will discuss each and every scenario or use case that is submitted, and will either accept it or reject it. A scenario would be rejected if it is not about interoperability (e.g. single vendor or unique to a specific IT environment), if the interoperability does not involve Web services (e.g. browser / web server HTML incompatibility), if it is a duplicate of another requirement, which includes the case where the requirement has already been addressed in another profile, or if more information is needed in order to make a determination. Scenarios that are accepted as relevant to the topic of Web services interoperability go into the Catalog of Scenarios. The WS-I Requirements Gathering Working Group looks at the scenarios in the catalog in an attempt to identify the most important requirements. This analysis is documented in a Requirements Document and submitted to the WS-I Board for its consideration.
If you would like to submit an interoperability requirement to the WS-I Requirements Gathering Working Group, the process is as follows:
Note: If you are not sure if your scenario is valid, you can submit just a cover sheet. If the WS-I Requirements Gathering Working Group accepts your cover sheet, you will be asked to submit a business scenario and/or a use case which further describes your requirement.
The WS-I Requirements Gathering Working Group very much wants to hear your interoperability requirements. There is no guarantee that your requirements will be accepted and incorporated into a future WS-I profile, but they will at least be taken into consideration.
A "business scenario" is a description of a current business problem or new business opportunity from a business person's / business process point of view.
A "technical scenario" is a description of an application or a system from a development or system administration point of view.
A "use case" is an application specific course of events describing the interactions between actors, roles, and the system under consideration.
None.
This catalog of scenarios is the work of the WS-I Requirements Gathering Working Group, whose members have included:
Randy Armstrong (OPC Foundation), Heidi Buelow (Quovadx), Doug Bunting (Sun Microsystems), Jon Calladine (BT), Martin Chapman (Oracle Corporation), Ugo Corda (SeeBeyond Tech), Paul Downey (BT), Rob Drew (Charles Schwab), Jacques Durand (Fujitsu Limited), Bob Freund (Hitachi, Ltd.), Shishir Garg (France Telecom), Norma Hale (Webify Solutions Inc), Jacek Kopecky (Systinet), Chris Kurt (Microsoft), Greg Lomow (IONA Technologies), John Miller (IBM), Jeff Mischkinsky (Oracle Corporation), Mark Nottingham (BEA Systems), Rimas Rekasius (IBM), Darren Self (Micro Focus), Dorival Simoes (Accenture), Cafer Tosun (SAP AG), William Vambenepe (Hewlett-Packard), Dave Wilkinson (Vignette).