W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > July 2005

2002/ws/desc/wsdl20 wsdl20.html,1.210,1.211 wsdl20-adjuncts.html,1.51,1.52 wsdl20.xml,1.301,1.302 wsdl20.tex,1.63,1.64 wsdl20-primer.html,1.85,1.86 wsdl20-z-ie.html,1.29,1.30 wsdl20-z.html,1.49,1.50

From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 11 Jul 2005 19:54:53 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1Ds4Mf-0006mU-QO@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv25706/wsdl20

Modified Files:
	wsdl20.html wsdl20-adjuncts.html wsdl20.xml wsdl20.tex 
	wsdl20-primer.html wsdl20-z-ie.html wsdl20-z.html 
Log Message:
Updated Example C-2. IRI References - Example IRIs to match Appendix A.

Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.51
retrieving revision 1.52
diff -C2 -d -r1.51 -r1.52
*** wsdl20-adjuncts.html	22 Jun 2005 14:35:01 -0000	1.51
--- wsdl20-adjuncts.html	11 Jul 2005 19:54:49 -0000	1.52
***************
*** 91,95 ****
            </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.9.3 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
            </a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.10 <a href="#http-transfer-coding-decl">Specifying the Transfer Coding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.1 <a href="#http-transfer-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.2 <a href="#http-transfer-coding-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.3 <a href="#http-transfer-coding-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.4 <a href="#http-transfer-coding-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.11 <a href="#http-cookies-decl">Specifying the Use of HTTP Cookies</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.1 <a href="#http-cookies-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.2 <a href="#http-cookies-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.3 <a href="#http-cookies-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.4 <a href="#http-cookies-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.12 <a href="#http-auth-decl">Specifying HTTP Access Authentication</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.1 <a href="#http-auth-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.2 <a href="#http-auth-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.3 <a href="#http-auth-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.4 <a href="#http-auth-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.13 <a href="#http-conformance">Conformance</a><br>7. <a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#Informative-References">Informative 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="#N1267D">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N12E26">WSDL 2.0 Extensions Change Log</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N130B0">WSDL 2.0 Bindings Change Log</a><br></p></div><hr><div class="body">
  
      
--- 91,95 ----
            </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.9.3 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
            </a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.10 <a href="#http-transfer-coding-decl">Specifying the Transfer Coding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.1 <a href="#http-transfer-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.2 <a href="#http-transfer-coding-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.3 <a href="#http-transfer-coding-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.10.4 <a href="#http-transfer-coding-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.11 <a href="#http-cookies-decl">Specifying the Use of HTTP Cookies</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.1 <a href="#http-cookies-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.2 <a href="#http-cookies-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.3 <a href="#http-cookies-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.11.4 <a href="#http-cookies-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.12 <a href="#http-auth-decl">Specifying HTTP Access Authentication</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.1 <a href="#http-auth-description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.2 <a href="#http-auth-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.3 <a href="#http-auth-decl-xml">XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.12.4 <a href="#http-auth-decl-mapping">Mapping from XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.13 <a href="#http-conformance">Conformance</a><br>7. <a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#Informative-References">Informative 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="#N1267D">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N12E38">WSDL 2.0 Extensions Change Log</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N130C2">WSDL 2.0 Bindings Change Log</a><br></p></div><hr><div class="body">
  
      
***************
*** 355,365 ****
  <h4><a name="fault-trigger"></a>2.2.2 Message Triggers Fault</h4>
  
! <p>Any message, including the first, MAY trigger a fault message in
! response.  Each recipient MAY propagate a fault message, and MUST propagate no
! more than one fault for each triggering message.  Each fault message has 
! direction the reverse of its triggering message.  The fault message MUST 
! be delivered to the originator of the message which triggered it, unless otherwise
! specified by an extension or binding extension.  If there  is no path to this node,
! the fault MUST be discarded.
  </p>
  
--- 355,364 ----
  <h4><a name="fault-trigger"></a>2.2.2 Message Triggers Fault</h4>
  
! <p>Any message, including the first in the pattern, MAY trigger a fault 
! message, which MUST have opposite direction. The fault message MUST be 
! delivered to the originator of the triggering message, unless otherwise 
! specified by an extension of binding extension. Any node MAY propagate a 
! fault message, and MUST not do so more than once for each triggering 
! message. If there is no path to the originator, the fault MUST be discarded.
  </p>
  
***************
*** 4972,4975 ****
--- 4971,4979 ----
  	    
              <tr>
+ 	      <td rowspan="1" colspan="1">20050707</td>
+ 	      <td rowspan="1" colspan="1">aal</td>
+ 	      <td rowspan="1" colspan="1">Modified 2.2.2 per text supplied by Jean-Jacques.</td>
+ 	    </tr>
+             <tr>
                <td rowspan="1" colspan="1">20050616</td>
                <td rowspan="1" colspan="1">AGR</td>
***************
*** 5275,5279 ****
        <div class="div2">
        
! <h3><a name="N12E26"></a>C.1 WSDL 2.0 Extensions Change Log</h3>
  
        <a name="wsdl-changelog-table"></a><br><table border="1">
--- 5279,5283 ----
        <div class="div2">
        
! <h3><a name="N12E38"></a>C.1 WSDL 2.0 Extensions Change Log</h3>
  
        <a name="wsdl-changelog-table"></a><br><table border="1">
***************
*** 5523,5527 ****
        <div class="div2">
        
! <h3><a name="N130B0"></a>C.2 WSDL 2.0 Bindings Change Log</h3>
          <a name="wsdl-spec3-changelog-table"></a><br><table border="1">
            <tbody>
--- 5527,5531 ----
        <div class="div2">
        
! <h3><a name="N130C2"></a>C.2 WSDL 2.0 Bindings Change Log</h3>
          <a name="wsdl-spec3-changelog-table"></a><br><table border="1">
            <tbody>

Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** wsdl20-z-ie.html	20 Jun 2005 17:15:00 -0000	1.29
--- wsdl20-z-ie.html	11 Jul 2005 19:54:50 -0000	1.30
***************
*** 11223,11230 ****
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/listFlights) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
--- 11223,11245 ----
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsResponse) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/listFlights) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
***************
*** 11252,11256 ****
  <tr>
  <th rowspan="1" colspan="1">Component</th>
! <th rowspan="1" colspan="1">Properties</th>
  </tr>
  <tr>
--- 11267,11279 ----
  <tr>
  <th rowspan="1" colspan="1">Component</th>
! <th rowspan="1" colspan="1">Defined Properties</th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href=".html#component-"></a>
! </td>
! <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-.features">features</a>}, {<a href="wsdl20.html#property-.name">name</a>}, {<a href="wsdl20.html#property-.parent">parent</a>}, {<a href="wsdl20.html#property-.properties">properties</a>}
! </td>
  </tr>
  <tr>
***************
*** 11259,11263 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>},{<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>},{<a href="wsdl20.html#property-Binding.features">features</a>},{<a href="wsdl20.html#property-Binding.interface">interface</a>},{<a href="wsdl20.html#property-Binding.name">name</a>},{<a href="wsdl20.html#property-Binding.properties">properties</a>},{<a href="wsdl20.html#property-Binding.type">type</a>}
  </td>
  </tr>
--- 11282,11286 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>}, {<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>}, {<a href="wsdl20.html#property-Binding.features">features</a>}, {<a href="wsdl20.html#property-Binding.interface">interface</a>}, {<a href="wsdl20.html#property-Binding.name">name</a>}, {<a href="wsdl20.html#property-Binding.properties">properties</a>}, {<a href="wsdl20.html#property-Binding.type">type</a>}
  </td>
  </tr>
***************
*** 11267,11271 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFault.features">features</a>},{<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>},{<a href="wsdl20.html#property-BindingFault.parent">parent</a>},{<a href="wsdl20.html#property-BindingFault.properties">properties</a>}
  </td>
  </tr>
--- 11290,11294 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFault.features">features</a>}, {<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>}, {<a href="wsdl20.html#property-BindingFault.parent">parent</a>}, {<a href="wsdl20.html#property-BindingFault.properties">properties</a>}
  </td>
  </tr>
***************
*** 11275,11279 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFaultReference.features">features</a>},{<a href="wsdl20.html#property-BindingFaultReference.interfacefaultreference">interface fault reference</a>},{<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>},{<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>}
  </td>
  </tr>
--- 11298,11302 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFaultReference.features">features</a>}, {<a href="wsdl20.html#property-BindingFaultReference.interfacefaultreference">interface fault reference</a>}, {<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>}, {<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>}
  </td>
  </tr>
***************
*** 11283,11287 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingMessageReference.features">features</a>},{<a href="wsdl20.html#property-BindingMessageReference.interfacemessagereference">interface message reference</a>},{<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>},{<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>}
  </td>
  </tr>
--- 11306,11310 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingMessageReference.features">features</a>}, {<a href="wsdl20.html#property-BindingMessageReference.interfacemessagereference">interface message reference</a>}, {<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>}, {<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>}
  </td>
  </tr>
***************
*** 11291,11295 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingOperation.bindingfaultreferences">binding fault references</a>},{<a href="wsdl20.html#property-BindingOperation.bindingmessagereferences">binding message references</a>},{<a href="wsdl20.html#property-BindingOperation.features">features</a>},{<a href="wsdl20.html#property-BindingOperation.interfaceoperation">interface operation</a>},{<a href="wsdl20.html#property-BindingOperation.parent">parent</a>},{<a href="wsdl20.html#property-BindingOperation.properties">properties</a>}
  </td>
  </tr>
--- 11314,11318 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingOperation.bindingfaultreferences">binding fault references</a>}, {<a href="wsdl20.html#property-BindingOperation.bindingmessagereferences">binding message references</a>}, {<a href="wsdl20.html#property-BindingOperation.features">features</a>}, {<a href="wsdl20.html#property-BindingOperation.interfaceoperation">interface operation</a>}, {<a href="wsdl20.html#property-BindingOperation.parent">parent</a>}, {<a href="wsdl20.html#property-BindingOperation.properties">properties</a>}
  </td>
  </tr>
***************
*** 11299,11303 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Description.bindings">bindings</a>},{<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>},{<a href="wsdl20.html#property-Description.interfaces">interfaces</a>},{<a href="wsdl20.html#property-Description.services">services</a>},{<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
  </td>
  </tr>
--- 11322,11326 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Description.bindings">bindings</a>}, {<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>}, {<a href="wsdl20.html#property-Description.interfaces">interfaces</a>}, {<a href="wsdl20.html#property-Description.services">services</a>}, {<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
  </td>
  </tr>
***************
*** 11315,11319 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Endpoint.address">address</a>},{<a href="wsdl20.html#property-Endpoint.binding">binding</a>},{<a href="wsdl20.html#property-Endpoint.features">features</a>},{<a href="wsdl20.html#property-Endpoint.name">name</a>},{<a href="wsdl20.html#property-Endpoint.parent">parent</a>},{<a href="wsdl20.html#property-Endpoint.properties">properties</a>}
  </td>
  </tr>
--- 11338,11342 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Endpoint.address">address</a>}, {<a href="wsdl20.html#property-Endpoint.binding">binding</a>}, {<a href="wsdl20.html#property-Endpoint.features">features</a>}, {<a href="wsdl20.html#property-Endpoint.name">name</a>}, {<a href="wsdl20.html#property-Endpoint.parent">parent</a>}, {<a href="wsdl20.html#property-Endpoint.properties">properties</a>}
  </td>
  </tr>
***************
*** 11323,11327 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Feature.parent">parent</a>},{<a href="wsdl20.html#property-Feature.ref">ref</a>},{<a href="wsdl20.html#property-Feature.required">required</a>}
  </td>
  </tr>
--- 11346,11350 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Feature.parent">parent</a>}, {<a href="wsdl20.html#property-Feature.ref">ref</a>}, {<a href="wsdl20.html#property-Feature.required">required</a>}
  </td>
  </tr>
***************
*** 11331,11335 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>},{<a href="wsdl20.html#property-Interface.features">features</a>},{<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>},{<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>},{<a href="wsdl20.html#property-Interface.name">name</a>},{<a href="wsdl20.html#property-Interface.properties">properties</a>}
  </td>
  </tr>
--- 11354,11358 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>}, {<a href="wsdl20.html#property-Interface.features">features</a>}, {<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>}, {<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>}, {<a href="wsdl20.html#property-Interface.name">name</a>}, {<a href="wsdl20.html#property-Interface.properties">properties</a>}
  </td>
  </tr>
***************
*** 11339,11343 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>},{<a href="wsdl20.html#property-InterfaceFault.features">features</a>},{<a href="wsdl20.html#property-InterfaceFault.name">name</a>},{<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>},{<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>}
  </td>
  </tr>
--- 11362,11366 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>}, {<a href="wsdl20.html#property-InterfaceFault.features">features</a>}, {<a href="wsdl20.html#property-InterfaceFault.name">name</a>}, {<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>}
  </td>
  </tr>
***************
*** 11347,11351 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>}
  </td>
  </tr>
--- 11370,11374 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>}
  </td>
  </tr>
***************
*** 11355,11359 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>}
  </td>
  </tr>
--- 11378,11382 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>}
  </td>
  </tr>
***************
*** 11363,11367 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceOperation.features">features</a>},{<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>},{<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>},{<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>},{<a href="wsdl20.html#property-InterfaceOperation.name">name</a>},{<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>},{<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>},{<a href="wsdl20.html#property-InterfaceOperation.style">style</a>}
  </td>
  </tr>
--- 11386,11390 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceOperation.features">features</a>}, {<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>}, {<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>}, {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>}, {<a href="wsdl20.html#property-InterfaceOperation.name">name</a>}, {<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>}, {<a href="wsdl20.html#property-InterfaceOperation.style">style</a>}
  </td>
  </tr>
***************
*** 11371,11375 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Property.parent">parent</a>},{<a href="wsdl20.html#property-Property.ref">ref</a>},{<a href="wsdl20.html#property-Property.value">value</a>},{<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>}
  </td>
  </tr>
--- 11394,11398 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Property.parent">parent</a>}, {<a href="wsdl20.html#property-Property.ref">ref</a>}, {<a href="wsdl20.html#property-Property.value">value</a>}, {<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>}
  </td>
  </tr>
***************
*** 11379,11383 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Service.endpoints">endpoints</a>},{<a href="wsdl20.html#property-Service.features">features</a>},{<a href="wsdl20.html#property-Service.interface">interface</a>},{<a href="wsdl20.html#property-Service.name">name</a>},{<a href="wsdl20.html#property-Service.properties">properties</a>}
  </td>
  </tr>
--- 11402,11406 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Service.endpoints">endpoints</a>}, {<a href="wsdl20.html#property-Service.features">features</a>}, {<a href="wsdl20.html#property-Service.interface">interface</a>}, {<a href="wsdl20.html#property-Service.name">name</a>}, {<a href="wsdl20.html#property-Service.properties">properties</a>}
  </td>
  </tr>
***************
*** 11390,11393 ****
--- 11413,11580 ----
  </td>
  </tr>
+ <tr>
+ <th rowspan="1" colspan="1">Property</th>
+ <th rowspan="1" colspan="1">Where Defined</th>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">address</td>
+ <td rowspan="1" colspan="1">Endpoint.{<a href="wsdl20.html#property-Endpoint.address">address</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">binding</td>
+ <td rowspan="1" colspan="1">Endpoint.{<a href="wsdl20.html#property-Endpoint.binding">binding</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">binding faults</td>
+ <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">binding operations</td>
+ <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">bindings</td>
+ <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.bindings">bindings</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">direction</td>
+ <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">element declaration</td>
+ <td rowspan="1" colspan="1">Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">element declarations</td>
+ <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">endpoints</td>
+ <td rowspan="1" colspan="1">Service.{<a href="wsdl20.html#property-Service.endpoints">endpoints</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">extended interfaces</td>
+ <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">features</td>
+ <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.features">features</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.features">features</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.features">features</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>}, .{<a href="wsdl20.html#property-.features">features</a>}, Binding.{<a href="wsdl20.html#property-Binding.features">features</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.features">features</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.features">features</a>}, Service.{<a href="wsdl20.html#property-Service.features">features</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.features">features</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.features">features</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.features">features</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface</td>
+ <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.interface">interface</a>}, Service.{<a href="wsdl20.html#property-Service.interface">interface</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface fault</td>
+ <td rowspan="1" colspan="1">Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface fault references</td>
+ <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface faults</td>
+ <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface message references</td>
+ <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interface operations</td>
+ <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">interfaces</td>
+ <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.interfaces">interfaces</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">message content model</td>
+ <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">message exchange pattern</td>
+ <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">message label</td>
+ <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">name</td>
+ <td rowspan="1" colspan="1">Element Declaration.{<a href="wsdl20.html#property-ElementDeclaration.name">name</a>}, Type Definition.{<a href="wsdl20.html#property-TypeDefinition.name">name</a>}, Interface.{<a href="wsdl20.html#property-Interface.name">name</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.name">name</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.name">name</a>}, Binding.{<a href="wsdl20.html#property-Binding.name">name</a>}, Service.{<a href="wsdl20.html#property-Service.name">name</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.name">name</a>}, .{<a href="wsdl20.html#property-.name">name</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">parent</td>
+ <td rowspan="1" colspan="1">.{<a href="wsdl20.html#property-.parent">parent</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>}, Feature.{<a href="wsdl20.html#property-Feature.parent">parent</a>}, Property.{<a href="wsdl20.html#property-Property.parent">parent</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.parent">parent</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.parent">parent</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.parent">parent</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">properties</td>
+ <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.properties">properties</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>}, .{<a href="wsdl20.html#property-.properties">properties</a>}, Binding.{<a href="wsdl20.html#property-Binding.properties">properties</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.properties">properties</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.properties">properties</a>}, Service.{<a href="wsdl20.html#property-Service.properties">properties</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.properties">properties</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">ref</td>
+ <td rowspan="1" colspan="1">Feature.{<a href="wsdl20.html#property-Feature.ref">ref</a>}, Property.{<a href="wsdl20.html#property-Property.ref">ref</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">required</td>
+ <td rowspan="1" colspan="1">Feature.{<a href="wsdl20.html#property-Feature.required">required</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">services</td>
+ <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.services">services</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">style</td>
+ <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.style">style</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">type</td>
+ <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.type">type</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">type definitions</td>
+ <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">value</td>
+ <td rowspan="1" colspan="1">Property.{<a href="wsdl20.html#property-Property.value">value</a>}
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">value constraint</td>
+ <td rowspan="1" colspan="1">Property.{<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>}
+ </td>
+ </tr>
  </tbody>
  
***************
*** 11417,11420 ****
--- 11604,11614 ----
      
      <tr>
+     	<td rowspan="1" colspan="1">20050711</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Updated Example C-2. IRI References - Example IRIs to match Appendix A.
+      	</td>
+     </tr>
+     
+     <tr>
      	<td rowspan="1" colspan="1">20050616</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.63
retrieving revision 1.64
diff -C2 -d -r1.63 -r1.64
*** wsdl20.tex	22 Jun 2005 14:35:01 -0000	1.63
--- wsdl20.tex	11 Jul 2005 19:54:50 -0000	1.64
***************
*** 12347,12354 ****
  
  \begin{verbatim}
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/listFlights) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/reserveFlight)
  \end{verbatim}
  
--- 12347,12369 ----
  
  \begin{verbatim}
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsResponse) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/listFlights) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/reserveFlight)
  \end{verbatim}
  
***************
*** 12748,12751 ****
--- 12763,12773 ----
      
      
+     	20050711&
+     	AGR&
+     	Updated Example C-2. IRI References - Example IRIs to match Appendix A.
+      	
+     \\ \hline 
+     
+     
      	20050616&
      	AGR&

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.301
retrieving revision 1.302
diff -C2 -d -r1.301 -r1.302
*** wsdl20.xml	17 Jun 2005 01:33:46 -0000	1.301
--- wsdl20.xml	11 Jul 2005 19:54:49 -0000	1.302
***************
*** 12071,12078 ****
  <head>IRI References - Example IRIs</head>
  <eg xml:space="preserve">
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/listFlights) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/reserveFlight)
  </eg>
  </example>
--- 12071,12093 ----
  <head>IRI References - Example IRIs</head>
  <eg xml:space="preserve">
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsResponse) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/listFlights) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/reserveFlight)
  </eg>
  </example>
***************
*** 12119,12122 ****
--- 12134,12144 ----
      
      <tr>
+     	<td>20050711</td>
+     	<td>AGR</td>
+     	<td>Updated Example C-2. IRI References - Example IRIs to match Appendix A.
+      	</td>
+     </tr>
+     
+     <tr>
      	<td>20050616</td>
      	<td>AGR</td>

Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -C2 -d -r1.49 -r1.50
*** wsdl20-z.html	17 Jun 2005 01:33:47 -0000	1.49
--- wsdl20-z.html	11 Jul 2005 19:54:50 -0000	1.50
***************
*** 11193,11200 ****
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/listFlights) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
--- 11193,11215 ----
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsResponse) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/listFlights) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
***************
*** 11222,11289 ****
  <tr>
  <th rowspan="1" colspan="1">Component</th>
! <th rowspan="1" colspan="1">Properties</th>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-ElementDeclaration">Element Declaration</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-ElementDeclaration.name">name</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-TypeDefinition">Type Definition</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-TypeDefinition.name">name</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Description">Description</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Description.interfaces">interfaces</a>},{<a href="wsdl20.html#property-Description.bindings">bindings</a>},{<a href="wsdl20.html#property-Description.services">services</a>},{<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>},{<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Interface">Interface</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Interface.name">name</a>},{<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>},{<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>},{<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>},{<a href="wsdl20.html#property-Interface.features">features</a>},{<a href="wsdl20.html#property-Interface.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFault.name">name</a>},{<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>},{<a href="wsdl20.html#property-InterfaceFault.features">features</a>},{<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>},{<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceOperation">Interface Operation</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceOperation.name">name</a>},{<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>},{<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>},{<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>},{<a href="wsdl20.html#property-InterfaceOperation.style">style</a>},{<a href="wsdl20.html#property-InterfaceOperation.features">features</a>},{<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>},{<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>},{<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceFaultReference">Interface Fault Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>},{<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>}
  </td>
  </tr>
--- 11237,11312 ----
  <tr>
  <th rowspan="1" colspan="1">Component</th>
! <th rowspan="1" colspan="1">Defined Properties</th>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href=".html#component-"></a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-.features">features</a>}, {<a href="wsdl20.html#property-.name">name</a>}, {<a href="wsdl20.html#property-.parent">parent</a>}, {<a href="wsdl20.html#property-.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Binding">Binding</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>}, {<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>}, {<a href="wsdl20.html#property-Binding.features">features</a>}, {<a href="wsdl20.html#property-Binding.interface">interface</a>}, {<a href="wsdl20.html#property-Binding.name">name</a>}, {<a href="wsdl20.html#property-Binding.properties">properties</a>}, {<a href="wsdl20.html#property-Binding.type">type</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingFault">Binding Fault</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFault.features">features</a>}, {<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>}, {<a href="wsdl20.html#property-BindingFault.parent">parent</a>}, {<a href="wsdl20.html#property-BindingFault.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingFaultReference">Binding Fault Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFaultReference.features">features</a>}, {<a href="wsdl20.html#property-BindingFaultReference.interfacefaultreference">interface fault reference</a>}, {<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>}, {<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingMessageReference">Binding Message Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingMessageReference.features">features</a>}, {<a href="wsdl20.html#property-BindingMessageReference.interfacemessagereference">interface message reference</a>}, {<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>}, {<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingOperation">Binding Operation</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingOperation.bindingfaultreferences">binding fault references</a>}, {<a href="wsdl20.html#property-BindingOperation.bindingmessagereferences">binding message references</a>}, {<a href="wsdl20.html#property-BindingOperation.features">features</a>}, {<a href="wsdl20.html#property-BindingOperation.interfaceoperation">interface operation</a>}, {<a href="wsdl20.html#property-BindingOperation.parent">parent</a>}, {<a href="wsdl20.html#property-BindingOperation.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Description">Description</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Description.bindings">bindings</a>}, {<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>}, {<a href="wsdl20.html#property-Description.interfaces">interfaces</a>}, {<a href="wsdl20.html#property-Description.services">services</a>}, {<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-ElementDeclaration">Element Declaration</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-ElementDeclaration.name">name</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Endpoint">Endpoint</a>
! </td>
! <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Endpoint.address">address</a>}, {<a href="wsdl20.html#property-Endpoint.binding">binding</a>}, {<a href="wsdl20.html#property-Endpoint.features">features</a>}, {<a href="wsdl20.html#property-Endpoint.name">name</a>}, {<a href="wsdl20.html#property-Endpoint.parent">parent</a>}, {<a href="wsdl20.html#property-Endpoint.properties">properties</a>}
  </td>
  </tr>
***************
*** 11293,11345 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Feature.ref">ref</a>},{<a href="wsdl20.html#property-Feature.required">required</a>},{<a href="wsdl20.html#property-Feature.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Property">Property</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Property.ref">ref</a>},{<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>},{<a href="wsdl20.html#property-Property.value">value</a>},{<a href="wsdl20.html#property-Property.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Binding">Binding</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Binding.name">name</a>},{<a href="wsdl20.html#property-Binding.interface">interface</a>},{<a href="wsdl20.html#property-Binding.type">type</a>},{<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>},{<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>},{<a href="wsdl20.html#property-Binding.features">features</a>},{<a href="wsdl20.html#property-Binding.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingFault">Binding Fault</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>},{<a href="wsdl20.html#property-BindingFault.features">features</a>},{<a href="wsdl20.html#property-BindingFault.properties">properties</a>},{<a href="wsdl20.html#property-BindingFault.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingOperation">Binding Operation</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingOperation.interfaceoperation">interface operation</a>},{<a href="wsdl20.html#property-BindingOperation.bindingmessagereferences">binding message references</a>},{<a href="wsdl20.html#property-BindingOperation.bindingfaultreferences">binding fault references</a>},{<a href="wsdl20.html#property-BindingOperation.features">features</a>},{<a href="wsdl20.html#property-BindingOperation.properties">properties</a>},{<a href="wsdl20.html#property-BindingOperation.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingMessageReference">Binding Message Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingMessageReference.interfacemessagereference">interface message reference</a>},{<a href="wsdl20.html#property-BindingMessageReference.features">features</a>},{<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>},{<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-BindingFaultReference">Binding Fault Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-BindingFaultReference.interfacefaultreference">interface fault reference</a>},{<a href="wsdl20.html#property-BindingFaultReference.features">features</a>},{<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>},{<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>}
  </td>
  </tr>
--- 11316,11368 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Feature.parent">parent</a>}, {<a href="wsdl20.html#property-Feature.ref">ref</a>}, {<a href="wsdl20.html#property-Feature.required">required</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Interface">Interface</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>}, {<a href="wsdl20.html#property-Interface.features">features</a>}, {<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>}, {<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>}, {<a href="wsdl20.html#property-Interface.name">name</a>}, {<a href="wsdl20.html#property-Interface.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>}, {<a href="wsdl20.html#property-InterfaceFault.features">features</a>}, {<a href="wsdl20.html#property-InterfaceFault.name">name</a>}, {<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceFaultReference">Interface Fault Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-InterfaceOperation">Interface Operation</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-InterfaceOperation.features">features</a>}, {<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>}, {<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>}, {<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>}, {<a href="wsdl20.html#property-InterfaceOperation.name">name</a>}, {<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>}, {<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>}, {<a href="wsdl20.html#property-InterfaceOperation.style">style</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Property">Property</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Property.parent">parent</a>}, {<a href="wsdl20.html#property-Property.ref">ref</a>}, {<a href="wsdl20.html#property-Property.value">value</a>}, {<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>}
  </td>
  </tr>
***************
*** 11349,11361 ****
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Service.name">name</a>},{<a href="wsdl20.html#property-Service.interface">interface</a>},{<a href="wsdl20.html#property-Service.endpoints">endpoints</a>},{<a href="wsdl20.html#property-Service.features">features</a>},{<a href="wsdl20.html#property-Service.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-Endpoint">Endpoint</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Endpoint.name">name</a>},{<a href="wsdl20.html#property-Endpoint.binding">binding</a>},{<a href="wsdl20.html#property-Endpoint.address">address</a>},{<a href="wsdl20.html#property-Endpoint.features">features</a>},{<a href="wsdl20.html#property-Endpoint.properties">properties</a>},{<a href="wsdl20.html#property-Endpoint.parent">parent</a>}
  </td>
  </tr>
--- 11372,11548 ----
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-Service.endpoints">endpoints</a>}, {<a href="wsdl20.html#property-Service.features">features</a>}, {<a href="wsdl20.html#property-Service.interface">interface</a>}, {<a href="wsdl20.html#property-Service.name">name</a>}, {<a href="wsdl20.html#property-Service.properties">properties</a>}
  </td>
  </tr>
  <tr>
  <td rowspan="1" colspan="1">
! <a href="wsdl20.html#component-TypeDefinition">Type Definition</a>
  </td>
  <td rowspan="1" colspan="1">
! {<a href="wsdl20.html#property-TypeDefinition.name">name</a>}
! </td>
! </tr>
! <tr>
! <th rowspan="1" colspan="1">Property</th>
! <th rowspan="1" colspan="1">Where Defined</th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">address</td>
! <td rowspan="1" colspan="1">Endpoint.{<a href="wsdl20.html#property-Endpoint.address">address</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">binding</td>
! <td rowspan="1" colspan="1">Endpoint.{<a href="wsdl20.html#property-Endpoint.binding">binding</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">binding faults</td>
! <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.bindingfaults">binding faults</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">binding operations</td>
! <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.bindingoperations">binding operations</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">bindings</td>
! <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.bindings">bindings</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">direction</td>
! <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.direction">direction</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.direction">direction</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">element declaration</td>
! <td rowspan="1" colspan="1">Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.elementdeclaration">element declaration</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.elementdeclaration">element declaration</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">element declarations</td>
! <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.elementdeclarations">element declarations</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">endpoints</td>
! <td rowspan="1" colspan="1">Service.{<a href="wsdl20.html#property-Service.endpoints">endpoints</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">extended interfaces</td>
! <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">features</td>
! <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.features">features</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.features">features</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.features">features</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.features">features</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.features">features</a>}, .{<a href="wsdl20.html#property-.features">features</a>}, Binding.{<a href="wsdl20.html#property-Binding.features">features</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.features">features</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.features">features</a>}, Service.{<a href="wsdl20.html#property-Service.features">features</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.features">features</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.features">features</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.features">features</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface</td>
! <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.interface">interface</a>}, Service.{<a href="wsdl20.html#property-Service.interface">interface</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface fault</td>
! <td rowspan="1" colspan="1">Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.interfacefault">interface fault</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.interfacefault">interface fault</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface fault references</td>
! <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.interfacefaultreferences">interface fault references</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface faults</td>
! <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.interfacefaults">interface faults</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface message references</td>
! <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.interfacemessagereferences">interface message references</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interface operations</td>
! <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.interfaceoperations">interface operations</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">interfaces</td>
! <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.interfaces">interfaces</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">message content model</td>
! <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.messagecontentmodel">message content model</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">message exchange pattern</td>
! <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.messageexchangepattern">message exchange pattern</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">message label</td>
! <td rowspan="1" colspan="1">Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.messagelabel">message label</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.messagelabel">message label</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">name</td>
! <td rowspan="1" colspan="1">Element Declaration.{<a href="wsdl20.html#property-ElementDeclaration.name">name</a>}, Type Definition.{<a href="wsdl20.html#property-TypeDefinition.name">name</a>}, Interface.{<a href="wsdl20.html#property-Interface.name">name</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.name">name</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.name">name</a>}, Binding.{<a href="wsdl20.html#property-Binding.name">name</a>}, Service.{<a href="wsdl20.html#property-Service.name">name</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.name">name</a>}, .{<a href="wsdl20.html#property-.name">name</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">parent</td>
! <td rowspan="1" colspan="1">.{<a href="wsdl20.html#property-.parent">parent</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.parent">parent</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.parent">parent</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.parent">parent</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.parent">parent</a>}, Feature.{<a href="wsdl20.html#property-Feature.parent">parent</a>}, Property.{<a href="wsdl20.html#property-Property.parent">parent</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.parent">parent</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.parent">parent</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.parent">parent</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.parent">parent</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.parent">parent</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">properties</td>
! <td rowspan="1" colspan="1">Interface.{<a href="wsdl20.html#property-Interface.properties">properties</a>}, Interface Fault.{<a href="wsdl20.html#property-InterfaceFault.properties">properties</a>}, Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.properties">properties</a>}, Interface Message Reference.{<a href="wsdl20.html#property-InterfaceMessageReference.properties">properties</a>}, Interface Fault Reference.{<a href="wsdl20.html#property-InterfaceFaultReference.properties">properties</a>}, .{<a href="wsdl20.html#property-.properties">properties</a>}, Binding.{<a href="wsdl20.html#property-Binding.properties">properties</a>}, Binding Fault.{<a href="wsdl20.html#property-BindingFault.properties">properties</a>}, Binding Operation.{<a href="wsdl20.html#property-BindingOperation.properties">properties</a>}, Service.{<a href="wsdl20.html#property-Service.properties">properties</a>}, Endpoint.{<a href="wsdl20.html#property-Endpoint.properties">properties</a>}, Binding Message Reference.{<a href="wsdl20.html#property-BindingMessageReference.properties">properties</a>}, Binding Fault Reference.{<a href="wsdl20.html#property-BindingFaultReference.properties">properties</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">ref</td>
! <td rowspan="1" colspan="1">Feature.{<a href="wsdl20.html#property-Feature.ref">ref</a>}, Property.{<a href="wsdl20.html#property-Property.ref">ref</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">required</td>
! <td rowspan="1" colspan="1">Feature.{<a href="wsdl20.html#property-Feature.required">required</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">services</td>
! <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.services">services</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">style</td>
! <td rowspan="1" colspan="1">Interface Operation.{<a href="wsdl20.html#property-InterfaceOperation.style">style</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">type</td>
! <td rowspan="1" colspan="1">Binding.{<a href="wsdl20.html#property-Binding.type">type</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">type definitions</td>
! <td rowspan="1" colspan="1">Description.{<a href="wsdl20.html#property-Description.typedefinitions">type definitions</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">value</td>
! <td rowspan="1" colspan="1">Property.{<a href="wsdl20.html#property-Property.value">value</a>}
! </td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">value constraint</td>
! <td rowspan="1" colspan="1">Property.{<a href="wsdl20.html#property-Property.valueconstraint">value constraint</a>}
  </td>
  </tr>
***************
*** 11387,11390 ****
--- 11574,11584 ----
      
      <tr>
+     	<td rowspan="1" colspan="1">20050711</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Updated Example C-2. IRI References - Example IRIs to match Appendix A.
+      	</td>
+     </tr>
+     
+     <tr>
      	<td rowspan="1" colspan="1">20050616</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.210
retrieving revision 1.211
diff -C2 -d -r1.210 -r1.211
*** wsdl20.html	22 Jun 2005 14:35:01 -0000	1.210
--- wsdl20.html	11 Jul 2005 19:54:49 -0000	1.211
***************
*** 8956,8963 ****
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/listFlights) 
! http://example.org/TicketAgent.wsdl20#wsdl.operation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
--- 8956,8978 ----
  <p class="exampleHead" style="text-align: left"><a name="iri-ref-example-iris"></a><i><span>Example C-2. </span>IRI References - Example IRIs</i></p>
  <div class="exampleInner"><pre>
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:listFlightsResponse) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightRequest) 
+ 
+ http://example.org/TicketAgent.wsdl20#xmlns(xsTicketAgent=http://example.org/TicketAgent.xsd)
+ 	wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent) 
+ 
  http://example.org/TicketAgent.wsdl20#wsdl.feature(wsdl.interface(TicketAgent)/http://example.com/secure-channel) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/listFlights) 
! 
! http://example.org/TicketAgent.wsdl20#wsdl.interfaceOperation(TicketAgent/reserveFlight)
  </pre></div>
  </div>
***************
*** 9322,9325 ****
--- 9337,9347 ----
      
      <tr>
+     	<td rowspan="1" colspan="1">20050711</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Updated Example C-2. IRI References - Example IRIs to match Appendix A.
+      	</td>
+     </tr>
+     
+     <tr>
      	<td rowspan="1" colspan="1">20050616</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.85
retrieving revision 1.86
diff -C2 -d -r1.85 -r1.86
*** wsdl20-primer.html	6 Jul 2005 20:35:26 -0000	1.85
--- wsdl20-primer.html	11 Jul 2005 19:54:50 -0000	1.86
***************
*** 1,3 ****
! <!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>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</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"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</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 Description Language (WSDL) Version 2.0 Part 0: Primer</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 Description Language (WSDL) Version 2.0 Part 0: Primer</h1>
***************
*** 96,103 ****
  	<hr><div class="toc">
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>6. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</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="#Introduction">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#Prerequisites">Prerequisites</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#PrimerStructure">Structure of this Primer</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3 <a href="#basics-types">Defining Message Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.4 <a href="#basics-interface">Defining an Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.5 <a href="#basics-binding">Defining a Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.6 <a href="#basics-service">Defining a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.6.1 <a href="#example-initial-service-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.7 <a href="#basics-documentation">Documenting the Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.1 <a href="#element-order">WSDL2.0 Element Ordering</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#more-types">More on Message Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#more-interfaces">More on Interfaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2 <a href="#N67903">Operation Message References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.1 <a href="#N67932">The messageLabel Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.2 <a href="#N67956">The element Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.3 <a href="#N68037">Multiple infault or outfault Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#more-bindings">More on Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.4 <a href="#bindingOperations">Binding Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.6.1 <a href="#N68496">Explanation of
! 			Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#N68832">Schemas in Imported Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.2 <a href="#N68971">Multiple Inline Schemas in One Document</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3.1 <a href="#N69067">Using the id Attribute to Identify Inline
! 						Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#adv-extensibility">Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#adv-FP">Features and Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#adv-fp-properties">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#adv-MEP">Defining New MEPs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.4 <a href="#adv-RPCstyle">RPC Style</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.5 <a href="#adv-MTOM">MTOM and Attachments Support</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#adv-versioning">Web Service Versioning</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.1 <a href="#N70059">Additional Optional Elements Added in Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.2 <a href="#N70082">Additional Optional Elements Added to a Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.3 <a href="#N70105">Additional Mandatory Elements in Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.4 <a href="#N70128">Additional Optional Operation Added to Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.5 <a href="#N70140">Additional Mandatory Operation Added to Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.6 <a href="#N70166">Indicating Incompatibility by Changing the Endpoint URI</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.7 <a href="#N70175">Indicating Incompatibility by Changing the SOAP Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.8 <a href="#N70198">Indicating Incompatibility by Changing the Element Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#adv-service-references">Describing Web Service Messages That Refer to Other Web Services</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#reservationDetails">The Reservation Details Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#reservationList">The Reservation List Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.3 <a href="#reservationDetails_HTTP">Reservation Details Web Service Using HTTP Transfer</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.4 <a href="#reservationList_HTTP_GET">Reservation List Web Service Using HTTP GET</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#adv-multiple-docs-describing-same-service">Multiple Interfaces for the Same Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.5 <a href="#adv-rdf-mapping">Mapping to RDF and Semantic Web</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.5.1 <a href="#adv-rdf-rep-wsdl">RDF Representation of WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.6 <a href="#adv-notes-on-uris">Notes on URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.1 <a href="#adv-namespaces-and-schema-locations">XML Namespaces and Schema Locations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.2 <a href="#adv-relative-uris">Relative URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.3 <a href="#adv-generating-uris">Generating Temporary URIs</a><br>6. <a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendix</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="body">
  		
  		
--- 96,103 ----
  	<hr><div class="toc">
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>6. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</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="#Introduction">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#Prerequisites">Prerequisites</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#PrimerStructure">Structure of this Primer</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3 <a href="#basics-types">Defining Message Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.4 <a href="#basics-interface">Defining an Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.5 <a href="#basics-binding">Defining a Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.6 <a href="#basics-service">Defining a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.6.1 <a href="#example-initial-service-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.7 <a href="#basics-documentation">Documenting the Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.1 <a href="#element-order">WSDL2.0 Element Ordering</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#more-types">More on Message Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#more-interfaces">More on Interfaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2 <a href="#N1093F">Operation Message References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.1 <a href="#N1095C">The messageLabel Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.2 <a href="#N10974">The element Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.2.3 <a href="#N109C5">Multiple infault or outfault Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#more-bindings">More on Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.4 <a href="#bindingOperations">Binding Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.6.1 <a href="#N10B90">Explanation of
! 			Example</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#N10CE0">Schemas in Imported Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.2 <a href="#N10D6B">Multiple Inline Schemas in One Document</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3.1 <a href="#N10DCB">Using the id Attribute to Identify Inline
! 						Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#adv-extensibility">Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#adv-FP">Features and Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#adv-fp-properties">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#adv-MEP">Defining New MEPs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.4 <a href="#adv-RPCstyle">RPC Style</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.5 <a href="#adv-MTOM">MTOM and Attachments Support</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#adv-versioning">Web Service Versioning</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.1 <a href="#N111AB">Additional Optional Elements Added in Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.2 <a href="#N111C2">Additional Optional Elements Added to a Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.3 <a href="#N111D9">Additional Mandatory Elements in Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.4 <a href="#N111F0">Additional Optional Operation Added to Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.5 <a href="#N111FC">Additional Mandatory Operation Added to Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.6 <a href="#N11216">Indicating Incompatibility by Changing the Endpoint URI</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.7 <a href="#N1121F">Indicating Incompatibility by Changing the SOAP Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5.8 <a href="#N11236">Indicating Incompatibility by Changing the Element Content</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#adv-service-references">Describing Web Service Messages That Refer to Other Web Services</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#reservationDetails">The Reservation Details Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#reservationList">The Reservation List Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.3 <a href="#reservationDetails_HTTP">Reservation Details Web Service Using HTTP Transfer</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.4 <a href="#reservationList_HTTP_GET">Reservation List Web Service Using HTTP GET</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#adv-multiple-docs-describing-same-service">Multiple Interfaces for the Same Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.5 <a href="#adv-rdf-mapping">Mapping to RDF and Semantic Web</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.5.1 <a href="#adv-rdf-rep-wsdl">RDF Representation of WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.6 <a href="#adv-notes-on-uris">Notes on URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.1 <a href="#adv-namespaces-and-schema-locations">XML Namespaces and Schema Locations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.2 <a href="#adv-relative-uris">Relative URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.6.3 <a href="#adv-generating-uris">Generating Temporary URIs</a><br>6. <a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendix</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="body">
  		
  		
***************
*** 164,168 ****
  			<div class="div3">
  <h4><a name="basics-greath-scenario"></a>2.1.1 Example Scenario: The GreatH Hotel Reservation Service</h4><p>Hotel GreatH (a fictional hotel)) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ul><li><p><em>CheckAvailability</em>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if not. If any input data is invalid, the service should return an error.  Thus, the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </li><li><p><em>MakeReservation</em>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></li></ul> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <em>CheckAvailability</em> operation.  </p><p>The next several sections proceed step-by-step through the process of developing a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial"></a><i><span>Example 2-1. </span>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
--- 164,168 ----
  			<div class="div3">
  <h4><a name="basics-greath-scenario"></a>2.1.1 Example Scenario: The GreatH Hotel Reservation Service</h4><p>Hotel GreatH (a fictional hotel)) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ul><li><p><em>CheckAvailability</em>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if not. If any input data is invalid, the service should return an error.  Thus, the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </li><li><p><em>MakeReservation</em>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></li></ul> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <em>CheckAvailability</em> operation.  </p><p>The next several sections proceed step-by-step through the process of developing a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial"></a><i><span>Example 2-1. </span>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
***************
*** 253,257 ****
  <div class="div3">
  <h4><a name="basics-getting-started"></a>2.1.2 Defining a WSDL 2.0 Target Namespace</h4><p>Before writing our WSDL 2.0 document, we need to decide on a <em>WSDL 2.0 target namespace</em> URI for it.  The WSDL 2.0 target namespace is analogous to an XML Schema target namespace. Interface, binding and service names that we define in our WSDL 2.0 document will be associated with the WSDL 2.0 target namespace, and thus will be distinguishable from similar names in a different WSDL 2.0 target namespace.  (This will become important if using WSDL 2.0's import or interface inheritance mechanisms.)  </p><p>The value of the  WSDL 2.0  target namespace must be an absolute URI.  Furthermore, it should be dereferenceable to a WSDL 2.0 document that describes the Web service that the WSDL 2.0 target namespace is used to describe.  For example, the GreatH owners should make the WSDL 2.0 document available from this URI.  (And if a WSDL 2.0 description is split into multiple documents, then the WSDL 2.0 target namespace should resolve to a master document that includes all the WSDL 2.0 documents needed for that service description.)  However, there is no absolute requirement for this URI to be dereferenceable, so a WSDL 2.0 processor must not depend on it being dereferenceable.  </p><p>This recommendation may sound circular, but bear in mind that the client might have obtained the WSDL 2.0 document from anywhere -- not necessarily an authoritative source.  But by dereferencing the WSDL 2.0 target namespace URI, a user  should be able to obtain an authoritative version.  Since GreatH will be the owner of the service, the WSDL 2.0 target namespace URI should refer to a location on  the GreatH Web site or otherwise within its control.</p><p>Once we have decided on a WSDL 2.0 target namespace URI, we can begin our WSDL 2.0 document as the following empty shell.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-empty-shell"></a><i><span>Example 2-2. </span>An Initial Empty WSDL 2.0 Document</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
--- 253,257 ----
  <div class="div3">
  <h4><a name="basics-getting-started"></a>2.1.2 Defining a WSDL 2.0 Target Namespace</h4><p>Before writing our WSDL 2.0 document, we need to decide on a <em>WSDL 2.0 target namespace</em> URI for it.  The WSDL 2.0 target namespace is analogous to an XML Schema target namespace. Interface, binding and service names that we define in our WSDL 2.0 document will be associated with the WSDL 2.0 target namespace, and thus will be distinguishable from similar names in a different WSDL 2.0 target namespace.  (This will become important if using WSDL 2.0's import or interface inheritance mechanisms.)  </p><p>The value of the  WSDL 2.0  target namespace must be an absolute URI.  Furthermore, it should be dereferenceable to a WSDL 2.0 document that describes the Web service that the WSDL 2.0 target namespace is used to describe.  For example, the GreatH owners should make the WSDL 2.0 document available from this URI.  (And if a WSDL 2.0 description is split into multiple documents, then the WSDL 2.0 target namespace should resolve to a master document that includes all the WSDL 2.0 documents needed for that service description.)  However, there is no absolute requirement for this URI to be dereferenceable, so a WSDL 2.0 processor must not depend on it being dereferenceable.  </p><p>This recommendation may sound circular, but bear in mind that the client might have obtained the WSDL 2.0 document from anywhere -- not necessarily an authoritative source.  But by dereferencing the WSDL 2.0 target namespace URI, a user  should be able to obtain an authoritative version.  Since GreatH will be the owner of the service, the WSDL 2.0 target namespace URI should refer to a location on  the GreatH Web site or otherwise within its control.</p><p>Once we have decided on a WSDL 2.0 target namespace URI, we can begin our WSDL 2.0 document as the following empty shell.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-empty-shell"></a><i><span>Example 2-2. </span>An Initial Empty WSDL 2.0 Document</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
***************
*** 274,278 ****
  <div class="div3">
  <h4><a name="basics-types"></a>2.1.3 Defining Message Types</h4><p>We know that the GreatH service will be sending and receiving messages, so a good starting point in describing the service is to define the message types that the service will use.  We'll use XML Schema to do so, because WSDL 2.0 processors are likely to support XML Schema at a minimum.  However, WSDL 2.0 does not prohibit the use of some other schema definition language.</p><p>WSDL 2.0 allows message types to be defined directly within the WSDL 2.0 document, inside the <code>types</code> element, which is a child of the <code>description</code> element.   (Later we'll see how we can provide the type definitions in a separate document, using XML Schema's <code>import</code> mechanism.)    The following schema defines <code>checkAvailability</code>, <code>checkAvailabilityResponse</code> and <code>invalidDataError</code> message types that we'll need.  </p><p>In WSDL 2.0, all normal and fault message types must be defined as single <em>elements</em> at the topmost level (though of course each element may have any amount of substructure inside it).  Thus, a message type must not directly consist of a sequence of elements or other complex type.  </p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial-types"></a><i><span>Example 2-3. </span>GreatH Message Types</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
--- 274,278 ----
  <div class="div3">
  <h4><a name="basics-types"></a>2.1.3 Defining Message Types</h4><p>We know that the GreatH service will be sending and receiving messages, so a good starting point in describing the service is to define the message types that the service will use.  We'll use XML Schema to do so, because WSDL 2.0 processors are likely to support XML Schema at a minimum.  However, WSDL 2.0 does not prohibit the use of some other schema definition language.</p><p>WSDL 2.0 allows message types to be defined directly within the WSDL 2.0 document, inside the <code>types</code> element, which is a child of the <code>description</code> element.   (Later we'll see how we can provide the type definitions in a separate document, using XML Schema's <code>import</code> mechanism.)    The following schema defines <code>checkAvailability</code>, <code>checkAvailabilityResponse</code> and <code>invalidDataError</code> message types that we'll need.  </p><p>In WSDL 2.0, all normal and fault message types must be defined as single <em>elements</em> at the topmost level (though of course each element may have any amount of substructure inside it).  Thus, a message type must not directly consist of a sequence of elements or other complex type.  </p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial-types"></a><i><span>Example 2-3. </span>GreatH Message Types</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
***************
*** 316,320 ****
  				
  				<p>For the GreatH service, we will (initially) define an interface containing a single operation, <code>opCheckAvailability</code>, using  the <code>checkAvailability</code> and <code>checkAvailabilityResponse</code> message types that we defined in the <code>types</code> section.   We'll use the <a href="wsdl20-adjuncts.html#in-out">in-out</a> pattern for this operation, because this is the most natural way to represent a simple request-response interaction.  We could have instead (for example) defined two separate operations using the <a href="wsdl20-adjuncts.html#in-out">in-only</a> and <a href="wsdl20-adjuncts.html#out-only">out-only</a> patterns (see <em>WSDL 2.0 Predefined Extensions</em> [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] section  2.2.1 <a href="wsdl20-adjuncts.html#in-only">In-Only</a> and section  2.2.5 <a href="wsdl20-adjuncts.html#out-only">Out-Only</a>), but that would just complicate matters for the client, because we would then have to separately indicate to the client developer that the two operations should be used together as a request-response pair.</p><p>In addition to the normal input and output messages, we also need to specify the fault message that we wish to use in the event of an error.  WSDL 2.0 permits fault messages to be declared within the <code>interface</code> element in order to facilitate reuse of faults across operations.   If a fault occurs, it terminates whatever message sequence was indicated by the message exchange pattern of the operation.  </p><p>Let's add these to our WSDL 2.0 document.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial-interface"></a><i><span>Example 2-4. </span>GreatH Interface Definition</i></p>
  					
  				<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
--- 316,320 ----
  				
  				<p>For the GreatH service, we will (initially) define an interface containing a single operation, <code>opCheckAvailability</code>, using  the <code>checkAvailability</code> and <code>checkAvailabilityResponse</code> message types that we defined in the <code>types</code> section.   We'll use the <a href="wsdl20-adjuncts.html#in-out">in-out</a> pattern for this operation, because this is the most natural way to represent a simple request-response interaction.  We could have instead (for example) defined two separate operations using the <a href="wsdl20-adjuncts.html#in-out">in-only</a> and <a href="wsdl20-adjuncts.html#out-only">out-only</a> patterns (see <em>WSDL 2.0 Predefined Extensions</em> [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] section  2.2.1 <a href="wsdl20-adjuncts.html#in-only">In-Only</a> and section  2.2.5 <a href="wsdl20-adjuncts.html#out-only">Out-Only</a>), but that would just complicate matters for the client, because we would then have to separately indicate to the client developer that the two operations should be used together as a request-response pair.</p><p>In addition to the normal input and output messages, we also need to specify the fault message that we wish to use in the event of an error.  WSDL 2.0 permits fault messages to be declared within the <code>interface</code> element in order to facilitate reuse of faults across operations.   If a fault occurs, it terminates whatever message sequence was indicated by the message exchange pattern of the operation.  </p><p>Let's add these to our WSDL 2.0 document.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial-interface"></a><i><span>Example 2-4. </span>GreatH Interface Definition</i></p>
  					
  				<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
***************
*** 387,390 ****
--- 387,391 ----
  				elements inside a
  				<code>binding</code>
+ 
  				element, as shown in the example below. However, in some
  				cases it is possible to use defaulting rules to supply
***************
*** 418,422 ****
  			</p>
  			<p>For the GreatH service, we will use SOAP 1.2 as our concrete message format and HTTP as our  underlying transmission protocol, as shown below. </p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial-binding"></a><i><span>Example 2-5. </span>GreatH Binding Definition</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
--- 419,423 ----
  			</p>
  			<p>For the GreatH service, we will use SOAP 1.2 as our concrete message format and HTTP as our  underlying transmission protocol, as shown below. </p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial-binding"></a><i><span>Example 2-5. </span>GreatH Binding Definition</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
***************
*** 473,477 ****
  <div class="div3">
  <h4><a name="basics-service"></a>2.1.6 Defining a Service</h4><p>Now that our binding has specified <em>how</em> messages will be transmitted, we are ready to specify <em>where</em> the service can be accessed, by use of the <code>service</code> element.  </p><p>A WSDL 2.0 <em>service</em> specifies a single interface that the service will support, and  a list of <em>endpoint</em> locations where that service can be accessed.  Each endpoint must also reference a previously defined binding to indicate what protocols and transmission formats are to be used at that endpoint.  A service is only permitted to have one interface.   (See  <a href="#adv-multiple-docs-describing-same-service"><b>5.4 Multiple Interfaces for the Same Service</b></a> for further discussion of this limitation.) </p><p>Here is a definition for our GreatH service.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial-service"></a><i><span>Example 2-6. </span>GreatH Service Definition</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
--- 474,478 ----
  <div class="div3">
  <h4><a name="basics-service"></a>2.1.6 Defining a Service</h4><p>Now that our binding has specified <em>how</em> messages will be transmitted, we are ready to specify <em>where</em> the service can be accessed, by use of the <code>service</code> element.  </p><p>A WSDL 2.0 <em>service</em> specifies a single interface that the service will support, and  a list of <em>endpoint</em> locations where that service can be accessed.  Each endpoint must also reference a previously defined binding to indicate what protocols and transmission formats are to be used at that endpoint.  A service is only permitted to have one interface.   (See  <a href="#adv-multiple-docs-describing-same-service"><b>5.4 Multiple Interfaces for the Same Service</b></a> for further discussion of this limitation.) </p><p>Here is a definition for our GreatH service.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial-service"></a><i><span>Example 2-6. </span>GreatH Service Definition</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
***************
*** 513,517 ****
  				<div class="div3">
  <h4><a name="basics-documentation"></a>2.1.7 Documenting the Service</h4><p>As we have seen, a WSDL 2.0 document is inherently only a <em>partial</em> description of a service.  Although it captures the basic mechanics of interacting with the service -- the message types, transmission protocols, service location, etc. -- in general, additional documentation will need to explain other application-level requirements for its use.  For example, such documentation should explain the purpose and use of the service, the meanings of all messages, constraints on their use, and the sequence in which operations should be invoked.</p><p>The <code>documentation</code> element allows the WSDL 2.0 author to include some human-readable documentation inside a WSDL 2.0 document.   It is also a convenient place to reference any additional external documentation that a client developer may need in order to use the service.   It can appear in a number of places in a WSDL 2.0 document (see <a href="#wsdl-infoset-diagram"><b>2.2.1 WSDL 2.0 Infoset</b></a>), though in this example we have only demonstrated its use at the beginning.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-initial-documentation"></a><i><span>Example 2-7. </span>Documenting the GreatH Service</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
--- 514,518 ----
  				<div class="div3">
  <h4><a name="basics-documentation"></a>2.1.7 Documenting the Service</h4><p>As we have seen, a WSDL 2.0 document is inherently only a <em>partial</em> description of a service.  Although it captures the basic mechanics of interacting with the service -- the message types, transmission protocols, service location, etc. -- in general, additional documentation will need to explain other application-level requirements for its use.  For example, such documentation should explain the purpose and use of the service, the meanings of all messages, constraints on their use, and the sequence in which operations should be invoked.</p><p>The <code>documentation</code> element allows the WSDL 2.0 author to include some human-readable documentation inside a WSDL 2.0 document.   It is also a convenient place to reference any additional external documentation that a client developer may need in order to use the service.   It can appear in a number of places in a WSDL 2.0 document (see <a href="#wsdl-infoset-diagram"><b>2.2.1 WSDL 2.0 Infoset</b></a>), though in this example we have only demonstrated its use at the beginning.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-initial-documentation"></a><i><span>Example 2-7. </span>Documenting the GreatH Service</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
***************
*** 547,551 ****
  <p>The following diagram gives an overview of  the XML Infoset for a WSDL 2.0 document.
  
! <div class="figure" style="text-align: center"><br><img src="images/WSDL20InfosetModel.png" alt="WSDL 2.0 Infoset Diagram"><p style="text-align:left"><i><span>Figure 2-1. </span>WSDL 2.0 Infoset Diagram</i></p><br></div>
  
  </p>
--- 548,552 ----
  <p>The following diagram gives an overview of  the XML Infoset for a WSDL 2.0 document.
  
! <div style="text-align: center" class="figure"><br><img src="images/WSDL20InfosetModel.png" alt="WSDL 2.0 Infoset Diagram"><p style="text-align:left"><i><span>Figure 2-1. </span>WSDL 2.0 Infoset Diagram</i></p><br></div>
  
  </p>
***************
*** 652,656 ****
  <p>The WSDL 2.0 Infoset model above illustrates the required structure of a WSDL 2.0 document, using the XML Infoset.  However, the WSDL 2.0 language also imposes many semantic constraints over and above structural conformance to this XML Infoset. In order to precisely describe these constraints, and as  an aid in precisely defining the meaning of each WSDL 2.0 document, the WSDL 2.0 specification defines a <em>component model</em>  as an additional layer of abstraction above the XML Infoset.  Constraints and meaning are defined in terms of this component model, and the definition of each component includes a mapping that specifies how values in the component model are derived from corresponding items in the XML Infoset.   The following diagram gives an overview of  the WSDL 2.0 components and their containment hierarchy.
  
!  <div class="figure" style="text-align: center"><br><img src="images/WSDL20Components.png" alt="WSDL 2.0 Components Containment hierarchy"><p style="text-align:left"><i><span>Figure 2-2. </span>WSDL 2.0 Components Containment hierarchy</i></p><br></div></p>
  
  
--- 653,657 ----
  <p>The WSDL 2.0 Infoset model above illustrates the required structure of a WSDL 2.0 document, using the XML Infoset.  However, the WSDL 2.0 language also imposes many semantic constraints over and above structural conformance to this XML Infoset. In order to precisely describe these constraints, and as  an aid in precisely defining the meaning of each WSDL 2.0 document, the WSDL 2.0 specification defines a <em>component model</em>  as an additional layer of abstraction above the XML Infoset.  Constraints and meaning are defined in terms of this component model, and the definition of each component includes a mapping that specifies how values in the component model are derived from corresponding items in the XML Infoset.   The following diagram gives an overview of  the WSDL 2.0 components and their containment hierarchy.
  
!  <div style="text-align: center" class="figure"><br><img src="images/WSDL20Components.png" alt="WSDL 2.0 Components Containment hierarchy"><p style="text-align:left"><i><span>Figure 2-2. </span>WSDL 2.0 Components Containment hierarchy</i></p><br></div></p>
  
  
***************
*** 796,800 ****
  				<p>Here is an example of importing a schema. Assuming the message types in <a href="#example-initial-types">Example 2-3</a> are defined in a separate schema file named "http://greath.example.com/2004/schemas/resSvc.xsd" with a target namespace "http://greath.example.com/2004/schemas/resSvc",  the schema definition can then be imported into the WSDL 2.0 as follows:  </p>
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-schema-import"></a><i><span>Example 2-8. </span>Example of Importing Message Definitions</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
--- 797,801 ----
  				<p>Here is an example of importing a schema. Assuming the message types in <a href="#example-initial-types">Example 2-3</a> are defined in a separate schema file named "http://greath.example.com/2004/schemas/resSvc.xsd" with a target namespace "http://greath.example.com/2004/schemas/resSvc",  the schema definition can then be imported into the WSDL 2.0 as follows:  </p>
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-schema-import"></a><i><span>Example 2-8. </span>Example of Importing Message Definitions</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt; 
  &lt;description 
***************
*** 992,996 ****
  
  <div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-faults"></a><i><span>Example 2-9. </span>Interface Inheritance</i></p>
  				<div class="exampleInner"><pre>
  					
--- 993,997 ----
  
  <div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-faults"></a><i><span>Example 2-9. </span>Interface Inheritance</i></p>
  				<div class="exampleInner"><pre>
  					
***************
*** 1104,1111 ****
  				
  				</div><div class="div4">
! <h5><a name="N67903"></a>2.4.4.2 Operation Message References</h5><p>An <code>operation</code> will also have <code>input</code>, <code>output</code>,<code>infault</code>, and/or <code>outfault</code> element children that specify the ordinary and fault message types to be used by that operation.  The MEP specified by the <code>pattern</code> attribute determines which of these  elements should be included, since each MEP has placeholders for the message types involved in its pattern.     </p><p>Since operations were already discussed in <a href="#basics-interface"><b>2.1.4 Defining an Interface</b></a>, this section will merely comment on additional capabilities that were not previously explained.</p>
  				<div class="div5">
  					
! <h6><a name="N67932"></a>2.4.4.2.1 The messageLabel Attribute</h6>
  					<p>
  						The
--- 1105,1112 ----
  				
  				</div><div class="div4">
! <h5><a name="N1093F"></a>2.4.4.2 Operation Message References</h5><p>An <code>operation</code> will also have <code>input</code>, <code>output</code>,<code>infault</code>, and/or <code>outfault</code> element children that specify the ordinary and fault message types to be used by that operation.  The MEP specified by the <code>pattern</code> attribute determines which of these  elements should be included, since each MEP has placeholders for the message types involved in its pattern.     </p><p>Since operations were already discussed in <a href="#basics-interface"><b>2.1.4 Defining an Interface</b></a>, this section will merely comment on additional capabilities that were not previously explained.</p>
  				<div class="div5">
  					
! <h6><a name="N1095C"></a>2.4.4.2.1 The messageLabel Attribute</h6>
  					<p>
  						The
***************
*** 1127,1131 ****
  				<div class="div5">
  					
! <h6><a name="N67956"></a>2.4.4.2.2 The element Attribute</h6>
  					<p>
  						The
--- 1128,1132 ----
  				<div class="div5">
  					
! <h6><a name="N10974"></a>2.4.4.2.2 The element Attribute</h6>
  					<p>
  						The
***************
*** 1188,1192 ****
  				</div>
  				<div class="div5">
! <h6><a name="N68037"></a>2.4.4.2.3 Multiple infault or outfault Elements</h6><p>When <code>infault</code> and/or <code>outfault</code> occur multiple times within an <code>operation</code>, they define alternative fault messages. </p></div></div>
  			
  			
--- 1189,1193 ----
  				</div>
  				<div class="div5">
! <h6><a name="N109C5"></a>2.4.4.2.3 Multiple infault or outfault Elements</h6><p>When <code>infault</code> and/or <code>outfault</code> occur multiple times within an <code>operation</code>, they define alternative fault messages. </p></div></div>
  			
  			
***************
*** 1196,1199 ****
--- 1197,1201 ----
  				<p>WSDL 2.0 message exchange patterns (MEPs) are used to define the sequence and cardinality of the abstract messages in  an operation. By design, WSDL 2.0 MEPs are abstract. First of all, they abstract out specific message types. MEPs identify placeholders for messages, and placeholders are associated with specific message types when an operation is defined, which includes specifying which MEP to use for that operation. Secondly, unless explicitly stated otherwise, MEPs also abstract out binding-specific information like timing between messages, whether the pattern is synchronous or asynchronous, and whether the messages are sent over a single or multiple channels.</p>
  				<p>It's worth pointing out that WSDL 2.0 MEPs do not exhaustively describe the set of messages that may be 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 
+ 
  MEP. For instance, even though an MEP may define a single message sent 
  from a service to one other node, a service defined by that MEP may multicast that message to 
***************
*** 1207,1211 ****
  		
  <div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-outbound-operation"></a><i><span>Example 2-10. </span>Use of outbound MEPs</i></p>
  				<div class="exampleInner"><pre>
  					
--- 1209,1213 ----
  		
  <div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-outbound-operation"></a><i><span>Example 2-10. </span>Use of outbound MEPs</i></p>
  				<div class="exampleInner"><pre>
  					
***************
*** 1301,1305 ****
  					
  				<p>The WSDL 2.0 SOAP Binding Extension (see WSDL 2.0 Part 2 [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>])   was primarily designed to support the features of SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].  However, for backwards compatibility, it also provides some support for SOAP 1.1 [<cite><a href="#SOAP11">SOAP 1.1</a></cite>].     </p><p>An example using the WSDL 2.0 SOAP binding extension was already presented in <a href="#basics-binding"><b>2.1.5 Defining a Binding</b></a>, but some additional points are worth mentioning:<ul><li><p>Because the same binding extension is used for both SOAP 1.2 and SOAP 1.1, a <code>wsoap:version</code> attribute is provided to allow you to indicate which version of SOAP you want.  If this attribute is not specified, it defaults to SOAP 1.2.</p></li><li><p>The WSDL 2.0 SOAP binding extension defines a set of default rules, so that bindings can be specified at the interface level or at the operation level (or both), with the operation level taking precedence.   However, it does not define default binding rules for faults. Thus, if a given interface defines any faults, then corresponding binding information must be explicitly provided for each such fault.</p></li><li><p>If HTTP is used as the underlying protocol, then the binding can (and should) control whether each operation will  use HTTP GET or POST.  (See    <a href="#adv-get-vs-post"><b>2.5.7 HTTP GET Versus POST: Which to Use?</b></a>.)</p></li></ul></p><p>Here is an example that illustrates both a SOAP 1.2 binding (as seen before) and a SOAP 1.1 binding.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-binding-soap"></a><i><span>Example 2-11. </span>SOAP 1.2 and SOAP 1.1 Bindings</i></p>
  
  <div class="exampleInner"><pre>
--- 1303,1307 ----
  					
  				<p>The WSDL 2.0 SOAP Binding Extension (see WSDL 2.0 Part 2 [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>])   was primarily designed to support the features of SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].  However, for backwards compatibility, it also provides some support for SOAP 1.1 [<cite><a href="#SOAP11">SOAP 1.1</a></cite>].     </p><p>An example using the WSDL 2.0 SOAP binding extension was already presented in <a href="#basics-binding"><b>2.1.5 Defining a Binding</b></a>, but some additional points are worth mentioning:<ul><li><p>Because the same binding extension is used for both SOAP 1.2 and SOAP 1.1, a <code>wsoap:version</code> attribute is provided to allow you to indicate which version of SOAP you want.  If this attribute is not specified, it defaults to SOAP 1.2.</p></li><li><p>The WSDL 2.0 SOAP binding extension defines a set of default rules, so that bindings can be specified at the interface level or at the operation level (or both), with the operation level taking precedence.   However, it does not define default binding rules for faults. Thus, if a given interface defines any faults, then corresponding binding information must be explicitly provided for each such fault.</p></li><li><p>If HTTP is used as the underlying protocol, then the binding can (and should) control whether each operation will  use HTTP GET or POST.  (See    <a href="#adv-get-vs-post"><b>2.5.7 HTTP GET Versus POST: Which to Use?</b></a>.)</p></li></ul></p><p>Here is an example that illustrates both a SOAP 1.2 binding (as seen before) and a SOAP 1.1 binding.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-binding-soap"></a><i><span>Example 2-11. </span>SOAP 1.2 and SOAP 1.1 Bindings</i></p>
  
  <div class="exampleInner"><pre>
***************
*** 1380,1384 ****
  				<p>In addition to the WSDL 2.0 SOAP binding extension described above, WSDL 2.0 Part 2  [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines a binding extension for HTTP 1.1 [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>] and HTTPS [<cite><a href="#RFC2818">IETF RFC 2818</a></cite>], so that these protocols can be used natively to send and receive messages, without first encoding them in SOAP.</p><p>The HTTP binding extension provides many features to control:<ul><li><p> Which HTTP operation will be used.  (GET, PUT, POST, DELETE, and other HTTP operations are supported.)</p></li><li><p>Input, output and fault serialization</p></li><li><p>Transfer codings</p></li><li><p>Authentication requirements</p></li><li><p>Cookies</p></li><li><p>HTTP over TLS (https)</p></li></ul></p><p>As with the WSDL 2.0 SOAP binding extension, the HTTP binding extension also provides defaulting rules to permit binding information to be specified at the interface level and used by default for each operation in the affected interface, however, defaulting rules are not provided for binding faults.</p><p>Here is an example of using the HTTP binding extension to check hotel room 
  availability at GreatH.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-bindings-http"></a><i><span>Example 2-12. </span>HTTP Binding Extension</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
--- 1382,1386 ----
  				<p>In addition to the WSDL 2.0 SOAP binding extension described above, WSDL 2.0 Part 2  [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines a binding extension for HTTP 1.1 [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>] and HTTPS [<cite><a href="#RFC2818">IETF RFC 2818</a></cite>], so that these protocols can be used natively to send and receive messages, without first encoding them in SOAP.</p><p>The HTTP binding extension provides many features to control:<ul><li><p> Which HTTP operation will be used.  (GET, PUT, POST, DELETE, and other HTTP operations are supported.)</p></li><li><p>Input, output and fault serialization</p></li><li><p>Transfer codings</p></li><li><p>Authentication requirements</p></li><li><p>Cookies</p></li><li><p>HTTP over TLS (https)</p></li></ul></p><p>As with the WSDL 2.0 SOAP binding extension, the HTTP binding extension also provides defaulting rules to permit binding information to be specified at the interface level and used by default for each operation in the affected interface, however, defaulting rules are not provided for binding faults.</p><p>Here is an example of using the HTTP binding extension to check hotel room 
  availability at GreatH.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-bindings-http"></a><i><span>Example 2-12. </span>HTTP Binding Extension</i></p>
  					<div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="utf-8" ?&gt; 
***************
*** 1410,1414 ****
  				</div>
  			<div class="div4">
! <h5><a name="N68496"></a>2.5.6.1 Explanation of
  			Example</h5>
  			
--- 1412,1416 ----
  				</div>
  			<div class="div4">
! <h5><a name="N10B90"></a>2.5.6.1 Explanation of
  			Example</h5>
  			
***************
*** 1434,1438 ****
  
  <p>Here is an alternate example that appends "/" to the type name in order to serialize the remaining instance data into the message body:</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-bindings-http-path-subsset"></a><i><span>Example 2-13. </span>Serializing a Subset of Types in the Path</i></p>
  					<div class="exampleInner"><pre>
  
--- 1436,1440 ----
  
  <p>Here is an alternate example that appends "/" to the type name in order to serialize the remaining instance data into the message body:</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-bindings-http-path-subsset"></a><i><span>Example 2-13. </span>Serializing a Subset of Types in the Path</i></p>
  					<div class="exampleInner"><pre>
  
***************
*** 1461,1465 ****
  
  <div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-binding-safety"></a><i><span>Example 2-14. </span>Safety and HTTP Binding</i></p>
  
  <div class="exampleInner"><pre>
--- 1463,1467 ----
  
  <div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-binding-safety"></a><i><span>Example 2-14. </span>Safety and HTTP Binding</i></p>
  
  <div class="exampleInner"><pre>
***************
*** 1518,1522 ****
  				
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="credit-card-faults"></a><i><span>Example 3-1. </span>Standard Credit Card Validation Faults (credit-card-faults.wsdl)</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 1520,1524 ----
  				
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="credit-card-faults"></a><i><span>Example 3-1. </span>Standard Credit Card Validation Faults (credit-card-faults.wsdl)</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 1569,1573 ****
  			
  			<div class="exampleOuter">
! 				<p style="text-align: left" class="exampleHead"><a name="use-credit-card-faults"></a><i><span>Example 3-2. </span>Using the Standard Credit Card Validation Faults (use-credit-card-faults.wsdl)</i></p>
  				<div class="exampleInner"><pre>&lt;?xml version="1.0"?&gt;
  &lt;description
--- 1571,1575 ----
  			
  			<div class="exampleOuter">
! 				<p class="exampleHead" style="text-align: left"><a name="use-credit-card-faults"></a><i><span>Example 3-2. </span>Using the Standard Credit Card Validation Faults (use-credit-card-faults.wsdl)</i></p>
  				<div class="exampleInner"><pre>&lt;?xml version="1.0"?&gt;
  &lt;description
***************
*** 1656,1660 ****
  				<div class="div3">
  					
! <h4><a name="N68832"></a>3.2.1 Schemas in Imported Documents</h4>
  					<p>
  						In this example, we consider some GreatH Hotel
--- 1658,1662 ----
  				<div class="div3">
  					
! <h4><a name="N10CE0"></a>3.2.1 Schemas in Imported Documents</h4>
  					<p>
  						In this example, we consider some GreatH Hotel
***************
*** 1693,1697 ****
  
  					<div class="exampleOuter">
! 						<p style="text-align: left" class="exampleHead"><a name="retrieveDetails.wsdl"></a><i><span>Example 3-3. </span>
  							The Retrieve Reservation Details Web
  							Service: retrieveDetails.wsdl
--- 1695,1699 ----
  
  					<div class="exampleOuter">
! 						<p class="exampleHead" style="text-align: left"><a name="retrieveDetails.wsdl"></a><i><span>Example 3-3. </span>
  							The Retrieve Reservation Details Web
  							Service: retrieveDetails.wsdl
***************
*** 1820,1824 ****
  
  					<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="updateDetails.wsdl"></a><i><span>Example 3-4. </span>The Update Reservation Details Web Service: updateDetails.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 1822,1826 ----
  
  					<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="updateDetails.wsdl"></a><i><span>Example 3-4. </span>The Update Reservation Details Web Service: updateDetails.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 1863,1867 ****
  				<div class="div3">
  					
! <h4><a name="N68971"></a>3.2.2 Multiple Inline Schemas in One Document</h4>
  					<p>
  						A WSDL 2.0 document may define multiple inline
--- 1865,1869 ----
  				<div class="div3">
  					
! <h4><a name="N10D6B"></a>3.2.2 Multiple Inline Schemas in One Document</h4>
  					<p>
  						A WSDL 2.0 document may define multiple inline
***************
*** 1919,1923 ****
  
  					<div class="exampleOuter">
! 						<p style="text-align: left" class="exampleHead"><a name="retrieveItems.wsdl"></a><i><span>Example 3-5. </span>
  							Multiple Inline Schemas: retrieveItems.wsdl
  						</i></p>
--- 1921,1925 ----
  
  					<div class="exampleOuter">
! 						<p class="exampleHead" style="text-align: left"><a name="retrieveItems.wsdl"></a><i><span>Example 3-5. </span>
  							Multiple Inline Schemas: retrieveItems.wsdl
  						</i></p>
***************
*** 1997,2001 ****
  the <code>schema</code> element. The simplest way to accomplish this is to use the <code>id</code> attribute, however XPointer (see [<cite><a href="#XPTR">XPointer Framework</a></cite>]) can also be used.
  </p><div class="div4">
! <h5><a name="N69067"></a>3.2.3.1 Using the id Attribute to Identify Inline
  						Schemas</h5><p>
  						<a href="#schemaIds.wsdl">Example 3-6</a>
--- 1999,2003 ----
  the <code>schema</code> element. The simplest way to accomplish this is to use the <code>id</code> attribute, however XPointer (see [<cite><a href="#XPTR">XPointer Framework</a></cite>]) can also be used.
  </p><div class="div4">
! <h5><a name="N10DCB"></a>3.2.3.1 Using the id Attribute to Identify Inline
  						Schemas</h5><p>
  						<a href="#schemaIds.wsdl">Example 3-6</a>
***************
*** 2014,2018 ****
  						attribute, i.e. <code>#items</code>.
  					</p>
! <div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="schemaIds.wsdl"></a><i><span>Example 3-6. </span>Using Ids in Inline Schemas: schemaIds.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 2016,2020 ----
  						attribute, i.e. <code>#items</code>.
  					</p>
! <div class="exampleOuter"><p class="exampleHead" style="text-align: left"><a name="schemaIds.wsdl"></a><i><span>Example 3-6. </span>Using Ids in Inline Schemas: schemaIds.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 2097,2101 ****
  <h3><a name="adv-FP"></a>4.2 Features and Properties</h3>
  
! 							<table border="1" summary="Editorial note: KevinL"><tr><td align="left" valign="top" width="50%"><b>Editorial note: KevinL</b></td><td align="right" valign="top" width="50%">20050519</td></tr><tr><td colspan="2" align="left" valign="top">
  						The section is subject to change. Pending on the resolution of the minority opinions filed about Feature and Property.
  					</td></tr></table>
--- 2099,2103 ----
  <h3><a name="adv-FP"></a>4.2 Features and Properties</h3>
  
! 							<table border="1" summary="Editorial note: KevinL"><tr><td width="50%" valign="top" align="left"><b>Editorial note: KevinL</b></td><td width="50%" valign="top" align="right">20050519</td></tr><tr><td valign="top" align="left" colspan="2">
  						The section is subject to change. Pending on the resolution of the minority opinions filed about Feature and Property.
  					</td></tr></table>
***************
*** 2104,2108 ****
  			<div class="div3">
  <h4><a name="adv-FP-soap-modules"></a>4.2.1 SOAP Modules</h4><p>The first step GreatH takes is to require the usage of the SOAP module in their normal SOAP/HTTP endpoint, which looks like this:</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-fp-requiring-soap-module"></a><i><span>Example 4-1. </span>Requiring a SOAP Module in an Endpoint</i></p>
  					<div class="exampleInner"><pre>
  
--- 2106,2110 ----
  			<div class="div3">
  <h4><a name="adv-FP-soap-modules"></a>4.2.1 SOAP Modules</h4><p>The first step GreatH takes is to require the usage of the SOAP module in their normal SOAP/HTTP endpoint, which looks like this:</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-fp-requiring-soap-module"></a><i><span>Example 4-1. </span>Requiring a SOAP Module in an Endpoint</i></p>
  					<div class="exampleInner"><pre>
  
***************
*** 2125,2129 ****
  </p><p>If the "required" attribute was not present, or if it was set to "<code>false</code>", then the <code>&lt;wsoap:module&gt;</code> syntax would indicate optional the availability of the referenced module, rather than a requirement to engage it, as explained in <a href="#adv-optional-versus-required"><b>4.1.1 Optional Versus Required Extensions</b></a>.</p></div><div class="div3">
  <h4><a name="adv-FP-abstract-features"></a>4.2.2 Abstract Features</h4><p>Since GreatH began the web service improvements, they have been talking to several travel agents.  The possibility of making their simple hotel interface an industry standard amongst a consortium of hotels has come up, and as such they would like to enable specifying the requirement for the "makeReservation" operation to be secure at the interface level &ndash; in other words indicating that the operation must be secure, but without specifying exactly how that should concretely be achieved (to enable maximal reuse of the interface).  The next example uses the WSDL 2.0 Feature element to indicate this.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-fp-declaring-abstract-feature"></a><i><span>Example 4-2. </span>Declaring an Abstract Feature Requirement</i></p>
  					<div class="exampleInner"><pre>
  . . .
--- 2127,2131 ----
  </p><p>If the "required" attribute was not present, or if it was set to "<code>false</code>", then the <code>&lt;wsoap:module&gt;</code> syntax would indicate optional the availability of the referenced module, rather than a requirement to engage it, as explained in <a href="#adv-optional-versus-required"><b>4.1.1 Optional Versus Required Extensions</b></a>.</p></div><div class="div3">
  <h4><a name="adv-FP-abstract-features"></a>4.2.2 Abstract Features</h4><p>Since GreatH began the web service improvements, they have been talking to several travel agents.  The possibility of making their simple hotel interface an industry standard amongst a consortium of hotels has come up, and as such they would like to enable specifying the requirement for the "makeReservation" operation to be secure at the interface level &ndash; in other words indicating that the operation must be secure, but without specifying exactly how that should concretely be achieved (to enable maximal reuse of the interface).  The next example uses the WSDL 2.0 Feature element to indicate this.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-fp-declaring-abstract-feature"></a><i><span>Example 4-2. </span>Declaring an Abstract Feature Requirement</i></p>
  					<div class="exampleInner"><pre>
  . . .
***************
*** 2137,2141 ****
  . . .</pre></div>
  				</div><p>This declaration indicates that understanding of, and compliance with, the specified security feature is required for all uses of the "makeReservation" operation.  The security feature is <em>abstract</em>, which means that although it defines semantics and a level of detail about its general operation, it expects a concrete component (like a SOAP module or binding) to actually realize the functionality.</p><p>By definition, if you understand a SOAP module, you understand which (if any) abstract features it implements.  Therefore, since the security module in this example is defined as an implementation of the abstract security feature, we know that the use of this module satisfies the requirement to implement the feature.  Therefore users of the HTTP endpoint shown above (with the required SOAP module) will be able to make use of it.  GreatH also defines a new endpoint:</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-fp-soap-over-shttp"></a><i><span>Example 4-3. </span>A SOAP Binding Over a Secure HTTP Protocol</i></p>
  					<div class="exampleInner"><pre>
  . . .
--- 2139,2143 ----
  . . .</pre></div>
  				</div><p>This declaration indicates that understanding of, and compliance with, the specified security feature is required for all uses of the "makeReservation" operation.  The security feature is <em>abstract</em>, which means that although it defines semantics and a level of detail about its general operation, it expects a concrete component (like a SOAP module or binding) to actually realize the functionality.</p><p>By definition, if you understand a SOAP module, you understand which (if any) abstract features it implements.  Therefore, since the security module in this example is defined as an implementation of the abstract security feature, we know that the use of this module satisfies the requirement to implement the feature.  Therefore users of the HTTP endpoint shown above (with the required SOAP module) will be able to make use of it.  GreatH also defines a new endpoint:</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-fp-soap-over-shttp"></a><i><span>Example 4-3. </span>A SOAP Binding Over a Secure HTTP Protocol</i></p>
  					<div class="exampleInner"><pre>
  . . .
***************
*** 2156,2160 ****
  				</div><p>The user will have a choice as to which of the endpoints, and therefore which binding, is to be used, but they both satisfy the abstract feature requirement specified in the interface.</p><p>Note that it is not necessary to declare the abstract feature in order to use/require the SOAP module, or in order to use/require the secure binding.  Abstract feature declarations serve purely to indicate requirements which must be fulfilled by more concrete components such as modules or bindings.  In other words, the abstract feature declaration allows components such as interfaces to be reused without caring exactly which SOAP modules or bindings satisfy the feature.</p></div><div class="div3">
  <h4><a name="adv-fp-properties"></a>4.2.3 Properties</h4><p>So far we've discussed how to indicate the availability or the "requiredness" of features and modules.  Often it is not enough to indicate that a particular extension is available/required: you also need some way to control or parameterize aspects of its behavior.  This is achieved by the use of WSDL 2.0 <em>properties</em>.  Each feature, SOAP module, or SOAP binding may express a variety of <em>properties</em> in its specification.  These properties are very much like variables in a programming language.  If GreatH would like to indicate that the <code>securityLevel</code> property should be 5 for the "makeReservation" operation, it would look like this:</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-fp-def-prop"></a><i><span>Example 4-4. </span>Defining a Property</i></p>
  					<div class="exampleInner"><pre>
  . . .
--- 2158,2162 ----
  				</div><p>The user will have a choice as to which of the endpoints, and therefore which binding, is to be used, but they both satisfy the abstract feature requirement specified in the interface.</p><p>Note that it is not necessary to declare the abstract feature in order to use/require the SOAP module, or in order to use/require the secure binding.  Abstract feature declarations serve purely to indicate requirements which must be fulfilled by more concrete components such as modules or bindings.  In other words, the abstract feature declaration allows components such as interfaces to be reused without caring exactly which SOAP modules or bindings satisfy the feature.</p></div><div class="div3">
  <h4><a name="adv-fp-properties"></a>4.2.3 Properties</h4><p>So far we've discussed how to indicate the availability or the "requiredness" of features and modules.  Often it is not enough to indicate that a particular extension is available/required: you also need some way to control or parameterize aspects of its behavior.  This is achieved by the use of WSDL 2.0 <em>properties</em>.  Each feature, SOAP module, or SOAP binding may express a variety of <em>properties</em> in its specification.  These properties are very much like variables in a programming language.  If GreatH would like to indicate that the <code>securityLevel</code> property should be 5 for the "makeReservation" operation, it would look like this:</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-fp-def-prop"></a><i><span>Example 4-4. </span>Defining a Property</i></p>
  					<div class="exampleInner"><pre>
  . . .
***************
*** 2171,2175 ****
  				</div><p>The <code>property</code> element specifies which property is to be set.  By setting the <code>value</code> element, a toolkit processing this WSDL 2.0 document is informed that the securityLevel property must be set to 5.   The particular meanings of any such values are up to the implementations of the modules/bindings that use them.  The <code>property</code> element can be placed at many different levels in a WSDL 2.0 document (see "Property Composition Model" section in WSDL 2.0 Part 1 [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).
  </p><p>It is also possible to provide a <em>constraint</em> on the value space for a given property.  This allows the author of the WSDL 2.0 document to indicate that several valid values for the property are possible for a given scope, limiting the value space already described in the specification that defined the property.  Let's extend our  example to make this clearer.</p><p>The security feature specification defines securityLevel as an integer with values between 1 and 10, each of which indicates, according to the spec, a progressively higher level of security.  The GreatH service authors, having read the relevant specifications, have decided that any security level between 3 and 7 will be supported by their infrastructure.  Levels less than 3 are deemed unsafe for GreatH's purposes, and levels greater than 7 require too much in the way of resources to make it worthwhile.  We can express this in WSDL 2.0 as follows:</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-fp-def-prop-constraints"></a><i><span>Example 4-5. </span>Defining Property Constraints</i></p>
  					<div class="exampleInner"><pre>
  . . .
--- 2173,2177 ----
  				</div><p>The <code>property</code> element specifies which property is to be set.  By setting the <code>value</code> element, a toolkit processing this WSDL 2.0 document is informed that the securityLevel property must be set to 5.   The particular meanings of any such values are up to the implementations of the modules/bindings that use them.  The <code>property</code> element can be placed at many different levels in a WSDL 2.0 document (see "Property Composition Model" section in WSDL 2.0 Part 1 [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).
  </p><p>It is also possible to provide a <em>constraint</em> on the value space for a given property.  This allows the author of the WSDL 2.0 document to indicate that several valid values for the property are possible for a given scope, limiting the value space already described in the specification that defined the property.  Let's extend our  example to make this clearer.</p><p>The security feature specification defines securityLevel as an integer with values between 1 and 10, each of which indicates, according to the spec, a progressively higher level of security.  The GreatH service authors, having read the relevant specifications, have decided that any security level between 3 and 7 will be supported by their infrastructure.  Levels less than 3 are deemed unsafe for GreatH's purposes, and levels greater than 7 require too much in the way of resources to make it worthwhile.  We can express this in WSDL 2.0 as follows:</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-fp-def-prop-constraints"></a><i><span>Example 4-5. </span>Defining Property Constraints</i></p>
  					<div class="exampleInner"><pre>
  . . .
***************
*** 2225,2229 ****
  
  <div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="weather-not-initial"></a><i><span>Example 4-6. </span>Weather Notification Service (Initial)</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 2227,2231 ----
  
  <div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="weather-not-initial"></a><i><span>Example 4-6. </span>Weather Notification Service (Initial)</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 2334,2338 ****
  
  <div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="weather-not-final"></a><i><span>Example 4-7. </span>Weather Notification Service (Revised)</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 2336,2340 ----
  
  <div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="weather-not-final"></a><i><span>Example 4-7. </span>Weather Notification Service (Revised)</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 2384,2388 ****
  signature. This example is a modified version of the GreatH reservation
  service.  In particular, the <code>interface</code> and <code>types</code> sections have been modified to specify and conform to the RPC Style.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-rpc-style"></a><i><span>Example 4-8. </span>Specifying RPC Style </i></p>
  
  <div class="exampleInner"><pre>. . .
--- 2386,2390 ----
  signature. This example is a modified version of the GreatH reservation
  service.  In particular, the <code>interface</code> and <code>types</code> sections have been modified to specify and conform to the RPC Style.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-rpc-style"></a><i><span>Example 4-8. </span>Specifying RPC Style </i></p>
  
  <div class="exampleInner"><pre>. . .
***************
*** 2443,2447 ****
  for mapping simple types to Java types and
  designated inout and output parameters by using Holder classes.</p><div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-rpc-style-java-sig"></a><i><span>Example 4-9. </span>Sample Java(TM) Signature for   RPC Style</i></p>
  
  <div class="exampleInner"><pre>public interface reservationInterface extends Remote{
--- 2445,2449 ----
  for mapping simple types to Java types and
  designated inout and output parameters by using Holder classes.</p><div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-rpc-style-java-sig"></a><i><span>Example 4-9. </span>Sample Java(TM) Signature for   RPC Style</i></p>
  
  <div class="exampleInner"><pre>public interface reservationInterface extends Remote{
***************
*** 2469,2473 ****
  
   				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-MTOM-schema"></a><i><span>Example 4-10. </span>XML Schema with Optimizable Elements </i></p>
  
  <div class="exampleInner"><pre>. . .
--- 2471,2475 ----
  
   				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-MTOM-schema"></a><i><span>Example 4-10. </span>XML Schema with Optimizable Elements </i></p>
  
  <div class="exampleInner"><pre>. . .
***************
*** 2514,2518 ****
  
   				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-MTOM-soap-message"></a><i><span>Example 4-11. </span>Non-optimized SOAP Message with Embedded Binary Data </i></p>
  
  <div class="exampleInner"><pre>
--- 2516,2520 ----
  
   				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-MTOM-soap-message"></a><i><span>Example 4-11. </span>Non-optimized SOAP Message with Embedded Binary Data </i></p>
  
  <div class="exampleInner"><pre>
***************
*** 2539,2543 ****
   
   				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example-MTOM-soap-binding"></a><i><span>Example 4-12. </span>Specifying MTOM in a WSDL 2.0 Binding</i></p>
  
  <div class="exampleInner"><pre>
--- 2541,2545 ----
   
   				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example-MTOM-soap-binding"></a><i><span>Example 4-12. </span>Specifying MTOM in a WSDL 2.0 Binding</i></p>
  
  <div class="exampleInner"><pre>
***************
*** 2674,2678 ****
  for schema versioning as a part of the Schema 1.1 activity.  See XML Schema Versioning Use Cases [<cite><a href="#xsd-versioning">XML Schema: Versioning Use-Cases</a></cite>].</p></li><li><p>The <a href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</a> is  
  examining how vocabularies may evolve.  See  [<cite><a href="#sw-vocabulary">SW VocabManagementNote</a></cite>]</p></li></ul>
! <table border="1" summary="Editorial note: PaulD"><tr><td align="left" valign="top" width="50%"><b>Editorial note: PaulD</b></td><td align="right" valign="top" width="50%">20050706</td></tr><tr><td colspan="2" align="left" valign="top">This section may be subject to change dependent upon the outcome of the WSDL Last Call Issue LC124, which discusses support compatible evolution of messages described using XML Schema 1.0.</td></tr></table>
  
  <p>While incomplete, these activities all agree in one important 
--- 2676,2680 ----
  for schema versioning as a part of the Schema 1.1 activity.  See XML Schema Versioning Use Cases [<cite><a href="#xsd-versioning">XML Schema: Versioning Use-Cases</a></cite>].</p></li><li><p>The <a href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</a> is  
  examining how vocabularies may evolve.  See  [<cite><a href="#sw-vocabulary">SW VocabManagementNote</a></cite>]</p></li></ul>
! <table border="1" summary="Editorial note: PaulD"><tr><td width="50%" valign="top" align="left"><b>Editorial note: PaulD</b></td><td width="50%" valign="top" align="right">20050706</td></tr><tr><td valign="top" align="left" colspan="2">This section may be subject to change dependent upon the outcome of the WSDL Last Call Issue LC124, which discusses support compatible evolution of messages described using XML Schema 1.0.</td></tr></table>
  
  <p>While incomplete, these activities all agree in one important 
***************
*** 2770,2774 ****
      <div class="div4">
  	
! <h5><a name="N70059"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
  	<p> The following example demonstrates how content may be extended with
  	    additional content. The reservation service is changed to a newer version that can accept an optional
--- 2772,2776 ----
      <div class="div4">
  	
! <h5><a name="N111AB"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
  	<p> The following example demonstrates how content may be extended with
  	    additional content. The reservation service is changed to a newer version that can accept an optional
***************
*** 2777,2781 ****
  	    into the schema as an optional element. </p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-additional-elements"></a><i><span>Example 5-1. </span>XML Schema with Optional Elements</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:complexType name="tCheckAvailability"&gt;     
--- 2779,2783 ----
  	    into the schema as an optional element. </p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-additional-elements"></a><i><span>Example 5-1. </span>XML Schema with Optional Elements</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:complexType name="tCheckAvailability"&gt;     
***************
*** 2799,2803 ****
      <div class="div4">
  	
! <h5><a name="N70082"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5>
  	<p> Another option is to add the extension as a header block. This is
  	    accomplished by defining an element for the extension and adding a
--- 2801,2805 ----
      <div class="div4">
  	
! <h5><a name="N111C2"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5>
  	<p> Another option is to add the extension as a header block. This is
  	    accomplished by defining an element for the extension and adding a
***************
*** 2805,2809 ****
  	    child of the input. </p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-additional-header-elements"></a><i><span>Example 5-2. </span>Additional optional elements added to a SOAP header</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:element name="NumberOfGuests" type="tNumberOfGuests"/&gt;
--- 2807,2811 ----
  	    child of the input. </p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-additional-header-elements"></a><i><span>Example 5-2. </span>Additional optional elements added to a SOAP header</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:element name="NumberOfGuests" type="tNumberOfGuests"/&gt;
***************
*** 2834,2838 ****
      <div class="div4">
  	
! <h5><a name="N70105"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
  	<p> This following example demonstrates an extention with additional
  	    content. The reservation service requires a number of guests parameter.
--- 2836,2840 ----
      <div class="div4">
  	
! <h5><a name="N111D9"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
  	<p> This following example demonstrates an extention with additional
  	    content. The reservation service requires a number of guests parameter.
***************
*** 2841,2845 ****
  	    element.</p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-additional-mandatory-elements"></a><i><span>Example 5-3. </span>Additional Mandatory Elements in Content</i></p>
                              <div class="exampleInner"><pre>
  &lt;xs:complexType name="tCheckAvailabilityV2"&gt;     
--- 2843,2847 ----
  	    element.</p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-additional-mandatory-elements"></a><i><span>Example 5-3. </span>Additional Mandatory Elements in Content</i></p>
                              <div class="exampleInner"><pre>
  &lt;xs:complexType name="tCheckAvailabilityV2"&gt;     
***************
*** 2862,2866 ****
      <div class="div4">
  	
! <h5><a name="N70128"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
  	<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
  	    of versioning or extension, where the reservationInterface extends the
--- 2864,2868 ----
      <div class="div4">
  	
! <h5><a name="N111F0"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
  	<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
  	    of versioning or extension, where the reservationInterface extends the
***************
*** 2871,2875 ****
      <div class="div4">
  	
! <h5><a name="N70140"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
  	<p> Often mandatory operations are added to an interface. The Hotel service
  	    decides to add an operation to the reservation service which is a
--- 2873,2877 ----
      <div class="div4">
  	
! <h5><a name="N111FC"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
  	<p> Often mandatory operations are added to an interface. The Hotel service
  	    decides to add an operation to the reservation service which is a
***************
*** 2880,2884 ****
  	    inheritance for defining the extension.</p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-additional-mandatory-operation"></a><i><span>Example 5-4. </span>Additional Mandatory Operation Added to the Interface</i></p>
  	    <div class="exampleInner"><pre>
  &lt;interface name="reservationWithConfirmation" extends="cc:creditCardFaults"&gt;
--- 2882,2886 ----
  	    inheritance for defining the extension.</p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-additional-mandatory-operation"></a><i><span>Example 5-4. </span>Additional Mandatory Operation Added to the Interface</i></p>
  	    <div class="exampleInner"><pre>
  &lt;interface name="reservationWithConfirmation" extends="cc:creditCardFaults"&gt;
***************
*** 2914,2918 ****
      <div class="div4">
  	
! <h5><a name="N70166"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
  	<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
  	    changed and messages send to the old Endpoint return a Fault.</p>
--- 2916,2920 ----
      <div class="div4">
  	
! <h5><a name="N11216"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
  	<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
  	    changed and messages send to the old Endpoint return a Fault.</p>
***************
*** 2920,2928 ****
      <div class="div4">
  	
! <h5><a name="N70175"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5>
  	<p> The SOAP Action can be set for the makeReservation request, and making
  	    it different than the earlier version should indicate incompatibility.</p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-SOAP-Action"></a><i><span>Example 5-5. </span>Indicating Incompatibility by changing the SOAP Action</i></p>
                              <div class="exampleInner"><pre>
  &lt;binding name="reservationSOAPBinding" 
--- 2922,2930 ----
      <div class="div4">
  	
! <h5><a name="N1121F"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5>
  	<p> The SOAP Action can be set for the makeReservation request, and making
  	    it different than the earlier version should indicate incompatibility.</p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-SOAP-Action"></a><i><span>Example 5-5. </span>Indicating Incompatibility by changing the SOAP Action</i></p>
                              <div class="exampleInner"><pre>
  &lt;binding name="reservationSOAPBinding" 
***************
*** 2941,2945 ****
      <div class="div4">
  	
! <h5><a name="N70198"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
  	<p> The namespace or name of the makeReservation element can be changed, and
  	    then the interface and bindings changed. To indicate incompatibility,
--- 2943,2947 ----
      <div class="div4">
  	
! <h5><a name="N11236"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
  	<p> The namespace or name of the makeReservation element can be changed, and
  	    then the interface and bindings changed. To indicate incompatibility,
***************
*** 2947,2951 ****
  	    fault. The new interface, with a changed makeReservation, is:</p>
  	<div class="exampleOuter">
! 	    <p style="text-align: left" class="exampleHead"><a name="example-versioning-changing-element-content"></a><i><span>Example 5-6. </span>Indicating incompatibility by changing the element content</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:element name="ghns2:makeReservation" type="ghns:tmakeReservation"/&gt;
--- 2949,2953 ----
  	    fault. The new interface, with a changed makeReservation, is:</p>
  	<div class="exampleOuter">
! 	    <p class="exampleHead" style="text-align: left"><a name="example-versioning-changing-element-content"></a><i><span>Example 5-6. </span>Indicating incompatibility by changing the element content</i></p>
  	    <div class="exampleInner"><pre>
  &lt;xs:element name="ghns2:makeReservation" type="ghns:tmakeReservation"/&gt;
***************
*** 3042,3046 ****
  
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="reservationDetails-OMX736.xml"></a><i><span>Example 5-7. </span>Detail for Reservation OMX736</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;reservationDetails
--- 3044,3048 ----
  
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="reservationDetails-OMX736.xml"></a><i><span>Example 5-7. </span>Detail for Reservation OMX736</i></p>
  					<div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;reservationDetails
***************
*** 3071,3075 ****
  
  				<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="reservationDetails.wsdl"></a><i><span>Example 5-8. </span>The Reservation Details Web Service Description: reservationDetails.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
--- 3073,3077 ----
  
  				<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="reservationDetails.wsdl"></a><i><span>Example 5-8. </span>The Reservation Details Web Service Description: reservationDetails.wsdl</i></p>
  <div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
  &lt;description xmlns="http://www.w3.org/2005/05/wsdl"
***************
*** 3136,3140 ****
  
  	<div class="exampleOuter">
! 		<p style="text-align: left" class="exampleHead"><a name="reservationDetails.xsd"></a><i><span>Example 5-9. </span>
  			The Reservation Details Web Service XML Schema:
  			reservationDetails.xsd
--- 3138,3142 ----
  
  	<div class="exampleOuter">
! 		<p class="exampleHead" style="text-align: left"><a name="reservationDetails.xsd"></a><i><span>Example 5-9. </span>
  			The Reservation Details Web Service XML Schema:
  			reservationDetails.xsd
***************
*** 3242,3246 ****
  					</p>
  					<div class="exampleOuter">
! 						<p style="text-align: left" class="exampleHead"><a name="reservationList-all.xml"></a><i><span>Example 5-10. </span>
  							Response from the Reservation List Web
  							Service</i></p>
--- 3244,3248 ----
  					</p>
  					<div class="exampleOuter">
! 						<p class="exampleHead" style="text-align: left"><a name="reservationList-all.xml"></a><i><span>Example 5-10. </span>
  							Response from the Reservation List Web
  							Service</i></p>
***************
*** 3303,3307 ****
  
  					<div class="exampleOuter">
! 						<p style="text-align: left" class="exampleHead"><a name="reservationList.wsdl"></a><i><span>Example 5-11. </span>
  							The Reservation List Web Service
  							Description: reservationList.wsdl
--- 3305,3309 ----
  
  					<div class="exampleOuter">
! 						<p class="exampleHead" style="text-align: left"><a name="reservationList.wsdl"></a><i><span>Example 5-11. </span>
  							The Reservation List Web Service
  							Description: reservationList.wsdl
***************
*** 3396,3400 ****
  <p><a href="#reservationList.xsd">Example 5-12</a> shows the schema for the messages used in the Reservation List Web service.</p>
  <div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="reservationList.xsd"></a><i><span>Example 5-12. </span>The Reservation List Schema: reservationList.xsd</i></p>
  <div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
--- 3398,3402 ----
  <p><a href="#reservationList.xsd">Example 5-12</a> shows the schema for the messages used in the Reservation List Web service.</p>
  <div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="reservationList.xsd"></a><i><span>Example 5-12. </span>The Reservation List Schema: reservationList.xsd</i></p>
  <div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
***************
*** 3476,3480 ****
  
  					<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="reservationServiceReferences-HSG635.xml"></a><i><span>Example 5-13. </span>A Service Reference to the Reservation Details Web Service</i></p>
  <div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
--- 3478,3482 ----
  
  					<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="reservationServiceReferences-HSG635.xml"></a><i><span>Example 5-13. </span>A Service Reference to the Reservation Details Web Service</i></p>
  <div class="exampleInner"><pre>
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
***************
*** 3498,3502 ****
  <h4><a name="reservationDetails_HTTP"></a>5.3.3 Reservation Details Web Service Using HTTP Transfer</h4><p>This section presents a variation on the example in <a href="#reservationDetails"><b>5.3.1 The Reservation Details Web Service</b></a>.   It  illustrates the use of HTTP transfer operations, GET and PUT, to retrieve and update GreatH hotel reservation details using the Representational State Transfer (REST) architectural style described by Roy Fielding [<cite><a href="#rest">REST</a></cite>].  REST is a distillation of  the architectural properties that Dr. Fielding identified as being vital to the Web's robustness and enormous scalability.  </p><p>Since each reservation in our example will have a distinct URI, the Reservation Details Web
  service can be offered using HTTP GET and HTTP PUT.  The binding would be modified as follows:</p><div class="exampleOuter">
! 						<p style="text-align: left" class="exampleHead"><a name="reservationDetails_HTTP_example"></a><i><span>Example 5-14. </span>
  							Reservation Details Web Service Using HTTP Transfer</i></p>
  						<div class="exampleInner"><pre>
--- 3500,3504 ----
  <h4><a name="reservationDetails_HTTP"></a>5.3.3 Reservation Details Web Service Using HTTP Transfer</h4><p>This section presents a variation on the example in <a href="#reservationDetails"><b>5.3.1 The Reservation Details Web Service</b></a>.   It  illustrates the use of HTTP transfer operations, GET and PUT, to retrieve and update GreatH hotel reservation details using the Representational State Transfer (REST) architectural style described by Roy Fielding [<cite><a href="#rest">REST</a></cite>].  REST is a distillation of  the architectural properties that Dr. Fielding identified as being vital to the Web's robustness and enormous scalability.  </p><p>Since each reservation in our example will have a distinct URI, the Reservation Details Web
  service can be offered using HTTP GET and HTTP PUT.  The binding would be modified as follows:</p><div class="exampleOuter">
! 						<p class="exampleHead" style="text-align: left"><a name="reservationDetails_HTTP_example"></a><i><span>Example 5-14. </span>
  							Reservation Details Web Service Using HTTP Transfer</i></p>
  						<div class="exampleInner"><pre>
***************
*** 3536,3540 ****
  				</p>
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example_reservationList_HTTP_GET"></a><i><span>Example 5-15. </span>
  						Reservation List Web Service Using HTTP GET
  					</i></p>
--- 3538,3542 ----
  				</p>
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example_reservationList_HTTP_GET"></a><i><span>Example 5-15. </span>
  						Reservation List Web Service Using HTTP GET
  					</i></p>
***************
*** 3586,3590 ****
  				</p>
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example_reservationList_HTTP_GET_single"></a><i><span>Example 5-16. </span>
  						Query Sequence Using a Single Query Type
  					</i></p>
--- 3588,3592 ----
  				</p>
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example_reservationList_HTTP_GET_single"></a><i><span>Example 5-16. </span>
  						Query Sequence Using a Single Query Type
  					</i></p>
***************
*** 3614,3618 ****
  				</p>
  				<div class="exampleOuter">
! 					<p style="text-align: left" class="exampleHead"><a name="example_reservationList_HTTP_GET_single_wsdl"></a><i><span>Example 5-17. </span>WSDL 2.0 for Using a Single Query Type</i></p>
  					<div class="exampleInner"><pre>
  						. . .
--- 3616,3620 ----
  				</p>
  				<div class="exampleOuter">
! 					<p class="exampleHead" style="text-align: left"><a name="example_reservationList_HTTP_GET_single_wsdl"></a><i><span>Example 5-17. </span>WSDL 2.0 for Using a Single Query Type</i></p>
  					<div class="exampleInner"><pre>
  						. . .
***************
*** 3683,3687 ****
  <h3><a name="adv-rdf-mapping"></a>5.5 Mapping to RDF and Semantic Web</h3>
  
! 				<table border="1" summary="Editorial note: KevinL"><tr><td align="left" valign="top" width="50%"><b>Editorial note: KevinL</b></td><td align="right" valign="top" width="50%">20050429</td></tr><tr><td colspan="2" align="left" valign="top">
  						This section might be removed - pending on the availability of the RDF mapping note.					</td></tr></table>
  
--- 3685,3689 ----
  <h3><a name="adv-rdf-mapping"></a>5.5 Mapping to RDF and Semantic Web</h3>
  
! 				<table border="1" summary="Editorial note: KevinL"><tr><td width="50%" valign="top" align="left"><b>Editorial note: KevinL</b></td><td width="50%" valign="top" align="right">20050429</td></tr><tr><td valign="top" align="left" colspan="2">
  						This section might be removed - pending on the availability of the RDF mapping note.					</td></tr></table>
  
Received on Monday, 11 July 2005 19:55:16 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Monday, 11 July 2005 19:55:16 GMT