W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > October to December 2005

2004/ws/addressing ws-addr-wsdl.html,1.28,1.29

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 24 Oct 2005 01:54:18 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1ETrXW-0000zZ-4W@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv3768

Modified Files:
	ws-addr-wsdl.html 
Log Message:
Sync with XML.

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** ws-addr-wsdl.html	17 Oct 2005 18:47:56 -0000	1.28
--- ws-addr-wsdl.html	24 Oct 2005 01:54:16 -0000	1.29
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
***************
*** 45,49 ****
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </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>Web Services Addressing 1.0 - WSDL Binding</h1>
--- 45,49 ----
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body>
      <div class="head">
  <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
***************
*** 68,73 ****
          no official standing.</strong></p><p></p></div>
      <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N66005">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N66061">WSDL SOAP Module</a><br>4. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&bsp;4.3 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href=#wsdl20inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#wsdl20outonly">Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> 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">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N68415">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N68425">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N68435">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.4 <a href="#N68445">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 68,74 ----
          no official standing.</strong></p><p></p></div>
      <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N101D5">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N1020D">WSDL SOAP Module</a><br>4. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&bsp;4.3 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href=#wsdl20inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#wsdl20outonly">Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of
!             WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N10B63">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10B6D">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10B77">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10B81">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 209,213 ****
                      "http://example.com/www.fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 210,214 ----
                      "http://example.com/www.fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 248,252 ****
                      an embedded description is undefined.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 249,253 ----
                      an embedded description is undefined.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 282,286 ****
                  </div>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 283,287 ----
                  </div>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 320,324 ****
              <div class="div2">
                  
! <h3><a name="N66005"></a>3.1 UsingAddressing Extension Element</h3>
                  <p>WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be
                      used to indicate that an endpoint conforms to the WS-Addressing specification.
--- 321,325 ----
              <div class="div2">
                  
! <h3><a name="N101D5"></a>3.1 UsingAddressing Extension Element</h3>
                  <p>WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be
                      used to indicate that an endpoint conforms to the WS-Addressing specification.
***************
*** 365,369 ****
                      address with a value different from the anonymous URI.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 366,370 ----
                      address with a value different from the anonymous URI.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
***************
*** 377,381 ****
                  </div>
                   <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
    &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
--- 378,382 ----
                  </div>
                   <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
    &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
***************
*** 395,399 ****
              <div class="div2">
                  
! <h3><a name="N66061"></a>3.2 WSDL SOAP Module</h3>
                  <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of
                      the WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a 
--- 396,400 ----
              <div class="div2">
                  
! <h3><a name="N1020D"></a>3.2 WSDL SOAP Module</h3>
                  <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of
                      the WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a 
***************
*** 406,410 ****
                      the following URI: http://www.w3.org/@@@@/@@/addressing/module</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-3. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 407,411 ----
                      the following URI: http://www.w3.org/@@@@/@@/addressing/module</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
***************
*** 450,454 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-1. </span>Explicit specification of wsaw:Action value in a WSDL 2.0 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 451,455 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Explicit specification of wsaw:Action value in a WSDL 2.0 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 469,473 ****
                      action for the output of this same operation is http://example.com/Quote.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 470,474 ----
                      action for the output of this same operation is http://example.com/Quote.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 496,500 ****
                      form of an action URI is as follows:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
--- 497,501 ----
                      form of an action URI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
***************
*** 503,507 ****
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
--- 504,508 ----
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
***************
*** 590,594 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
--- 591,595 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
***************
*** 623,627 ****
                      IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
--- 624,628 ----
                      IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
***************
*** 630,634 ****
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
--- 631,635 ----
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
***************
*** 683,687 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
--- 684,688 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
***************
*** 712,716 ****
                      not present. Consider the following example:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message names.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 713,717 ----
                      not present. Consider the following example:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message names.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 1061,1065 ****
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td align="left" valign="top" width="50%"><b>Editorial note: MJH</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">Given that [message id] is mandatory above, should [fault endpoint]
                              also be required ?</td></tr></table>
                      <table border="1">
--- 1062,1066 ----
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td width="50%" valign="top" align="left"><b>Editorial note: MJH</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">Given that [message id] is mandatory above, should [fault endpoint]
                              also be required ?</td></tr></table>
                      <table border="1">
***************
*** 1117,1121 ****
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td align="left" valign="top" width="50%"><b>Editorial note: MJH</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">Should [fault endpoint] be prohibited in the above ? This would
                              prevent getting a fault in response to a fault.</td></tr></table>
                  </div>
--- 1118,1122 ----
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td width="50%" valign="top" align="left"><b>Editorial note: MJH</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">Should [fault endpoint] be prohibited in the above ? This would
                              prevent getting a fault in response to a fault.</td></tr></table>
                  </div>
***************
*** 1354,1377 ****
  </div>
   <div class="div1">
              
! <h2><a name="changelog"></a>B. Change Log (Non-Normative)</h2>
          <div class="div2">
              
! <h3><a name="N68415"></a>B.1 Changes Since Third Working Draft</h3>
!             <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatres</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
          </div>
          <div class="div2">
                  
! <h3><a name="N68425"></a>B.2 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message sinatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Chaned MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added resolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68435"></a>B.3 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68445"></a>B.4 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
--- 1355,1422 ----
  </div>
   <div class="div1">
+         
+ <h2><a name="actioncompatibility"></a>B. Compatibility of [action] with previous versions of
+             WS-Addressing (Non-Normative)</h2>
+         <p>This section describes strategies for choosing [action] values
+             consistent between this specification and the WS-Addressing Member
+             Submission published 10 August 2004 (hereafter called "2004-08").  The
+             wsa200408 namespace prefix below refers to the
+             "http://schemas.xmlsoap.org/ws/2004/08/addressing" namespace defined
+                 in the 2004-08 version.
+         </p>
+         <p>The WS-Addressing 1.0 [action] property, which identifies the semantics
+             implied by a message, is semantically equivalent to the [action] message
+             information header defined in the 2004-08 version.  Authors are
+             therefore advised to use the same value for 1.0 [action] and 2004-08
+             [action].
+         </p>
+         <p>However, when describing services in WSDL, the namespace of the Action
+             attribute used to associate values with WSDL operations differs in the
+             two versions (wsaw:Action versus wsa200408:Action), and the default
+             action pattern in WS-Addressing 1.0 differs in two respects from that in
+             the 2004-08 version: the [delimiter] can be either "/" or ":" in 1.0
+             while in 2004-08 it is always "/", and the default action pattern for
+             faults is closer to that of other messages instead of a constant URI.
+         </p>
+         <p>If a default action pattern is desired, this specification recommends
+             the 1.0 default action pattern.  The 200408 [action] can be made
+             consistent with the 1.0 default by:
+         </p>
+         <ol>
+             <li>specifying wsa200408:Action explicitly when the targetNamespace
+                 is a URN, and</li>
+             <li>specifying wsa200408:Action explicitly when the message is a
+                 fault.</li>
+         </ol>
+          <p>
+              If the targetNamespace is a URN, it is not advisable to use the 2004-08
+             default action pattern, as it leads to malformed IRIs.  If the
+             targetNamespace is not a URN, and the 2004-08 default action pattern is
+             in use, the 1.0 [action] value can be made consistent by:
+           </p><ol>
+              <li>specifying wsaw:Action explicitly when the message is a fault.</li> 
+          </ol>
+     </div>
+         <div class="div1">
              
! <h2><a name="changelog"></a>C. Change Log (Non-Normative)</h2>
          <div class="div2">
              
! <h3><a name="N10B63"></a>C.1 Changes Since Third Working Draft</h3>
!             <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-1 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
          </div>
          <div class="div2">
                  
! <h3><a name="N10B6D"></a>C.2 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-9-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><d>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added resolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10B77"></a>C.3 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10B81"></a>C.4 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
Received on Monday, 24 October 2005 01:55:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT