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

2002/ws/desc/wsdl20 wsdl20-primer.xml,1.122,1.123

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 01 Aug 2005 10:39:29 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20050801103929.779BB4F028@homer.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv19372

Modified Files:
	wsdl20-primer.xml 
Log Message:
Added ref to SOAP 1.1 binding


Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.122
retrieving revision 1.123
diff -C2 -d -r1.122 -r1.123
*** wsdl20-primer.xml	1 Aug 2005 10:16:50 -0000	1.122
--- wsdl20-primer.xml	1 Aug 2005 10:39:27 -0000	1.123
***************
*** 92,98 ****
  				
  				<p>Section 2 starts with a hypothetical use case involving a hotel reservation service.  It proceeds step-by-step through the development of a simple example WSDL 2.0 document that describes this service:<ulist><item><p>The   <code>types</code>  element describes the kinds of messages that the service will send and receive.  </p></item><item><p>The <code>interface</code> element describes <emph>what</emph>  abstract functionality the Web service provides.   </p></item><item><p>The <code>binding</code> element describes <emph>how</emph> to access the service. </p></item><item><p>The <code>service</code> element describes <emph>where</emph> to access the service.</p></item></ulist></p>
! 				<p>After presenting the example, it moves on to introduce the WSDL2.0 infoset, schema, and component model. Then it provides more detailed coverage on defining message types, interfaces, bindings, and services.</p>
  				
! 				<p>Section 3 explains the WSDL2.0 importing mechanisms in great details.</p>
  				
  				<p>Section 4 talks about WSDL 2.0 extensibility and various predefined extensions. </p>
--- 92,98 ----
  				
  				<p>Section 2 starts with a hypothetical use case involving a hotel reservation service.  It proceeds step-by-step through the development of a simple example WSDL 2.0 document that describes this service:<ulist><item><p>The   <code>types</code>  element describes the kinds of messages that the service will send and receive.  </p></item><item><p>The <code>interface</code> element describes <emph>what</emph>  abstract functionality the Web service provides.   </p></item><item><p>The <code>binding</code> element describes <emph>how</emph> to access the service. </p></item><item><p>The <code>service</code> element describes <emph>where</emph> to access the service.</p></item></ulist></p>
! 				<p>After presenting the example, it moves on to introduce the WSDL 2.0 infoset, schema, and component model. Then it provides more detailed coverage on defining message types, interfaces, bindings, and services.</p>
  				
! 				<p>Section 3 explains the WSDL 2.0 importing mechanisms in great details.</p>
  				
  				<p>Section 4 talks about WSDL 2.0 extensibility and various predefined extensions. </p>
***************
*** 486,490 ****
  				
  			<div4 id="example-initial-documentation-explanation"><head>Explanation of Example</head><glist><gitem><label><code>&lt;documentation&gt;</code></label><def><p>  This element is optional, but a good idea to include.    It can contain arbitrary mixed content.  </p></def></gitem><gitem><label><code>at http://greath.example.com/2004/reservation-documentation.html</code></label><def><p>The most important thing to  include is  a pointer to any additional documentation that a client developer would need in order to use the service. </p></def></gitem></glist>
! <p>This completes our presentation of the GreatH example.  In the following sections, we will move on to look into more details of various aspects of WSDL2.0 specification. </p></div4></div3>
  </div2>
  
--- 486,490 ----
  				
  			<div4 id="example-initial-documentation-explanation"><head>Explanation of Example</head><glist><gitem><label><code>&lt;documentation&gt;</code></label><def><p>  This element is optional, but a good idea to include.    It can contain arbitrary mixed content.  </p></def></gitem><gitem><label><code>at http://greath.example.com/2004/reservation-documentation.html</code></label><def><p>The most important thing to  include is  a pointer to any additional documentation that a client developer would need in order to use the service. </p></def></gitem></glist>
! <p>This completes our presentation of the GreatH example.  In the following sections, we will move on to look into more details of various aspects of WSDL 2.0 specification. </p></div4></div3>
  </div2>
  
***************
*** 509,516 ****
  <head>WSDL 2.0 Schema</head>
  
! <p>The WSDL 2.0 specification supplies a <xspecref href="&wsdl-ns;">normative WSDL 2.0 schema</xspecref>, defined in <bibref ref="XMLSchemaP1"/>, which can be used as an aid in validating WSDL 2.0 documents. We say "as an aid" here because WSDL 2.0 specification <bibref ref="WSDL-PART1"/> often provides further constraints to the WSDL2.0 schema. In addition to being valid with the normative schema, a WSDL 2.0 document must also follow all the constraints defined by the WSDL2.0 specification.   
  </p>
! <div4 id="element-order"><head>WSDL2.0 Element Ordering</head>
! <p>This section gives an example of how WSDL 2.0 specification constrains the WSDL 2.0 schema about the ordering of top WSDL2.0 elements.</p>  
  
  <p>Although the WSDL 2.0 schema does not indicate the required ordering of elements, the WSDL 2.0 specification (WSDL 2.0 Part 1 <bibref ref="WSDL-PART1"/> section "<xspecref href="&w3c-designation-part1;#Description_XMLRep">XML Representation of Description Component</xspecref>") clearly states a set of constraints about how the children elements of the <code>description</code> element should be ordered. Thus, the order of the WSDL 2.0 elements matters, in spite of what the WSDL 2.0 schema says. </p><p>The following is a pseudo-content model of <code>description</code>.</p>
--- 509,516 ----
  <head>WSDL 2.0 Schema</head>
  
! <p>The WSDL 2.0 specification supplies a <xspecref href="&wsdl-ns;">normative WSDL 2.0 schema</xspecref>, defined in <bibref ref="XMLSchemaP1"/>, which can be used as an aid in validating WSDL 2.0 documents. We say "as an aid" here because WSDL 2.0 specification <bibref ref="WSDL-PART1"/> often provides further constraints to the WSDL 2.0 schema. In addition to being valid with the normative schema, a WSDL 2.0 document must also follow all the constraints defined by the WSDL 2.0 specification.   
  </p>
! <div4 id="element-order"><head>WSDL 2.0 Element Ordering</head>
! <p>This section gives an example of how WSDL 2.0 specification constrains the WSDL 2.0 schema about the ordering of top WSDL 2.0 elements.</p>  
  
  <p>Although the WSDL 2.0 schema does not indicate the required ordering of elements, the WSDL 2.0 specification (WSDL 2.0 Part 1 <bibref ref="WSDL-PART1"/> section "<xspecref href="&w3c-designation-part1;#Description_XMLRep">XML Representation of Description Component</xspecref>") clearly states a set of constraints about how the children elements of the <code>description</code> element should be ordered. Thus, the order of the WSDL 2.0 elements matters, in spite of what the WSDL 2.0 schema says. </p><p>The following is a pseudo-content model of <code>description</code>.</p>
***************
*** 1296,1300 ****
  
  
! 			<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>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</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>&lt;binding...wsoap:version="1.1"</code></label><def><p>This line indicates that this binding uses SOAP 1.1, rather than SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP"&gt;</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>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></label><def><p>Note that <code>wsoap:mep</code> is not appliable to SOAP 1.1 binding. </p></def></gitem>
--- 1296,1300 ----
  
  
! 			<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>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</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>&lt;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"&gt;</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>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></label><def><p>Note that <code>wsoap:mep</code> is not appliable to SOAP 1.1 binding. </p></def></gitem>
***************
*** 3751,3755 ****
  	  1998.</bibl>
  
! 					<bibl key="WSDL20 Core" href="&w3c-designation-part1;" id="WSDL-PART1">
  						<titleref>&part1.title;</titleref>, R. Chinnici, J-J.
              Moreau, A. Ryman, S. Weerawarana, Editors. World Wide Web Consortium,
--- 3751,3755 ----
  	  1998.</bibl>
  
! 					<bibl key="WSDL 2.0 Core" href="&w3c-designation-part1;" id="WSDL-PART1">
  						<titleref>&part1.title;</titleref>, R. Chinnici, J-J.
              Moreau, A. Ryman, S. Weerawarana, Editors. World Wide Web Consortium,
***************
*** 3776,3779 ****
--- 3776,3795 ----
  	  </bibl>
  
+ 	  <bibl key="WSDL 2.0 SOAP 1.1 Binding" href="&w3c-designation-soap11binding;"
+ 	  	id="WSDL-SOAP11">
+ 	  	<titleref>
+ 		  &soap11binding.title;
+ 	  	</titleref>, A. Vedamuthu, Editor.  World
+ 	  	Wide Web Consortium, &draft.day; &draft.month;
+ 	  	&draft.year;.  This version of the "&soap11binding.title;"
+ 	  	Specification is available at
+ 	  	&w3c-designation-soap11binding;. The
+ 	  	<loc href="&soap11binding.latest;">
+ 	  		latest version of "&soap11binding.title;"
+ 	  	</loc>
+ 	  	is available at
+ 	  	&soap11binding.latest;.
+ 	  </bibl>
+ 
  	  <!--
  	  <bibl key="WSDL 2.0 RDF Mapping" href="&w3c-designation-part4;" id="WSDL-PART4">
Received on Monday, 1 August 2005 10:39:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:50 UTC