- From: Amelia Lewis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 07 Nov 2006 18:54:36 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv5896
Added Files:
wsdl20-additional-meps.html
Log Message:
really adding the html, this time
--- NEW FILE: wsdl20-additional-meps.html ---
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>WSDL 2.0 Additional MEPs</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
dt.label { display: run-in; }
li, p { margin-top: 0.3em;
margin-bottom: 0.3em; }
.diff-chg { background-color: yellow; }
.diff-del { background-color: red; text-decoration: line-through;}
.diff-add { background-color: lime; }
table { empty-cells: show; }
table caption {
font-weight: normal;
font-style: italic;
text-align: left;
margin-bottom: .5em;
}
div.issue {
color: red;
}
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
th { color: #000000; background-color: #CCCC99; }
span.test-assertion { background-color: #FFC0CB; }
span.test-assertion-tr:hover { background-color: #FFC0CB; }
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body>
<div class="head">
<h1>WSDL 2.0 Additional MEPs</h1>
<h2 id="h2-title">Editors' copy $Date: 2006/11/07 18:54:34 $ @@ @@@@ @@@@</h2><dl><dt id="dt-this-version">This version:</dt><dd>
<a href="wsdl20-additional-meps.html">wsdl20-additional-meps.html</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/2002/ws/desc/wsdl20-additional-meps">http://www.w3.org/2002/ws/desc/wsdl20-additional-meps</a>
</dd><dt>Previous versions:</dt><dd>
<a href="http://none">http://none</a>
</dd><dt>Editor:</dt>
<dd>Amelia A. Lewis, TIBCO Software</dd>
</dl><p>This document is also available in these non-normative formats: <a href=""></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract">Abstract</a></h2>
<p>
WSDL 2.0 is an XML format for describing network services as a set
of endpoints operating on messages containing either
document-oriented or procedure-oriented information.
WSDL 2.0 Additional MEPs specifies predefined extensions for use in WSDL 2.0:
</p>
<ul>
<li><p>Message exchange patterns</p></li>
</ul>
<p>
This
specification depends on WSDL Version 2.0 [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].
</p>
</div><div>
<h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#meps">Additional Message Exchange Patterns</a><br>3. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#notcon">Notational Conventions</a><br> 1.2 <a href="#assertions">Assertions</a><br>2. <a href="#meps">Additional Message Exchange Patterns</a><br> 2.1 <a href="#mep-template">Template for Message Exchange Patterns</a><br> 2.1.1 <a href="#template-sample">Pattern Name</a><br> 2.2 <a href="#fault-rules">Fault Propagation Rules</a><br> 2.3 <a href="#patterns">Message Exchange Patterns</a><br> 2.3.1 <a href="#in-opt-out">In-Optional-Out message exchange pattern</a><br> 2.3.2 <a href="#out-only">Out-Only message exchange pattern</a><br> 2.3.3 <a href="#robust-out-only">Robust Out-Only message exchange pattern</a><br> 2.3.4 <a href="#out-in">Out-In message exchange pattern</a><br> 2.3.5 <a href="#out-opt-in">Out-Optional-In message exchange pattern</a><br> 2.4 <a hre="#mep-sec-sec">Security Considerations</a><br>3. <a href="#References">References</a><br> 3.1 <a href="#Normative-References">Normative References</a><br></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="intro"></a>1. Introduction</h2>
<p> The Web Services Description Language WSDL Version 2.0 (WSDL)
[<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] defines an XML language
for describing network services as collections of communication
endpoints capable of exchanging messages. WSDL service descriptions
provide documentation for distributed systems and serve as a recipe
for automating the details involved in applications
communication. This document defines extensions for the WSDL 2.0
language:</p>
<ul>
<li><p>Message exchange patterns: <a href="#meps"><b>2. Additional Message Exchange Patterns</b></a></p></li>
</ul>
<p> WSDL 2.0 Primer [<cite><a href="#">WSDL-PART0</a></cite>] is a non-normative
document intended to provide an easily understandable tutorial on the
features of the WSDL Version 2.0 specifications. </p>
<p> The Core Language [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] of the WSDL 2.0
specification describes the core elements of the WSDL language. </p>
<div class="div2">
<h3><a name="notcon"></a>1.1 Notational Conventions</h3>
<p>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 RFC2119 [<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].</p>
<p>This specification uses a number of namespace prefixes throughout;
they are listed in <a href="#tabprefns">Table 1-1</a>. Note that the choice of
any namespace prefix is arbitrary and not semantically significant
(see [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]).</p>
<a name="tabprefns"></a><br><table border="1" summary="Mapping of prefixes used in this document to their
associated namespace name">
<caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
<tbody>
<tr>
<th rowspan="1" colspan="1">Prefix</th>
<th rowspan="1" colspan="1">Namespace</th>
<th rowspan="1" colspan="1">Notes</th>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdl</td>
<td rowspan="1" colspan="1">
"http://www.w3.org/@@@@/@@/wsdl"
</td>
<td rowspan="1" colspan="1">
This namespace is defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>].
A normative XML Schema [<cite><a href="#">XMLSchemaP1</a></cite>],
[<cite><a href="#">XMLSchemaP2</a></cite>] document for the
"http://www.w3.org/@@@@/@@/wsdl"
namespace can be found at <a href="http://www.w3.org/@@@@/@@/wsdl">http://www.w3.org/@@@@/@@/wsdl</a>. This namespace is used as
the default namespace throughout this specification.</td>
</tr>
</tbody>
</table><br>
<p>This document is the product of the Web Services Description Working Group, but its contets
are non-normative. The Message Exchange Patterns defined herein are provided as examples of this form
of extensibility.</p>
</div>
<div class="div2">
<h3><a name="assertions"></a>1.2 Assertions</h3>
<p>
Assertions about WSDL 2.0 documents and components that are
not enforced by the normative XML schema for WSDL 2.0 are
marked by a dagger symbol (†) at the end of a
sentence. Each assertion has been assigned a unique
identifier that consists of a descriptive textual prefix and
a unique numeric suffix. The numeric suffixes are assigned
sequentially and never reused so there may be gaps in the
sequence. The assertion identifiers MAY be used by
implementations of this specification for any purpose,
e.g. error reporting.
</p>
</div>
</div>
<div class="div1">
<h2><a name="meps"></a>2. Additional Message Exchange Patterns</h2>
<p>
Web Services Description Language (WSDL) message exchange patterns (hereafter simply
'patterns') define the sequence and cardinality of abstract messages listed in
an operation. Message exchange patterns also define which other nodes send
messages to, and receive messages from, the service implementing the operation.
</p>
<p>
A <em>node</em> is an agent (<a href="http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#agent">section 2.3.2.2
Agent of the Web Services Architecture</a> [<cite><a href="#wsarch">Web Services Architecture</a></cite>]) that can transmit and/or receive message(s)
described in WSDL description(s) and process them.
</p>
<div class="note"><p class="prefix"><b>Note:</b></p>
<p>A
node MAY be accessible via more than one physical address or transport.</p>
</div>
<p>
WSDL message exchange patterns describe the interaction at the abstract
(interface) level, which may be distinct from the pattern used by the
underlying protocol binding.</p>
<p>
By design, WSDL message exchange patterns abstract out specific message types.
Patterns identify placeholders for messages, and placeholders are
associated with specific message types by the operation using the
pattern.
</p>
<p>
Unless explicitly stated otherwise, WSDL message exchange patterns also
abstract out binding-specific information such as timing between
messages, whether the pattern is synchronous or asynchronous, and
whether the messages are sent over a single or multiple channels.
</p>
<p>
Like interfaces and operations, WSDL message exchange patterns do not
exhaustively describe the set of messages exchanged between a service
and other nodes; by some prior agreement, another node and/or the
service MAY send other messages (to each other or to other nodes) that
are not described by the pattern. For instance, even though a pattern
may define a single message sent from a service to one other node, the
Web service may multicast that message to other nodes.
</p>
<p>
To maximize reuse, WSDL message exchange patterns identify a minimal contract
between other parties and Web services, and contain only information
that is relevant to both the Web service and another party.
</p>
<p>This specification defines several message exchange patterns for
use with <em>WSDL Version 2.0 Part 1: Core Language</em> [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>].</p>
<div class="div2">
<h3><a name="mep-template"></a>2.1 Template for Message Exchange Patterns</h3>
<p>New message exchange patterns may be defined by any organization able and
willing to do so. It is recommended that the patterns use the general
template provided here, after examination of existing predefined patterns.</p>
<div class="div3">
<h4><a name="template-sample"></a>2.1.1 Pattern Name</h4>
<p>This pattern consists of [number] message[s, in order] as follows:</p>
<p>[enumeration, specifying, for each message] A[n optional] message:</p>
<ol>
<li><p>indicated by an <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is
"[label]" and {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "[direction]"</p></li>
<li><p>[received from|sent to] ['some' if first mention] node [node
identifier]</p></li>
</ol>
<p>This pattern uses the rule [fault ruleset reference].</p>
<p>An <a href="wsdl20.html#component-InterfaceOperation">Interface Operation</a> using this message exchange pattern has a
{<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>}
property with the value "[pattern IRI]".</p>
<p>Note: In the template, the bracketed items indicate a replacement operation.
Substitute the correct terms for each bracketed item.</p>
<p>Note: the "received from" and "sent to" are always from the point of
view of the service, and participating nodes other than the service are
implicitly identified as the originators of or destinations for
messages in the exchange.</p>
</div>
</div>
<div class="div2">
<h3><a name="fault-rules"></a>2.2 Fault Propagation Rules</h3>
<p>These patterns use the fault propagation rulesets defined in [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</p>
</div>
<div class="div2">
<h3><a name="patterns"></a>2.3 Message Exchange Patterns</h3>
<p>WSDL patterns are described in terms of the WSDL component model,
specifically the <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>
and <a href="wsdl20.html#component-InterfaceFaultReference">Interface Fault Reference</a> components. </p>
<div class="div3">
<h4><a name="in-opt-out"></a>2.3.1 In-Optional-Out message exchange pattern</h4>
<p>The in-optional-out message exchange pattern consists of one or two messages, in order, as
follows:</p>
<ol>
<li><p>A message:</p>
<ul>
<li><p>indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is "In" and
{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "in"</p></li>
<li><p>received from some node N</p></li>
</ul>
</li>
<li><p>An optional message:</p>
<ul>
<li><p>indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is "Out" and
{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "out"</p></li>
<li><p>sent to node N</p></li>
</ul>
</li>
</ol>
<p>The in-optional-out message exchange pattern uses the rule
<a href="wsdl20-adjuncts.html#fault-trigger">Message Triggers
Fault</a>.</p>
<p>An operation using this message exchange pattern has
a {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>} property
with the value "http://www.w3.org/@@@@/@@/wsdl/in-opt-out".</p>
</div>
<div class="div3">
<h4><a name="out-only"></a>2.3.2 Out-Only message exchange pattern</h4>
<p>The out-only message exchange pattern
consists of exactly one message as follows:</p>
<ol>
<li>
<p>
A message:
</p>
<ul>
<li>
<p>
indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component
whose {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}
is "Out " and {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "out"
</p>
</li>
<li>
<p>
sent to some node N
</p>
</li>
</ul>
</li>
</ol>
<p>The out-only message exchange pattern uses the rule
<a href="wsdl20-adjuncts.html#no-fault">No Fault</a>.</p>
<p>
An operation using this message exchange pattern has
a {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>} property with
the value "http://www.w3.org/@@@@/@@/wsdl/out-only".
</p>
</div>
<div class="div3">
<h4><a name="robust-out-only"></a>2.3.3 Robust Out-Only message exchange pattern</h4>
<p>The robust out-only message exchange pattern
consists of exactly one message as follows:</p>
<ol>
<li><p>message:</p>
<ul>
<li><p>indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is "Out" and
{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "out"</p></li>
<li><p>sent to some node N</p></li>
</ul>
</li>
</ol>
<p>The robust out-only message exchange pattern uses the rule
<a href="wsdl20-adjuncts.html#fault-trigger">Message Triggers
Fault</a>.</p>
<p>An operation using this message exchange pattern has
a {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>} property with
the value "http://www.w3.org/@@@@/@@/wsdl/robust-out-only".</p>
</div>
<div class="div3">
<h4><a name="out-in"></a>2.3.4 Out-In message exchange pattern</h4>
<p>The out-in message exchange pattern consists of exactly two messages, in order, as
follows:</p>
<ol>
<li>
<p>
A message:
</p>
<ul>
<li>
<p>
indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component
whose {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}
is "Out" and {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "out"
</p>
</li>
<li>
<p>
sent to some node N
</p>
</li>
</ul>
</li>
<li>
<p>
A message:
</p>
<ul>
<li>
<p>
indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component
whose {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}
is "In" and {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "in"
</p>
</li>
<li>
<p>
sent from node N
</p>
</li>
</ul>
</li>
</ol>
<p>The out-in message exchange pattern uses the rule
<a href="wsdl20-adjuncts.html#fault-replacement">Fault Replaces
Message</a>.</p>
<p>
An operation using this message exchange pattern has
a {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>} property with
the value "http://www.w3.org/@@@@/@@/wsdl/out-in".
</p>
</div>
<div class="div3">
<h4><a name="out-opt-in"></a>2.3.5 Out-Optional-In message exchange pattern</h4>
<p>The out-optional-in message exchange pattern consists of one or two messages, in order, as
follows:</p>
<ol>
<li><p>A message:</p>
<ul>
<li><p>indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is "Out" and
{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "out"</p></li>
<li><p>sent to some node N</p></li>
</ul>
</li>
<li><p>An optional message:</p>
<ul>
<li><p>indicated by a <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component whose
{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>} is "In" and
{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>} is "in"</p></li>
<li><p>sent from node N</p></li>
</ul>
</li>
</ol>
<p>The out-optional-in message exchange pattern uses the rule
<a href="wsdl20-adjuncts.html#fault-trigger">Message Triggers
Fault</a>.</p>
<p>An operation using this message exchange pattern has
a {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>} property with
the value "http://www.w3.org/@@@@/@@/wsdl/out-opt-in".</p>
</div>
</div>
<div class="div2">
<h3><a name="mep-sec-sec"></a>2.4 Security Considerations</h3>
<p>Security considerations are discussed in [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</p>
</div>
</div>
<div class="div1">
<h2><a name="References"></a>3. References</h2>
<div class="div2">
<h3><a name="Normative-References"></a>3.1 Normative References</h3>
<dl>
<dt class="label"><a name="RFC2119"></a>[IETF RFC 2119]</dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement
Levels</a></cite>, S. Bradner, Author. Internet Engineering
Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.
</dd>
<dt class="label"><a name="RFC3986"></a>[IETF RFC 3986]</dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifiers (URI): Generic
Syntax</a></cite>, T. Berners-Lee, R. Fielding, L. Masinter,
Authors. Internet Engineering Task Force, January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt.
</dd>
<dt class="label"><a name="RFC3987"></a>[IETF RFC 3987]</dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers
(IRIs)</a></cite>, M. Duerst, M. Suignard,
Authors. Internet Engineering Task Force, January
2005. Available at http://www.ietf.org/rfc/rfc3987.txt.
</dd>
<dt class="label"><a name="wsarch"></a>[Web Services Architecture]</dt><dd>
<cite><a href="http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/">Web Services Architecture</a></cite>,
David Booth, Hugo Haas, Francis McCabe, Eric Newcomer, Michael Champion, Chris Ferris, David Orchard, Editors.
World Wide Web Consortium,
11 February 2004.
This version of the
"Web Services Architecture" Working Group Note is
http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/. The <a href="http://www.w3.org/TR/ws-arch/">latest version of
"Web Services Architecture"</a> is available at
http://www.w3.org/TR/ws-arch/.
</dd>
<dt class="label"><a name="WSDL-PART1"></a>[WSDL 2.0 Core Language]</dt><dd>
<cite><a href="wsdl20.html">Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</a></cite>, R. Chinnici, M. Gudgin, J-J. Moreau,
S. Weerawarana, Editors. World Wide Web Consortium,
@@ @@@@
@@@@. This version of the
"Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language" Specification is
available at wsdl20.html. The <a href="http://www.w3.org/2002/ws/desc/wsdl20">latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"</a> is available at
http://www.w3.org/2002/ws/desc/wsdl20.
</dd>
<dt class="label"><a name="WSDL-PART2"></a>[WSDL 2.0 Adjuncts]</dt><dd>
<cite><a href="wsdl20-adjuncts.html">Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts</a></cite>, R. Chinnici, H. Haas, A.
Lewis, J-J. Moreau, D. Orchard, S. Weerawarana, Editors. World
Wide Web Consortium, @@ @@@@ @@@@.
This version of the "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts" Specification is
available at wsdl20-adjuncts.html. The <a href="http://www.w3.org/2002/ws/desc/wsdl20-adjuncts">latest version of
"Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts"</a> is available at http://www.w3.org/2002/ws/desc/wsdl20-adjuncts.
</dd>
<dt class="label"><a name="XML10"></a>[XML 1.0]</dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204/">Extensible Markup Language (XML) 1.0 (Third
Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World Wide
Web Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
http://www.w3.org/TR/2004/REC-xml-20040204/. The <a href="http://www.w3.org/TR/REC-xml">latest version of "Extensible Markup Language (XML) 1.0"</a> is available at http://www.w3.org/TR/REC-xml.
</dd>
<dt class="label"><a name="XMLInfoSet"></a>[XML Information Set]</dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">XML Information Set (Second Edition)</a></cite>, J. Cowan and R.
Tobin, Editors. World Wide Web Consortium, 4 February 2004.
This version of the XML Information Set Recommendation is
http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <a href="http://www.w3.org/TR/xml-infoset">latest version of
XML Information Set</a> is available at
http://www.w3.org/TR/xml-infoset.
</dd>
</dl>
</div>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a name="acknowledgments"></a>A. Acknowledgements (Non-Normative)</h2>
<p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
Description Working Group</a>.</p>
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order):
Allen Brookes
(Rogue Wave Softwave), Dave Chappell
(Sonic Software), Helen Chen
(Agfa-Gevaert N. V.), Roberto Chinnici
(Sun Microsystems), Kendall Clark
(University of Maryland), Glen Daniels
(Sonic Software), Paul Downey
(British Telecommunications), Youenn Fablet
(Canon), Hugo Haas
(W3C), Tom Jordahl
(Macromedia), Anish Karmarkar
(Oracle Corporation), Jacek Kopecky
(DERI Innsbruck at the Leopold-Franzens-Universität
Innsbruck, Austria), Amelia Lewis
(TIBCO Software, Inc.), Michael Liddy
(Education.au Ltd.), Kevin Canyang Liu
(SAP AG), Jonathan Marsh
(Microsoft Corporation), Josephine Micallef
(SAIC - Telcordia Technologies), Jeff Mischkinsky
(Oracle Corporation), Dale Moberg
(Cyclone Commerce), Jean-Jacques Moreau
(Canon), Mark Nottingham
(BEA Systems, Inc.), David Orchard
(BEA Systems, Inc.), Vivek Pandey
(Sun Microsystems), Bijan Parsia
(University of Maryland), Gilbert Pilz
(BEA Systems, Inc.), Tony Rogers
(Computer Associates), Arthur Ryman
(IBM), Adi Sakala
(IONA Technologies), Asir Vedamuthu
(Microsoft Corporation), Sanjiva Weerawarana
(WSO2), Ümit Yalçınalp
(SAP AG).</p>
<p>Previous members were:
Lily Liu
(webMethods, Inc.), Don Wright
(Lexmark), Joyce Yang
(Oracle Corporation), Daniel Schutzer
(Citigroup), Dave Solo
(Citigroup), Stefano Pogliani
(Sun Microsystems), William Stumbo
(Xerox), Stephen White
(SeeBeyond), Barbara Zengler
(DaimlerChrysler Research and Technology), Tim Finin
(University of Maryland), Laurent De Teneuille
(L'Echangeur), Johan Pauhlsson
(L'Echangeur), Mark Jones
(AT&T), Steve Lind
(AT&T), Sandra Swearingen
(U.S. Department of Defense, U.S. Air Force), Philippe Le Hégaret
(W3C), Jim Hendler
(University of Maryland), Dietmar Gaertner
(Software AG), Michael Champion
(Software AG), Don Mullen
(TIBCO Software, Inc.), Steve Graham
(Global Grid Forum), Steve Tuecke
(Global Grid Forum), Michael Mahan
(Nokia), Bryan Thompson
(Hicks & Associates), Ingo Melzer
(DaimlerChrysler Research and Technology), Sandeep Kumar
(Cisco Systems), Alan Davies
(SeeBeyond), Jacek Kopecky
(Systinet), Mike Ballantyne
(Electronic Data Systems), Mike Davoren
(W. W. Grainger), Dan Kulp
(IONA Technologies), Mike McHugh
(W. W. Grainger), Michael Mealling
(Verisign), Waqar Sadiq
(Electronic Data Systems), Yaron Goland
(BEA Systems, Inc.), Ümit Yalçınalp
(Oracle Corporation), Peter Madziak
(Agfa-Gevaert N. V.), Jeffrey Schlimmer
(Microsoft Corporation), Hao He
(The Thomson Corporation), Erik Ackerman
(Lexmark), Jerry Thrasher
(Lexmark), Prasad Yendluri
(webMethods, Inc.), William Vambenepe
(Hewlett-Packard Company), David Booth
(W3C), Sanjiva Weerawarana
(IBM), Charlton Barreto
(webMethods, Inc.), Asir Vedamuthu
(webMethods, Inc.), Igor Sedukhin
(Computer Associates), Martin Gudgin
(Microsoft Corporation), Rebecca Bergersen
(IONA Technologies), Ugo Corda
(SeeBeyond).</p>
<p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
on www-ws-desc@w3.org</a> are also gratefully
acknowledged.</p>
</div>
<div class="div1">
<h2><a name="changelog"></a>B. Part 2 Change Log (Non-Normative)</h2>
<a name="wsdl-spec-changelog-table"></a><br><table border="1" width="100%">
<col width="10%" span="1">
<col width="10%" span="1">
<col width="80%" span="1">
<tbody>
<tr>
<th rowspan="1" colspan="1">Date</th>
<th rowspan="1" colspan="1">Author</th>
<th rowspan="1" colspan="1">Description</th>
</tr>
<tr>
<td rowspan="1" colspan="1">20061107</td>
<td rowspan="1" colspan="1">aal</td>
<td rowspan="1" colspan="1">More cleanup, especially references.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">20061107</td>
<td rowspan="1" colspan="1">aal</td>
<td rowspan="1" colspan="1">First pass revision/cleanup, mostly removing things.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">20061025</td>
<td rowspan="1" colspan="1">JJM</td>
<td rowspan="1" colspan="1">Created skeleton document from Part 2.</td>
</tr>
</tbody>
</table><br>
</div>
</div>
</body></html>
Received on Tuesday, 7 November 2006 18:54:49 UTC