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

2002/ws/desc/wsdl20 wsdl20-primer.xml,1.142,1.143

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 22 Nov 2005 12:06:06 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20051122120606.BC1034F413@homer.w3.org>

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

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.142
retrieving revision 1.143
diff -C2 -d -r1.142 -r1.143
*** wsdl20-primer.xml	18 Nov 2005 13:11:01 -0000	1.142
--- wsdl20-primer.xml	22 Nov 2005 12:06:04 -0000	1.143
***************
*** 125,129 ****
     (see <bibref ref="XMLInfoSet"/>). </p>
     
!    <p>Following the convention for XML syntax sumary in <bibref ref="WSDL-PART1"/>, this primer uses an informal syntax to describe the XML grammar of a WSDL 2.0 document: 
     <ulist>
     <item><p>The syntax appears as an XML instance, but the values indicate the data types instead of values.</p></item> 
--- 125,129 ----
     (see <bibref ref="XMLInfoSet"/>). </p>
     
!    <p>Following the convention for XML syntax summary in <bibref ref="WSDL-PART1"/>, this primer uses an informal syntax to describe the XML grammar of a WSDL 2.0 document: 
     <ulist>
     <item><p>The syntax appears as an XML instance, but the values indicate the data types instead of values.</p></item> 
***************
*** 705,709 ****
  </eg>
  					
! <p>There are two ways to make XML Schema message definitions visible, or in other words, available for reference by Qname (see WSDL 2.0 Part 1 <bibref ref="WSDL-PART1"/> "<xspecref href="&w3c-designation-part1;#qnameres">QName Resolution</xspecref>") in a WSDL 2.0 document: inlining or importing.  Inlining is to put the schema definitions directly within an <code>xs:schema</code> element under <code>types</code>.  Importing is to have the schema defined in a separate document and then bring it into the WSDL definition by using <code>xs:import</code> directly under <code>types</code>. </p> 
  
  <p>In the following sections, we will provide examples for the different mechanisms.</p>			 
--- 705,709 ----
  </eg>
  					
! <p>There are two ways to make XML Schema message definitions visible, or in other words, available for reference by QName (see WSDL 2.0 Part 1 <bibref ref="WSDL-PART1"/> "<xspecref href="&w3c-designation-part1;#qnameres">QName Resolution</xspecref>") in a WSDL 2.0 document: inlining or importing.  Inlining is to put the schema definitions directly within an <code>xs:schema</code> element under <code>types</code>.  Importing is to have the schema defined in a separate document and then bring it into the WSDL definition by using <code>xs:import</code> directly under <code>types</code>. </p> 
  
  <p>In the following sections, we will provide examples for the different mechanisms.</p>			 
***************
*** 771,775 ****
  
  
! <p>Of course, an inlined XML schema may also use XML Schema's native <code>xs:include</code> element to refer to schemas defined in separate files when the included schema has no namespace or has the same namespace as the including schema. In this case, according to XML Schema, the included schema components become a part of the including schema as though they had been copied and pasted into the including schema. Hence, the included schema components are also available to the containing WSDL 2.0 <code>description</code> for reference by Qname. </p>	
  
  <p>The following example has the same effect as <specref ref="example-initial-types"/>:</p>
--- 771,775 ----
  
  
! <p>Of course, an inlined XML schema may also use XML Schema's native <code>xs:include</code> element to refer to schemas defined in separate files when the included schema has no namespace or has the same namespace as the including schema. In this case, according to XML Schema, the included schema components become a part of the including schema as though they had been copied and pasted into the including schema. Hence, the included schema components are also available to the containing WSDL 2.0 <code>description</code> for reference by QName. </p>	
  
  <p>The following example has the same effect as <specref ref="example-initial-types"/>:</p>
***************
*** 987,991 ****
  					operations, component equivalence basically means
  					that the two operations have the same set of
! 					attributes and descendents.) In the second case, if
  					two operations have the same name in the same WSDL
  					2.0 target namespace but are not equivalent, then it
--- 987,991 ----
  					operations, component equivalence basically means
  					that the two operations have the same set of
! 					attributes and descendants.) In the second case, if
  					two operations have the same name in the same WSDL
  					2.0 target namespace but are not equivalent, then it
***************
*** 1104,1108 ****
  					<item><p>RPC Style. The RPC style is selected when the <att>style</att> is assigned the value &wsdl-rpc-ns;. It places restrictions for Remote Procedure Call-types of interactions. </p></item>
  					<item><p>IRI Style. The IRI style is selected when the <att>style</att> is assigned the value &IRI-STYLE;. It places restrictions on message definitions so they may be serialized into something like HTTP URL encoded.</p></item>
! 					<item><p>The Multipart style. The Multipart style is selected when the <att>style</att> is assigned the value &MULTIPART-STYLE;. In the HTTP binding, for XForm clients, a message must be defined following the Multipart style and serialized as "Multipart/form-data". </p> </item>
  				</ulist>	
  						
--- 1104,1108 ----
  					<item><p>RPC Style. The RPC style is selected when the <att>style</att> is assigned the value &wsdl-rpc-ns;. It places restrictions for Remote Procedure Call-types of interactions. </p></item>
  					<item><p>IRI Style. The IRI style is selected when the <att>style</att> is assigned the value &IRI-STYLE;. It places restrictions on message definitions so they may be serialized into something like HTTP URL encoded.</p></item>
! 					<item><p>The Multipart style. The Multipart style is selected when the <att>style</att> is assigned the value &MULTIPART-STYLE;. In the HTTP binding, for XForms clients, a message must be defined following the Multipart style and serialized as "Multipart/form-data". </p> </item>
  				</ulist>	
  						
***************
*** 2924,2928 ****
  	<p> The namespace or name of the makeReservation element can be changed, and
  	    then the interface and bindings changed. To indicate incompatibility,
! 	    requests using the old makeReservation Qname should probably return a
  	    fault. The new interface, with a changed makeReservation, is:</p>
  	<example id="example-versioning-changing-element-content">
--- 2924,2928 ----
  	<p> The namespace or name of the makeReservation element can be changed, and
  	    then the interface and bindings changed. To indicate incompatibility,
! 	    requests using the old makeReservation QName should probably return a
  	    fault. The new interface, with a changed makeReservation, is:</p>
  	<example id="example-versioning-changing-element-content">
Received on Tuesday, 22 November 2005 12:06:56 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Tuesday, 22 November 2005 12:06:57 GMT