2002/ws/desc/wsdl20 wsdl20.html,1.111,1.112 wsdl20.xml,1.121,1.122

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

Modified Files:
	wsdl20.html wsdl20.xml 
Log Message:
added paul text for faults issue 235

Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -C2 -d -r1.111 -r1.112
*** wsdl20.html	26 Jul 2004 20:36:00 -0000	1.111
--- wsdl20.html	26 Jul 2004 20:43:29 -0000	1.112
***************
*** 1029,1048 ****
  <h4><a name="InterfaceFault_details"></a>2.3.1 The Interface Fault Component</h4> 
          
!         <p>An Interface Fault component describes a fault that 
! MAY occur during invocation of an operation of the interface. 
! The Interface Fault component declares an abstract fault by naming 
! it and indicating the contents of the fault message. When and how 
! the fault message flows is indicated by the Interface Operation 
! component <a href="#InterfaceOperation"><b>2.4 Interface Operation</b></a>.</p>
  
! <p>The Interface Fault component provides a clear mechanism to name and
! describe the set of faults an interface may generate. This allows operations 
! to easily identify the individual faults they may generate by name. 
! This mechanism allows the ready identification of the same fault occurring 
! across multiple operations and referenced in multiple bindings as well
! as reducing duplication of description for an individual fault.</p>
  
! <p>Note that faults other than the ones described in the Interface component
! can also be generated at run-time, i.e. faults are an open set.</p>
  
          <p>The properties of the Interface Fault component are
--- 1029,1063 ----
  <h4><a name="InterfaceFault_details"></a>2.3.1 The Interface Fault Component</h4> 
          
!         <p>A fault is an event that occurs during the execution of a
!         message exchange that disrupts the normal flow of
!         messages.</p>
!  
!         <p>A fault is typically raised when a party is unable to
!         communicate an error condition inside the normal message flow,
!         or a party wishes to terminate a message exchange. A fault
!         message may be used to communicate out of band information
!         such as the reason for the error, the origin of the fault, as
!         well as other informal diagnostics such as a program stack
!         trace.</p>
  
!         <p>An Interface Fault component describes a fault that MAY
!         occur during invocation of an operation of the interface.  The
!         Interface Fault component declares an abstract fault by naming
!         it and indicating the contents of the fault message. When and
!         how the fault message flows is indicated by the Interface
!         Operation component <a href="#InterfaceOperation"><b>2.4 Interface Operation</b></a>.</p>
  
!         <p>The Interface Fault component provides a clear mechanism to
!         name and describe the set of faults an interface may
!         generate. This allows operations to easily identify the
!         individual faults they may generate by name.  This mechanism
!         allows the ready identification of the same fault occurring
!         across multiple operations and referenced in multiple bindings
!         as well as reducing duplication of description for an
!         individual fault.</p>
! 
!         <p>Note that faults other than the ones described in the
!         Interface component can also be generated at run-time,
!         i.e. faults are an open set.</p>
  
          <p>The properties of the Interface Fault component are
***************
*** 1062,1068 ****
              </li>
  
!             <li><p>{features} OPTIONAL. A set of Feature components.</p></li>
  
!             <li><p>{properties} OPTIONAL. A set of Property components.</p></li>
  	  </ul>
  
--- 1077,1085 ----
              </li>
  
!             <li><p>{features} OPTIONAL. A set of Feature
!             components.</p></li>
  
!             <li><p>{properties} OPTIONAL. A set of Property
!             components.</p></li>
  	  </ul>
  
***************
*** 2848,2852 ****
  		  </tr>
  		  <tr>
- 
  		    <td rowspan="1" colspan="1">{required}</td>
  			<td rowspan="1" colspan="1">
--- 2865,2868 ----
***************
*** 6908,6911 ****
--- 6924,6932 ----
  	  <td rowspan="1" colspan="1">20040727</td>
            <td rowspan="1" colspan="1">SW</td>
+           <td rowspan="1" colspan="1">Incorporated Paul's words for issue 235</td>
+         </tr>
+         <tr>
+ 	  <td rowspan="1" colspan="1">20040727</td>
+           <td rowspan="1" colspan="1">SW</td>
            <td rowspan="1" colspan="1">Added MarkN's text for issue 211</td>
          </tr>

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.121
retrieving revision 1.122
diff -C2 -d -r1.121 -r1.122
*** wsdl20.xml	26 Jul 2004 20:36:00 -0000	1.121
--- wsdl20.xml	26 Jul 2004 20:43:29 -0000	1.122
***************
*** 1026,1045 ****
        <head>The Interface Fault Component</head> 
          
!         <p>An Interface Fault component describes a fault that 
! MAY occur during invocation of an operation of the interface. 
! The Interface Fault component declares an abstract fault by naming 
! it and indicating the contents of the fault message. When and how 
! the fault message flows is indicated by the Interface Operation 
! component <specref ref="InterfaceOperation"/>.</p>
  
! <p>The Interface Fault component provides a clear mechanism to name and
! describe the set of faults an interface may generate. This allows operations 
! to easily identify the individual faults they may generate by name. 
! This mechanism allows the ready identification of the same fault occurring 
! across multiple operations and referenced in multiple bindings as well
! as reducing duplication of description for an individual fault.</p>
  
! <p>Note that faults other than the ones described in the Interface component
! can also be generated at run-time, i.e. faults are an open set.</p>
  
          <p>The properties of the Interface Fault component are
--- 1026,1060 ----
        <head>The Interface Fault Component</head> 
          
!         <p>A fault is an event that occurs during the execution of a
!         message exchange that disrupts the normal flow of
!         messages.</p>
!  
!         <p>A fault is typically raised when a party is unable to
!         communicate an error condition inside the normal message flow,
!         or a party wishes to terminate a message exchange. A fault
!         message may be used to communicate out of band information
!         such as the reason for the error, the origin of the fault, as
!         well as other informal diagnostics such as a program stack
!         trace.</p>
  
!         <p>An Interface Fault component describes a fault that MAY
!         occur during invocation of an operation of the interface.  The
!         Interface Fault component declares an abstract fault by naming
!         it and indicating the contents of the fault message. When and
!         how the fault message flows is indicated by the Interface
!         Operation component <specref ref="InterfaceOperation"/>.</p>
  
!         <p>The Interface Fault component provides a clear mechanism to
!         name and describe the set of faults an interface may
!         generate. This allows operations to easily identify the
!         individual faults they may generate by name.  This mechanism
!         allows the ready identification of the same fault occurring
!         across multiple operations and referenced in multiple bindings
!         as well as reducing duplication of description for an
!         individual fault.</p>
! 
!         <p>Note that faults other than the ones described in the
!         Interface component can also be generated at run-time,
!         i.e. faults are an open set.</p>
  
          <p>The properties of the Interface Fault component are
***************
*** 1059,1065 ****
              </item>
  
!             <item><p>{features} OPTIONAL. A set of Feature components.</p></item>
  
!             <item><p>{properties} OPTIONAL. A set of Property components.</p></item>
  	  </ulist>
  
--- 1074,1082 ----
              </item>
  
!             <item><p>{features} OPTIONAL. A set of Feature
!             components.</p></item>
  
!             <item><p>{properties} OPTIONAL. A set of Property
!             components.</p></item>
  	  </ulist>
  
***************
*** 6894,6897 ****
--- 6911,6919 ----
  	  <td>20040727</td>
            <td>SW</td>
+           <td>Incorporated Paul's words for issue 235</td>
+         </tr>
+         <tr>
+ 	  <td>20040727</td>
+           <td>SW</td>
            <td>Added MarkN's text for issue 211</td>
          </tr>

Received on Monday, 26 July 2004 16:46:59 UTC