W3C

Web Services Description Language (WSDL) Version 1.2 Part 2: Message Patterns

W3C Working Draft 11 June 2003

This version:
http://www.w3.org/TR/2003/WD-wsdl12-patterns-20030611
Latest version:
http://www.w3.org/TR/wsdl12-patterns
Editors:
Martin Gudgin, Microsoft
Amy Lewis, TIBCO
Jeffrey Schlimmer, Microsoft

This document is also available in these non-normative formats: postscript, PDF, XML, and  plain text.

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

Abstract

This document describes Web Services Description Language (WSDL) Version 1.2 message patterns. These patterns are intended for use with the Web Services Description Language (WSDL).

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This is the first W3C Working Draft of the WSDL Version 1.2 Message Patterns specification for review by W3C members and other interested parties.

This document has been produced as part of the W3C Web Services Activity. The authors of this document are the Web Services Description Working Group members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or members of the Web Services Description Working Group.

Comments on this document are invited and are to be sent to public-ws-desc-comments@w3.org (public archive). It is inappropriate to send discussion emails to this address. Discussion of this document takes place on the public www-ws-desc@w3.org mailing list (public archive).

Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page.

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.

Short Table of Contents

1. Introduction
2. Message Patterns
3. References
A. Acknowledgements (Non-Normative)
B. Change Log (Non-Normative)

Table of Contents

1. Introduction
    1.1 Notational Conventions
2. Message Patterns
    2.1 In-Only
    2.2 In-Out
    2.3 Request-Response
    2.4 In-Multi-Out
    2.5 Out-Only
    2.6 Out-In
    2.7 Out-Multi-In
    2.8 Multicast-Solicit-Response
3. References
    3.1 Normative References
    3.2 Informative References

Appendices

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

1. Introduction

Web Services Description Language (WSDL) message patterns define the sequence, direction, and cardinality of abstract messages sent or received by an operation.

By design, WSDL message patterns abstract out specific message types; placeholders for messages identified by the pattern are associated with specific message types by the operation using the pattern.

Unless explicitly stated otherwise, WSDL message patterns also abstract out binding-specific information like timing between messages, whether the pattern is synchronous or asynchronous, and whether the message are sent over a single or multiple channels.

This specification defines several message patterns for use with WSDL Version 1.2 Part 1: Core Language [WSDL 1.2 Core Language].

1.1 Notational Conventions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [IETF RFC 2119].

2. Message Patterns

WSDL patterns are described in terms of the WSDL component model, specifically the message reference and fault reference components.

Editorial note: Pattern Review 5 March 2003
The working group plans to review the message patterns herein and eliminate those that are have not demonstrated to be useful (for example, supported by a binding with two interoperable implementations).

2.1 In-Only

This pattern consists of exactly one message as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-only'.

2.2 In-Out

This pattern consists of exactly two messages, in order, as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.

  • One of the following:

    • A message indicated by a message reference whose {name} is 'B' and {direction} is 'out', or

    • A message indicated by a fault reference whose {name} is 'C' and {direction} is 'out'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-out'.

2.3 Request-Response

This pattern is identical to In-Out with the following exception:

  • Any message with {direction} 'out' is sent on the same channel as the message with {direction} 'in'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/request-response'.

2.4 In-Multi-Out

This pattern consists of one or more messages, in order, as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'in'.

  • Zero or more messages indicated by a message reference whose {name} is 'B' and {direction} is 'out'.

  • An optional message indicated by a fault reference whose {name} is 'C' and {direction} is 'out'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/in-multi-out'.

2.5 Out-Only

This pattern consists of exactly one message as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-only'.

2.6 Out-In

This pattern consists of exactly two messages, in order, as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.

  • One of the following:

    • A message indicated by a message reference whose {name} is 'B' and {direction} is 'in', or

    • A message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-in'.

2.7 Out-Multi-In

This pattern consists of one or more messages, in order, as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'out'.

  • Zero or more messages indicated by a message reference whose {name} is 'B' and {direction} is 'in'.

  • An optional message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/out-multi-in'.

2.8 Multicast-Solicit-Response

This pattern consists of one or more messages, in sequence as follows:

  • A message indicated by a message reference whose {name} is 'A' and {direction} is 'out',

  • Zero or more messages, each of which is in one of the following sequences:

    • One or two messages, in sequence as follows:

      • A message indicated by a message reference whose {name} is 'B' and {direction} is 'in',

      • A message indicated by a fault reference whose {name} is 'D' and {direction} is 'out'.

    • A message indicated by a fault reference whose {name} is 'C' and {direction} is 'in'.

An operation using this message pattern has a {pattern} property with the value 'http://www.w3.org/2003/06/wsdl/multicast-solicit-response'.

3. References

3.1 Normative References

[IETF RFC 2119]
Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, Author. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2119.txt.
[WSDL 1.2 Core Language]
Web Services Description (WSDL) Version 1.2 Part 1: Core Language, R.Chinnici, M.Gudgin, J-J. Moreau, S.Weerawarana Editors. World Wide Web Consortium, 11 June 2003. This version of the "Web Services Description Version 1.2 Part 1: Core Language" Specification is available is available at http://www.w3.org/TR/2003/WD-wsdl12-20030611. The latest version of "Web Services Description Version 1.2 Part 1: Core Language" is available at http://www.w3.org/TR/wsdl12.

3.2 Informative References

[WSD Requirements]
Web Services Description Requirements, J. Schlimmer, Editor. World Wide Web Consortium, 28 October 2002. This version of the Web Services Description Requirements document is http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028. The latest version of Web Services Description Requirements is available at http://www.w3.org/TR/ws-desc-reqs.

A. Acknowledgements (Non-Normative)

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

Members of the Working Group are (at the time of writing, and by alphabetical order): Adi Sakala (IONA Technologies), Alan Davies (SeeBeyond), Allen Brookes (Rogue Wave Softwave), Amelia Lewis (TIBCO/Extensibility), Arthur Ryman (IBM), Bijan Parsia (University of Maryland), Dale Moberg (Cyclone Commerce), Dan Kulp (IONA Technologies), David Booth (W3C), Dietmar Gaertner (Software AG), Don Mullen (TIBCO Software), Erik Ackerman (Lexmark), Glen Daniels (Macromedia), Igor Sedukhin (Computer Associates), Ingo Melzer (DaimlerChrysler Research and Technology), Jacek Kopecky (Systinet), Jean-Jacques Moreau (Canon), Jeff Mischkinsky (Oracle Corporation), Jeffrey Schlimmer (Microsoft Corporation), Jerry Thrasher (Lexmark), Jim Hendler (University of Maryland), 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), Steve Graham (Global Grid Forum), Steve Lind (AT&T), Steve Tuecke (Global Grid Forum), Tom Jordahl (Macromedia), Umit Yalcinalp (Oracle Corporation), Waqar Sadiq (Electronic Data Systems), William Vambenepe (Hewlett-Packard Company), Youenn Fablet (Canon)

Previous members were: Aaron Skonnard (DevelopMentor), Don Wright (Lexmark), Barbara Zengler (DaimlerChrysler Research and Technology), 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), William Stumbo (Xerox), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), Stefano Pogliani (Sun Microsystems), Stephen White (SeeBeyond), Tim Finin (University of Maryland)

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

B. Change Log (Non-Normative)

B.1 Changes


Date Author Description
20030313 MJG Changed to Part 2 ( from Part 3 )
20030306 JCS Proposed name for MEP7.
20030305 JCS Per 4 Mar 03 meeting, renamed 'message exchange pattern' to 'message pattern' or 'pattern', added pattern for request-response, added ednote about review of patterns.
20030217 MJG Fixed some issues with entities and validity errors WRT ulists
20030212 JCS Initial draft