WSDL Version 1.2 Property and Feature Task Force (PFTF) Usage Scenarios

Editors' copy $Date: 2003/02/25 15:33:29 $ @@ @@@@ @@@@

This version:
wsdl12-bindings.html
Editors:
Glen Daniels, Macromedia
Jean-Jacques Moreau, Canon

Copyright © @@@@ W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.

Abstract

This document describes the WSDL PFTF Usage Scenarios and how they may be described using the WSDL 1.2 specification.

Status of this Document

This document is an editors' copy that has no official standing.

Short Table of Contents

1. Introduction
2. Documentation of Usage Scenarios
3. References
A. Acknowledgements (Non-Normative)
B. Part 1 Change Log (Non-Normative)

Table of Contents

1. Introduction
2. Documentation of Usage Scenarios
    2.1 S1 Simple feature
        2.1.1 Scenario Definition
    2.2 S2 Abstract feature expressed two ways
        2.2.1 Scenario Definition
    2.3 S3 Request-response over one-way protocol
        2.3.1 Scenario Definition
    2.4 S4 Non-declarative Features
        2.4.1 Scenario Definition
    2.5 S5 Feature expressed as underlying protocol data
        2.5.1 Scenario Definition
    2.6 S6 Asymetric feature
        2.6.1 Scenario Definition
    2.7 S7 Features sharing properties
        2.7.1 Scenario Definition
    2.8 S8 Negociation feature
        2.8.1 Scenario Definition
    2.9 S9 Absence Feature
        2.9.1 Scenario Definition
3. References
    3.1 Informative References

Appendices

A. Acknowledgements (Non-Normative)
B. Part 1 Change Log (Non-Normative)
    B.1 WSDL Specification Changes

1. Introduction

Introduction to the WSDL PFTF usage scenarios.

2. Documentation of Usage Scenarios

2.1 S1 Simple feature

2.1.1 Scenario Definition

A receiver requires that a particular feature be used, for example a recorded delivery feature.

2.2 S2 Abstract feature expressed two ways

2.2.1 Scenario Definition

A sender requires that a abstract particular security feature be used. The feature is either implemented natively by the selected transport protocol (S2.1) or implemented as one or more SOAP header blocks (S2.2).

2.3 S3 Request-response over one-way protocol

2.3.1 Scenario Definition

A sender and receiver engage in a request-response interaction using a one-way underlying protocol. This requires both the use of SOAP headers and some metadata exchange between the parties.

2.4 S4 Non-declarative Features

2.4.1 Scenario Definition

A receiver requires a particular feature, whose specification indicates a different SOAP header should be sent depending upon the time of day.

2.5 S5 Feature expressed as underlying protocol data

2.5.1 Scenario Definition

The feature engaged is implemented as via one or more header fields of the underlying protocol.

2.6 S6 Asymetric feature

2.6.1 Scenario Definition

The feature engaged is asymetric.

2.7 S7 Features sharing properties

2.7.1 Scenario Definition

A security feature is described which exposes a "username" property. A second feature, for non-repudiation logging, utilizes the same property.

2.8 S8 Negociation feature

2.8.1 Scenario Definition

The use of a particular feature is negotiated via a negotiation feature.

2.9 S9 Absence Feature

2.9.1 Scenario Definition

A feature implemented in an intermediary to forward or not based on the presence or absence of another feature (e.g., SOAP header block). For example, assuming a policy that certain SOAP requests must include a digital signature to be forwarded, this feature would generate a fault if the signature header block is missing (or perhaps invalid). The feature may be able to redirect the sender to another intermediary that knows how to add the required signature.

3. References

3.1 Informative References

[XML 1.0]
Extensible Markup Language (XML) 1.0 (Second Edition), T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 10 February 1998, revised 6 October 2000. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006. The latest version of XML 1.0 is available at http://www.w3.org/TR/REC-xml.
[WSDL 1.2]
Web Services Description Language (WSDL) Version 1.2, R. Chinnici, M. Gudgin, J-J. Moreau, S. Weerawarana, Editors. World Wide Web Consortium, @@@@@@@@@@. This version of the Web Services Description Version 1.2 Specification is available is available at wsdl12.html. The latest version of Web Services Description Version 1.2 is available at http://www.w3.org/2002/ws/desc/wsdl12.
[WSDL 1.2 Bindings]
Web Services Description (WSDL) Version 1.2: Bindings, J-J. Moreau, J. Schlimmer, Editors. World Wide Web Consortium, @@@@@@@@@@. This version of the Web Services Description Version 1.2: Bindings Specification is available is available at wsdl12-bindings.html. The latest version of Web Services Description Version 1.2: Bindings is available at http://www.w3.org/2002/ws/desc/wsdl12-bindings.

A. Acknowledgements (Non-Normative)

This specification is the work of the W3C Web Service Description Working Group.

Participants in this Working Group are (at the time of writing, and by alphabetical order): Adi Sakala (IONA Technologies), Allen Brookes (Rogue Wave Softwave), Amelia Lewis (TIBCO/Extensibility), Arthur Ryman (IBM), Barbara Zengler (DaimlerChrysler Research and Technology), Dale Moberg (Cyclone Commerce), Dan Kulp (IONA Technologies), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), David Booth (W3C), Dietmar Gaertner (Software AG), Don Mullen (TIBCO Software), Erik Ackerman (Lexmark), Glen Daniels (Macromedia), Igor Sedukhin (Computer Associates), Jacek Kopecky (Systinet), Jean-Jacques Moreau (Canon), Jeff Mischkinsky (Oracle Corporation), Jeffrey Schlimmer (Microsoft Corporation), Jerry Thrasher (Lexmark), Johan Pauhlsson (L'Échangeur), Jonathan Marsh (Chair, Microsoft Corporation), Kevin Canyang Liu (SAP), Laurent De Teneuille (L'Échangeur), Lily Liu (webMethods, Inc.), Martin Gudgin (Microsoft Corporation), Michael Champion (Software AG), Michael Mahan (Nokia), Michael Mealling (Verisign), Mike Ballantyne (Electronic Data Systems), Mike Davoren (W. W. Grainger), Mike McHugh (W. W. Grainger), Philippe Le Hégaret (W3C), Prasad Yendluri (webMethods, Inc.), Roberto Chinnici (Sun Microsystems), Sandeep Kumar (Cisco Systems), Sandra Swearingen (U.S. Department of Defense, U.S. Air Force), Sanjiva Weerawarana (IBM), Stefano Pogliani (Sun Microsystems), Stephen White (SeeBeyond), Steve Graham (Global Grid Forum), Steve Lind (AT&T), Steve Tuecke (Global Grid Forum), Tim Finin (University of Maryland), Tom Jordahl (Macromedia), Umit Yalcinalp (Oracle Corporation), Waqar Sadiq (Electronic Data Systems), William Stumbo (Xerox), William Vambenepe (Hewlett-Packard Company), Youenn Fablet (Canon)

Previous participants were: Aaron Skonnard (DevelopMentor), Don Wright (Lexmark), Jochen Ruetschlin (DaimlerChrysler Research and Technology), Joyce Yang (Oracle Corporation), Keith Ballinger (Microsoft), Krishna Sankar (Cisco Systems), Mario Jeckle (DaimlerChrysler Research and Technology), Pallavi Malu (Intel Corporation)

The people who have contributed to discussions on www-ws-desc@w3.org are also gratefully acknowledged.

B. Part 1 Change Log (Non-Normative)

B.1 WSDL Specification Changes

DateAuthorDescription
20030225JJMIncoporated Paul's "Absence feature" scenario (S9).
20030220JJMReworded S8 according to Colleen's suggestion.
20030218JJMAdded negociation scenario, as suggested by DaveO and Colleen.
20030217JJMClarified further some of the scenarios.
20030217JJMIncorporated comments from Glen.
20030214JJMCreated document. Populated with scenarios discussed during the first PFTF Task Force.