2002/ws/desc/wsdl20 wsdl20.xml,1.273,1.274

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

Modified Files:
	wsdl20.xml 
Log Message:
LC75x: removed appendix "migrating from WSDL 1.1 to WSDL 2.0".

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.273
retrieving revision 1.274
diff -C2 -d -r1.273 -r1.274
*** wsdl20.xml	1 Jun 2005 05:59:29 -0000	1.273
--- wsdl20.xml	2 Jun 2005 09:44:49 -0000	1.274
***************
*** 10724,10800 ****
      </inform-div1>
  
-     <inform-div1 id="migration">
-       <head>Migrating from WSDL 1.1 to WSDL 2.0</head>
-       <p>This section will attempt to document some of the migration
-          concerns of going from WSDL 1.1 to WSDL 2.0. We do not claim
-          that all migration problems will be addressed here.</p>
- 
-       <div2 id='mig_ops'>
-         <head>Operation Overloading</head>
-         <p>WSDL 1.1 supported operation overloading, whereas WSDL 2.0 does not.
-         </p>
-       </div2>
- 
-       <div2 id='mig_porttypes'>
-         <head>PortTypes</head>
-         <p>Port types have been renamed to interfaces. We now have interface inheritance.</p>
-       </div2>
- 
-       <div2 id='mig_ports'>
-         <head>Ports</head>
-         <p>Ports have been renamed to endpoints.</p>
-       </div2>
-       
-       <div2 id='single_interface_per_service'>
-       	<head>Single Interface per Service</head>
-       	<p>
-       		WSDL 2.0 requires that within a service, all endpoints (called ports in WSDL 1.1)
-       		implement exactly the same interface (called portType in WSDL 1.1).
-       		WSDL 1.1 imposed no such restriction. WSDL 1.1 documents could contain ports, from the same service,
-       		that implemented differents portTypes. Such WSDL 1.1 documents must therefore be converted, before
-       		they are valid WSDL 2.0 documents. Note: other types of conversions may also be required,
-       		because of other differences between WSDL 2.0 and WSDL 1.1. These differences are not considered
-       		further in this section.
-       	</p>
-       	<p>
-       		To convert a WSDL 1.1 document that contains ports from the same service that implement different
-       		portTypes, one must first move each portType implementing a different port to a new service. The new service
-       		is a replica of the original service, apart from the fact that it implements a different set of portTypes.
-       	</p>
-       	<p>
-       		Is is then generally desirable to indicate that the new services are related to each other.
-       		This can be achieved by using one of the following alternatives:
-       	</p>
-       	<ulist>
-       		<item><p>
-       		<b>Single document</b>.
-       		Keep the new services under the same <el>definition</el> &EII;.
-       		</p></item>
-       		
-       		<item><p>
-       		<b>Multiple documents, same targetNamespace</b>.
-       		Split the new services over multiple WSDL 2.0 documents,
-       		each with the same <att>targetNamespace</att>.
-       		</p></item>
-       		
-       		<item><p>
-       		<b>Multiple documents, same endpoint</b>.
-       		Split the new services in multiple WSDL 2.0 documents,
-       		each with the same <el>endpoint</el>. Note that this provides
-       		a looser coupling that the <att>targetNamespace</att> alternative above.
-       		</p></item>
-       		
-       		<item><p>
-       		<b>Extension</b>.
-       		Use a WSDL 2.0 extension whose semantics would be to link the new services
-       		together. This is somewhat analoguous to the <att>targetNamespace</att> approach above,
-       		although such an extension may carry additional semantics.
-       		The definition of such an extension is outside the scope of this specification.
-       		</p></item>
-       	</ulist>
-       </div2>
- 
-     </inform-div1>
- 
      <inform-div1 id='other-schemalang'>
  	  <head>Examples of Specifications of Extension Elements for Alternative Schema
--- 10724,10727 ----
***************
*** 11016,11019 ****
--- 10943,10953 ----
      
      <tr>
+     	<td>20050601</td>
+     	<td>JJM</td>
+     	<td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC75">LC75x</loc>: 
+     	removed appendix "migrating from WSDL 1.1 to WSDL 2.0".</td>
+     </tr>
+     
+     <tr>
      	<td>20050531</td>
      	<td>JJM</td>
***************
*** 11658,11662 ****
      		<loc href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC73'>LC73</loc>
      		<loc href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC75n'>LC75n</loc>:
!     		Added <specref ref="single_interface_per_service" />.
      	</td>
      </tr>
--- 11592,11596 ----
      		<loc href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC73'>LC73</loc>
      		<loc href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC75n'>LC75n</loc>:
!     		Added "single_interface_per_service".
      	</td>
      </tr>
***************
*** 12402,12406 ****
  	  <td>20030313</td>
  	  <td>MJG</td>
! 	  <td>Added text to <specref ref='mig_porttypes' /></td>
  	</tr>
  	<tr>
--- 12336,12340 ----
  	  <td>20030313</td>
  	  <td>MJG</td>
! 	  <td>Added text to 'mig_porttypes'</td>
  	</tr>
  	<tr>

Received on Thursday, 2 June 2005 09:44:57 UTC