OASIS Web Services Resource Framework (WSRF) TC
OASIS TC Call for Participation: Web Services Resource Framework
Date: Tue, 09 Mar 2004 15:13:36 -0500 From: Karl F. Best <email@example.com> To: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: OASIS TC Call for Participation: Web Services Resource Framework
A new OASIS technical committee is being formed. The OASIS Web Services Resource Framework (WSRF) TC has been proposed by the following members of OASIS: Fred Carter, AmberPoint; Glen Daniels, Sonic Software; Andreas Dharmawan, Individual; Ian Foster, ANL; Hiro Kishimoto, Fujitsu; Hitoshi Komori, Fujitsu; Lily Liu, webMethods; Bryan Murray, Hewlett-Packard Company; Richard Nikula, BMC Software; Homayoun Pourheidari, Hewlett-Packard Company; Alain Regnier, Ricoh; Ian Robinson, IBM; Igor Sedhuck, Computer Associates; Hitoshi Sekine, Ricoh; David Snelling, Fujitsu; Latha Srinivasan, Hewlett-Packard Company; Jem Treadwell, Hewlett-Packard Company; Steve Tuecke, ANL; William Vambenepe, Hewlett-Packard Company; Alan Weissberger, NEC; and Dave Orchard, BEA.
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/wsrf 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/
Further information about the topic of this TC may be found on the Cover Pages under "Stateful Web Services" at:
Karl F. Best Vice President, OASIS office +1 978.667.5115 x206 mobile +1 978.761.1648 firstname.lastname@example.org http://www.oasis-open.org
Name of the TC
OASIS Web Services Resource Framework (WSRF) Technical Committee
Statement of Purpose
The purpose of the Web Services Resource Framework (WSRF) TC is to define a generic and open framework for modeling and accessing stateful resources using Web services. This includes mechanisms to describe views on the state, to support management of the state through properties associated with the Web service, and to describe how these mechanisms are extensible to groups of Web services.
Web services implementations are often stateless in that they maintain no dynamic state whose lifetime exceeds the processing of an individual message. The statelessness of Web service implementations is a valuable asset to their availability and ability to accommodate dynamic workloads.
Web service interfaces, on the other hand, often imply the need for some form of stateful interaction with the clients of the service. This may be manifest in a conversational style of use of a particular Web service interface in which some aspect of the result of one operation influences the execution of the next operation. The state in interactions with such interfaces is typically contained in or referred to from the messages that are exchanged with the target service. Inferences concerning the nature of the state may sometimes be made, but only in an application-specific fashion and not in a generic manner that can be exploited easily by tooling.
The goal of this TC is to define a set of royalty-free, related, interoperable and modular specifications that will allow the relationship between a Web service and state to be modelled in an explicit and standardized fashion. This will simplify the definition of new service interfaces and enable more powerful discovery, management and development tools. These specifications will be composable with other available Web services specifications enabling applications to access state with the qualities of service - for example security, transactions and reliability - provided for in those specifications.
Scope of Work
The scope of this work is to define a framework within which Web services can access state in a consistent and interoperable manner, and an access pattern through which service requesters can interact indirectly with stateful resources through a Web service that encapsulates the state. An architectural separation will be maintained between a stateful resource and the Web service that encapsulates it to promote the desirable loose coupling between service requestor and the stateless service provider and to provide a highly available and scalable means to interact with state.
This TC will define the means by which:
- Web services can be associated with one or more stateful resources (named, typed, state components).
- Service requestors access stateful resources indirectly through Web services that encapsulate the state and manage all aspects of Web service based access to the state.
- Stateful resources can be destroyed, through immediate or time based destruction.
- The type definition of a stateful resource can be associated with the interface description of a Web service to enable well-formed queries against the resource via its Web service interface.
- The state of the stateful resource can be queried and modified via Web service message exchanges.
- Endpoint references to Web services that encapsulate stateful resources can be renewed when they become invalid, for example due to a transient failure in the network.
- Stateful resources can be aggregated for domain-specific purposes.
WSDL is an essential element of Web services architecture. The specifications produced by this TC will provide WSDL definitions for all normative message exchanges.
The benefits and results of this work will be a standard way for web services to access state leading to greater simplification in the definition of new Web service interfaces, better service interoperability and greater opportunity for tools vendors to provide means to manage Web service applications and resources.
The WSRF TC takes, as its starting point, the set of specifications and the papers "Modeling Stateful Resources with Web Service" (http://www.ibm.com/developerworks/library/ws-resource/ws-modelingresources.pdf and http://devresource.hp.com/drc/specifications/wsrf/ModelingState-1-1.pdf) and "The WS-Resource Framework" (http://www.ibm.com/developerworks/library/ws-resource/ws-wsrf.pdf, http://www-106.ibm.com/developerworks/library/ws-resource/ws-wsrf.pdf, and http://devresource.hp.com/drc/specifications/wsrf/WSRF_overview-1-0.pdf) recently published by IBM, the Globus Alliance, HP, Fujitsu and CA. The papers describe how state associated with a Web service can be modeled in terms of a WS-Resource and give an overview of the specifications that comprise the framework.
The specifications are:
WS-ResourceProperties (http://www.ibm.com/developerworks/library/ws-resource/ws-resourceproperties.pdf and http://devresource.hp.com/drc/specifications/wsrf/WS-ResourceProperties-1-1.pdf) defines how the type definition of a WS-Resource can be associated with the interface description of a Web service, and message exchanges for retrieving, changing, and deleting WS-Resource properties.
WS-ResourceLifetime (http://www.ibm.com/developerworks/library/ws-resource/ws-resourcelifetime.pdf and http://devresource.hp.com/drc/specifications/wsrf/WS-ResourceLifetime-1-1.pdf) defines mechanisms for WS-Resource destruction, including message exchanges that allow a requestor to destroy a resource, either immediately or by using a time-based scheduled resource termination mechanism.
Other contributions in addition to those listed above will be accepted for consideration without any prejudice or restrictions, and evaluated on their technical merit, as long as the contributions are within the scope of this charter.
Out of Scope
The following topics are outside the scope of this TC:
- Quality of service related policy enforcement on resource property access. The TC will not address security or transactions implications in the specifications it delivers.
- The consideration of protocol-specific bindings.
- Query and update of WS-Resource properties is within the scope of the TC, but general purpose XML document query and update, outside the context of managing stateful resources with Web services, is out of scope.
- A normative factory pattern for the creation of WS-Resources.
List of Deliverables
- A revised WS-ResourceProperties specification. Committee Draft due within one year of the first meeting.
- A revised WS-ResourceLifetime specification. Committee Draft due within one year of the first meeting.
- A WS-RenewableReferences specification, which defines a conventional decoration of a Web service endpoint reference with information needed to retrieve an updated version of an endpoint reference when it becomes invalid. Committee Draft due within one year of the first meeting.
- A WS-ServiceGroup specification, which defines an interface to heterogeneous by-reference collections of Web services. Committee Draft due within one year of the first meeting.
- A WS-BaseFaults specification, which defines a base fault XML type for use when returning faults in a Web services message exchange. Committee Draft due within one year of the first meeting.
These specifications will reflect refinements and changes made to, and by, contributions to the TC that are identified by members for additional functionality and semantic clarity within the scope of the TC charter. The titles and granularity of the specifications may change.
The anticipated audience for this work includes:
- other specification writers that need stateful interaction patterns for Web services
- vendors offering web service products
- software architects and programmers who design and write distributed applications requiring the management of state
The following is informational only for the purposes of starting the TC, and will not be part of the TC's charter:
Identification of Existing Activities
A number of efforts that use or require state-access patterns in Web services are underway throughout the industry. The following work may be relevant to this Web Services Resource Framework TC:
- OASIS Web Services Business Process Execution Language Technical Committee (WSBPEL)
- OASIS Web Services Composite Application Framework (WS-CAF) Technical Committee
- OASIS Web Services Distributed Management Technical Committee (WSDM TC)
- GGF Open Grid Services Infrastructure (OGSI)
- W3C WSDL Version 2.0
Date and Time of the First Meeting
The first meeting of the TC will be face-to-face on 28 April 2004 from 9am to 5pm, in New Orleans, in conjunction with the OASIS Symposium on Reliable Infrastructures.
Following the first meeting, the TC is expected to meet bi-weekly via teleconference and to have quarterly face to face meetings, unless a different schedule is agreed upon.
The sponsors for teleconference and further face to face meetings will be Fujitsu and IBM.
The following eligible people are in support of this proposal:
- Fred Carter (email@example.com), AmberPoint
- Glen Daniels (firstname.lastname@example.org), Sonic Software
- Andreas Dharmawan (email@example.com), Individual
- Ian Foster (firstname.lastname@example.org), ANL
- Hiro Kishimoto (email@example.com), Fujitsu
- Hitoshi Komori (firstname.lastname@example.org), Fujitsu
- Lily Liu (email@example.com), webMethods Inc
- Bryan Murray (firstname.lastname@example.org), Hewlett-Packard Company
- Richard Nikula (Richard_Nikula@bmc.com), BMC Software
- Homayoun Pourheidari (email@example.com), Hewlett-Packard Company
- Alain Regnier (firstname.lastname@example.org), Ricoh
- Ian Robinson (email@example.com), IBM
- Igor Sedhuck (Igor.Sedukhin@ca.com), Computer Associates
- Hitoshi Sekine (firstname.lastname@example.org), Ricoh
- David Snelling (email@example.com), Fujitsu
- Latha Srinivasan (firstname.lastname@example.org), Hewlett-Packard Company
- Jem Treadwell (email@example.com), Hewlett-Packard Company
- Steve Tuecke (firstname.lastname@example.org), ANL
- William Vambenepe (email@example.com), Hewlett-Packard Company
- Alan Weissberger, firstname.lastname@example.org, NEC
- Dave Orchard, email@example.com, BEA
The convenor for this TC shall be David Snelling
Prepared by Robin Cover for The XML Cover Pages archive. See additional information in the news story: "OASIS Forms TCs for Web Services Resource Framework and Web Services Notification." See context at "Web Services Resource Framework."