2002/ws/desc/wsdl20 wsdl20.xml,1.249,1.250

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

Modified Files:
	wsdl20.xml 
Log Message:
Rewrote the ONMR as Best practice.

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.249
retrieving revision 1.250
diff -C2 -d -r1.249 -r1.250
*** wsdl20.xml	3 May 2005 16:18:59 -0000	1.249
--- wsdl20.xml	3 May 2005 16:31:09 -0000	1.250
***************
*** 6349,6354 ****
  
          <div4 id="Service_OperationName">
!           <head>Operation Name Mapping Requirement</head>
  
            <p>Consider the Interface component specified in the {interface}
            property of a Service component. Further, consider all Interface Operation
--- 6349,6358 ----
  
          <div4 id="Service_OperationName">
!           <head>Operation Name Mapping Requirement (non-normative)</head>
  
+           <note>
+               <p>This section is best-practice and hence non-normative.</p>
+           </note>
+           
            <p>Consider the Interface component specified in the {interface}
            property of a Service component. Further, consider all Interface Operation
***************
*** 6365,6374 ****
            the global element declarations specified by the values of the {element declaration}
  	  properties of these Interface Message Reference components are not unique
! 	  when considered together, then either one of the following two
! 	  conditions MUST apply: 
  	  </p>
  	  <olist>
  	    <item><p>the {features} property of the Service or Interface components
!               MUST contain a Feature component, having a {required} property with
  	      a value of <emph>true</emph>, that unambiguously identifies the
                mechanism that a message sender is required to support in order to
--- 6369,6378 ----
            the global element declarations specified by the values of the {element declaration}
  	  properties of these Interface Message Reference components are not unique
! 	  when considered together, and the Operation Name Mapping Requirement needs to be engaged,
! 	  then either one of the following two conditions applies: 
  	  </p>
  	  <olist>
  	    <item><p>the {features} property of the Service or Interface components
!               contains a Feature component, having a {required} property with
  	      a value of <emph>true</emph>, that unambiguously identifies the
                mechanism that a message sender is required to support in order to
***************
*** 6379,6383 ****
  	    </item>
  	    <item><p>the &EII; for the Interface component
! 	    MUST contain an extension element (i.e., an element that is not
  	    in the &wsdl-ns; namespace), having a wsdl:required &AII; with
  	    a value of <attval>true</attval>, that unambiguously identifies
--- 6383,6387 ----
  	    </item>
  	    <item><p>the &EII; for the Interface component
! 	    contains an extension element (i.e., an element that is not
  	    in the &wsdl-ns; namespace), having a wsdl:required &AII; with
  	    a value of <attval>true</attval>, that unambiguously identifies
***************
*** 9620,9623 ****
--- 9624,9633 ----
      	<td>20050503</td>
      	<td>JJM</td>
+     	<td>Rewrote the ONMR as Best practice.</td>
+     </tr>
+     
+     <tr>
+     	<td>20050503</td>
+     	<td>JJM</td>
      	<td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC112">LC112</loc>:
      	Implemented resolution for issue LC112.</td>

Received on Tuesday, 3 May 2005 16:31:27 UTC