Another abandoned server code base... this is kind of an ancestor of taskrambler.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

584 lines
24 KiB

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
<title>Web Services Description Language (WSDL) Version 2.0:
Additional MEPs</title>
<style type="text/css" xml:space="preserve">
/*<![CDATA[*/
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
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;
}
.rfc2119 {
font-variant: small-caps;
}
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/W3C-WG-NOTE.css" />
</head>
<body>
<div class="head">
<p><a href="http://www.w3.org/"><img src=
"http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width=
"72" /></a></p>
<h1><a name="title" id="title"></a>Web Services Description
Language (WSDL) Version 2.0: Additional MEPs</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Group
Note 26 June 2007</h2>
<dl>
<dt>This version:</dt>
<dd><a href=
"http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626">http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626</a></dd>
<dt>Latest version:</dt>
<dd><a href=
"http://www.w3.org/TR/wsdl20-additional-meps">http://www.w3.org/TR/wsdl20-additional-meps</a></dd>
<dt>Previous version:</dt>
<dd><a href=
"http://www.w3.org/TR/2007/WD-wsdl20-additional-meps-20070523">http://www.w3.org/TR/2007/WD-wsdl20-additional-meps-20070523</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="wsdl20-additional-meps.pdf">PDF</a>, <a href=
"wsdl20-additional-meps.ps">PostScript</a>, <a href=
"wsdl20-additional-meps.xml">XML</a>, and&#160;<a href=
"wsdl20-additional-meps.txt">plain text</a>.</p>
<p class="copyright"><a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&#160;©&#160;2007&#160;<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" id="abstract"></a>Abstract</h2>
<p>This specification defines additional message exchange patterns
(MEPs) to be used in WSDL 2.0 and are provided as examples of the
extensibility of WSDL 2.0.</p>
</div>
<div>
<h2><a name="status" id="status"></a>Status of this Document</h2>
<p><em>This section describes the status of this document at the
time of its publication. Other documents may supersede this
document. A list of current W3C publications and the latest
revision of this technical report can be found in the <a href=
"http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>
<p>This is a <a href=
"http://www.w3.org/2005/10/Process-20051014/tr.html#WGNote">W3C
Working Group Note</a> of Web Services Description Language (WSDL)
Version 2.0: Additional MEPs. It has been produced by the <a href=
"http://www.w3.org/2002/ws/desc/">Web Services Description Working
Group</a>, which is part of the <a href=
"http://www.w3.org/2002/ws/Activity">W3C Web Services
Activity</a>.</p>
<p>This document contains additional MEPs that were previously
defined in <em>Web Services Description Language (WSDL) Version 2.0
Part 2: Adjuncts</em> [<cite><a href="#WSDL-PART2">WSDL 2.0
Adjuncts</a></cite>].</p>
<p>Please send comments about this document to the public <a href=
"mailto:public-ws-desc-comments@w3.org">public-ws-desc-comments@w3.org</a>
mailing list (<a href=
"http://lists.w3.org/Archives/Public/public-ws-desc-comments/">public
archive</a>).</p>
<p>A <a href="wsdl20-additional-meps-diff.html">diff-marked version
against the previous version of this document</a> is available.</p>
<p>Publication as a Working Group Note does not imply endorsement
by the W3C Membership. However, this Working group Note reflects
the consensus of the Working Group, who provide it for the
convenience of the community.</p>
<p>This document is governed by the <a href=
"http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24
January 2002 CPP</a> as amended by the <a href=
"http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy
Transition Procedure</a>. W3C maintains a <a href=
"http://www.w3.org/2002/ws/desc/2/04/24-IPR-statements.html">public
list of any patent disclosures</a> made in connection with the
deliverables of the group; that page also includes instructions for
disclosing a patent. An individual who has actual knowledge of a
patent which the individual believes contains <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
Essential Claim(s)</a> must disclose the information in accordance
with <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
section 6 of the W3C Patent Policy</a>.</p>
</div>
<div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1. <a href="#intro">Introduction</a>
<br />
2. <a href="#meps">Additional Message Exchange Patterns</a>
<br />
&#160;&#160;&#160;&#160;2.1 <a href="#fault-rules">Fault
Propagation Rules</a>
<br />
&#160;&#160;&#160;&#160;2.2 <a href="#patterns">Message Exchange
Patterns</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.1 <a href=
"#in-opt-out">In-Optional-Out message exchange pattern</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.2 <a href=
"#out-only">Out-Only message exchange pattern</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.3 <a href=
"#robust-out-only">Robust Out-Only message exchange pattern</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.4 <a href=
"#out-in">Out-In message exchange pattern</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.5 <a href=
"#out-opt-in">Out-Optional-In message exchange pattern</a>
<br />
&#160;&#160;&#160;&#160;2.3 <a href="#mep-sec-sec">Security
Considerations</a>
<br />
3. <a href="#References">References</a>
<br />
&#160;&#160;&#160;&#160;3.1 <a href=
"#Normative-References">Normative References</a>
<br /></p>
<h3><a name="appendices" id="appendices"></a>Appendix</h3>
<p class="toc">A. <a href="#acknowledgments">Acknowledgements</a>
(Non-Normative)
<br /></p>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a name="intro" id="intro"></a>1. Introduction</h2>
<p>The Web Services Description Language Version 2.0 (WSDL 2.0)
[<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]
provides a model and an XML format for describing Web services.
WSDL 2.0 enables one to separate the description of the abstract
functionality offered by a service from concrete details of a
service description such as "how" and "where" that functionality is
offered. This document defines additional message exchange patterns
(MEPs) to be used in WSDL 2.0 and are provided as examples of the
extensibility of WSDL 2.0. This document is the product of the Web
Services Description Working Group, but its contents are
non-normative.</p>
</div>
<div class="div1">
<h2><a name="meps" id="meps"></a>2. Additional Message Exchange
Patterns</h2>
<p>Web Services Description Language (WSDL) [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines several message
exchange patterns (hereafter simply 'patterns'), as well as rules
for defining additional patterns.</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>].
The <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#mep-template">
template</a> defined in [<cite><a href="#WSDL-PART2">WSDL 2.0
Adjuncts</a></cite>] was used for the further contents of this
document.</p>
<p>These patterns were originally intended for inclusion in
<em>WSDL Version 2.0 Part 2: Adjunct</em> [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>]. The Working Group
ultimately decided that including only those patterns which were
referenced by the bindings defined in that specification was
clearer for implementors and users, and resolved to publish these
remaining patterns separately as a Note.</p>
<div class="div2">
<h3><a name="fault-rules" id="fault-rules"></a>2.1 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" id="patterns"></a>2.2 Message Exchange
Patterns</h3>
<p>WSDL patterns are described in terms of the WSDL component
model, specifically the <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> and <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceFaultReference">
Interface Fault Reference</a> components.</p>
<div class="div3">
<h4><a name="in-opt-out" id="in-opt-out"></a>2.2.1 In-Optional-Out
message exchange pattern</h4>
<p>The <code>in-optional-out</code> message exchange pattern
consists of one or two messages, in order, as follows:</p>
<ol class="enumar">
<li>
<p>A message:</p>
<ul>
<li>
<p>indicated by a <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "In" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#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=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "Out" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.direction">direction</a>}
is "out"</p>
</li>
<li>
<p>sent to node N</p>
</li>
</ul>
</li>
</ol>
<p>The <code>in-optional-out</code> message exchange pattern uses
the rule <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#fault-trigger">
Message Triggers Fault</a>.</p>
<p>An operation using this message exchange pattern has a {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property with the value
"http://www.w3.org/ns/wsdl/in-opt-out".</p>
</div>
<div class="div3">
<h4><a name="out-only" id="out-only"></a>2.2.2 Out-Only message
exchange pattern</h4>
<p>The <code>out-only</code> message exchange pattern consists of
exactly one message as follows:</p>
<ol class="enumar">
<li>
<p>A message:</p>
<ul>
<li>
<p>indicated by a <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "Out " and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.direction">direction</a>}
is "out"</p>
</li>
<li>
<p>sent to some node N</p>
</li>
</ul>
</li>
</ol>
<p>The <code>out-only</code> message exchange pattern uses the rule
<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#no-fault">No
Fault</a>.</p>
<p>An operation using this message exchange pattern has a {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property with the value
"http://www.w3.org/ns/wsdl/out-only".</p>
</div>
<div class="div3">
<h4><a name="robust-out-only" id="robust-out-only"></a>2.2.3 Robust
Out-Only message exchange pattern</h4>
<p>The <code>robust out-only</code> message exchange pattern
consists of exactly one message as follows:</p>
<ol class="enumar">
<li>
<p>message:</p>
<ul>
<li>
<p>indicated by a <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "Out" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.direction">direction</a>}
is "out"</p>
</li>
<li>
<p>sent to some node N</p>
</li>
</ul>
</li>
</ol>
<p>The <code>robust out-only</code> message exchange pattern uses
the rule <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#fault-trigger">
Message Triggers Fault</a>.</p>
<p>An operation using this message exchange pattern has a {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property with the value
"http://www.w3.org/ns/wsdl/robust-out-only".</p>
</div>
<div class="div3">
<h4><a name="out-in" id="out-in"></a>2.2.4 Out-In message exchange
pattern</h4>
<p>The <code>out-in</code> message exchange pattern consists of
exactly two messages, in order, as follows:</p>
<ol class="enumar">
<li>
<p>A message:</p>
<ul>
<li>
<p>indicated by a <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "Out" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#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=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "In" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.direction">direction</a>}
is "in"</p>
</li>
<li>
<p>sent from node N</p>
</li>
</ul>
</li>
</ol>
<p>The <code>out-in</code> message exchange pattern uses the rule
<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#fault-replacement">
Fault Replaces Message</a>.</p>
<p>An operation using this message exchange pattern has a {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property with the value
"http://www.w3.org/ns/wsdl/out-in".</p>
</div>
<div class="div3">
<h4><a name="out-opt-in" id="out-opt-in"></a>2.2.5 Out-Optional-In
message exchange pattern</h4>
<p>The <code>out-optional-in</code> message exchange pattern
consists of one or two messages, in order, as follows:</p>
<ol class="enumar">
<li>
<p>A message:</p>
<ul>
<li>
<p>indicated by a <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "Out" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#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=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#component-InterfaceMessageReference">
Interface Message Reference</a> component whose {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.messagelabel">message
label</a>} is "In" and {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceMessageReference.direction">direction</a>}
is "in"</p>
</li>
<li>
<p>sent from node N</p>
</li>
</ul>
</li>
</ol>
<p>The <code>out-optional-in</code> message exchange pattern uses
the rule <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626#fault-trigger">
Message Triggers Fault</a>.</p>
<p>An operation using this message exchange pattern has a {<a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property with the value
"http://www.w3.org/ns/wsdl/out-opt-in".</p>
</div>
</div>
<div class="div2">
<h3><a name="mep-sec-sec" id="mep-sec-sec"></a>2.3 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" id="References"></a>3. References</h2>
<div class="div2">
<h3><a name="Normative-References" id=
"Normative-References"></a>3.1 Normative References</h3>
<dl>
<dt class="label"><a name="WSDL-PART1" id="WSDL-PART1"></a>[WSDL
2.0 Core Language]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626">Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
Language</a></cite>, R. Chinnici, J-J. Moreau, A. Ryman, S.
Weerawarana, Editors. World Wide Web Consortium, 26 June 2007. This
version of the "Web Services Description Language (WSDL) Version
2.0 Part 1: Core Language" Specification is available at
http://www.w3.org/TR/2007/REC-wsdl20-20070626. The <a href=
"http://www.w3.org/TR/wsdl20">latest version of "Web Services
Description Language (WSDL) Version 2.0 Part 1: Core Language"</a>
is available at http://www.w3.org/TR/wsdl20.</dd>
<dt class="label"><a name="WSDL-PART2" id="WSDL-PART2"></a>[WSDL
2.0 Adjuncts]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626">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, 26
June 2007. This version of the "Web Services Description Language
(WSDL) Version 2.0 Part 2: Adjuncts" Specification is available at
http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626. The
<a href="http://www.w3.org/TR/wsdl20-adjuncts">latest version of
"Web Services Description Language (WSDL) Version 2.0 Part 2:
Adjuncts"</a> is available at
http://www.w3.org/TR/wsdl20-adjuncts.</dd>
</dl>
</div>
</div>
</div>
<div class="back div1">
<h2><a name="acknowledgments" id="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): Charlton Barreto (Adobe Systems, Inc), 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), Ram Jeyaraman (Microsoft), Tom Jordahl (Adobe
Systems), Anish Karmarkar (Oracle Corporation), Jacek Kopecky (DERI
Innsbruck at the Leopold-Franzens-Universität Innsbruck, Austria),
Amelia Lewis (TIBCO Software, Inc.), Philippe Le Hegaret (W3C),
Michael Liddy (Education.au Ltd.), Kevin Canyang Liu (SAP AG),
Jonathan Marsh (WSO2), Monica Martin (Sun Microsystems), Josephine
Micallef (SAIC - Telcordia Technologies), Jeff Mischkinsky (Oracle
Corporation), Dale Moberg (Cyclone Commerce), Jean-Jacques Moreau
(Canon), David Orchard (BEA Systems, Inc.), Gilbert Pilz (BEA
Systems, Inc.), Tony Rogers (Computer Associates), Arthur Ryman
(IBM), Adi Sakala (IONA Technologies), Michael Shepherd (Xerox),
Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2),
Ümit Yalçınalp (SAP AG), Peter Zehler (Xerox).</p>
<p>Previous members were: Eran Chinthaka (WSO2), Mark Nottingham
(BEA Systems, Inc.), Hugo Haas (W3C), Vivek Pandey (Sun
Microsystems), Bijan Parsia (University of Maryland), 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&amp;T), Steve Lind (AT&amp;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
&amp; 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), 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>
</body>
</html>