- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 01 Aug 2005 11:00:07 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv23760
Modified Files:
wsdl20-primer.xml
Log Message:
Fixed typos
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.125
retrieving revision 1.126
diff -C2 -d -r1.125 -r1.126
*** wsdl20-primer.xml 1 Aug 2005 10:55:56 -0000 1.125
--- wsdl20-primer.xml 1 Aug 2005 11:00:05 -0000 1.126
***************
*** 71,75 ****
</langusage>
<revisiondesc>
! <p>Last modified: $Date$</p>
</revisiondesc>
</header>
--- 71,75 ----
</langusage>
<revisiondesc>
! <p>Last "Editors' copy $Date$</p>
</revisiondesc>
</header>
***************
*** 1297,1301 ****
<div4 id="more-bindings-soap-example-explanation"><head>Explanation of Example</head><p>Most lines in this example is the same as previously explained in <specref ref="basics-binding"/>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.<glist><gitem><label><code><description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"></code></label><def><p>This is the namespace for terms defined within the SOAP 1.1 specification <bibref ref="SOAP11"/>.</p></def></gitem><gitem><label><code><binding...wsoap:version="1.1"</code></label><def><p>This line indicates that this binding uses SOAP 1.1 <bibref ref="WSDL-SOAP11"/>, rather than SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP"></code></label><def><p>This line specifies that HTTP should be used as the underlying transmission protocol. See also <specref ref="adv-get-vs-post"/>.</p></def></gitem>
! <gitem><label><code><operation ref="tns:opCheckAvailability"/></code></label><def><p>Note that <code>wsoap:mep</code> is not appliable to SOAP 1.1 binding. </p></def></gitem>
<gitem><label><code><fault...wsoap:code="soap11:Client"/></code></label><def><p>This line specifies the SOAP 1.1 fault code that will be used in transmitting invalidDataFault.</p></def></gitem>
</glist></p>
--- 1297,1301 ----
<div4 id="more-bindings-soap-example-explanation"><head>Explanation of Example</head><p>Most lines in this example is the same as previously explained in <specref ref="basics-binding"/>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.<glist><gitem><label><code><description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"></code></label><def><p>This is the namespace for terms defined within the SOAP 1.1 specification <bibref ref="SOAP11"/>.</p></def></gitem><gitem><label><code><binding...wsoap:version="1.1"</code></label><def><p>This line indicates that this binding uses SOAP 1.1 <bibref ref="WSDL-SOAP11"/>, rather than SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP"></code></label><def><p>This line specifies that HTTP should be used as the underlying transmission protocol. See also <specref ref="adv-get-vs-post"/>.</p></def></gitem>
! <gitem><label><code><operation ref="tns:opCheckAvailability"/></code></label><def><p>Note that <code>wsoap:mep</code> is not applicable to SOAP 1.1 binding. </p></def></gitem>
<gitem><label><code><fault...wsoap:code="soap11:Client"/></code></label><def><p>This line specifies the SOAP 1.1 fault code that will be used in transmitting invalidDataFault.</p></def></gitem>
</glist></p>
***************
*** 2366,2370 ****
}
]]></eg></example><p>Programming languages may further specify how faults are mapped to
! langauage constructs and their scopes, such as Exceptions, but they
are not specific to RPC style.</p></div2>
--- 2366,2370 ----
}
]]></eg></example><p>Programming languages may further specify how faults are mapped to
! language constructs and their scopes, such as Exceptions, but they
are not specific to RPC style.</p></div2>
***************
*** 2744,2748 ****
<div4>
<head>Additional Mandatory Elements in Content</head>
! <p> This following example demonstrates an extention with additional
content. The reservation service requires a number of guests parameter.
The service provider wants existing clients to be unable to use the
--- 2744,2748 ----
<div4>
<head>Additional Mandatory Elements in Content</head>
! <p> This following example demonstrates an extension with additional
content. The reservation service requires a number of guests parameter.
The service provider wants existing clients to be unable to use the
***************
*** 2986,2990 ****
services. Use these services to retrieve or update reservation
details. Each reservation has its own service and endpoint. To
! obtain the serice reference for a reservation, make a request to
the GreatH Reservation List Web service. See
reservationList.wsdl for a description of the Reservation List
--- 2986,2990 ----
services. Use these services to retrieve or update reservation
details. Each reservation has its own service and endpoint. To
! obtain the service reference for a reservation, make a request to
the GreatH Reservation List Web service. See
reservationList.wsdl for a description of the Reservation List
Received on Monday, 1 August 2005 11:00:11 UTC