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

2002/ws/desc/wsdl20 wsdl20.xml,1.220,1.221

From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 22 Apr 2005 04:55:29 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DOqCP-00032q-Ke@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20.xml 
Log Message:
Corrected text referencing {interface operations} and {interface faults} to include inherited components.

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.220
retrieving revision 1.221
diff -C2 -d -r1.220 -r1.221
*** wsdl20.xml	22 Apr 2005 04:36:59 -0000	1.220
--- wsdl20.xml	22 Apr 2005 04:55:27 -0000	1.221
***************
*** 3358,3362 ****
              component in the {interface faults} property of the parent Interface
              Operation component's parent Interface
!             component. Identifying the Interface Fault component therefore
              indirectly defines the actual content or payload of the
              fault message.</p></item>
--- 3358,3363 ----
              component in the {interface faults} property of the parent Interface
              Operation component's parent Interface
!             component, or an Interface component that it directly or indirectly extends. 
!             Identifying the Interface Fault component therefore
              indirectly defines the actual content or payload of the
              fault message.</p></item>
***************
*** 3601,3605 ****
  		    <td>{interface fault}</td> <td>The Interface Fault
                      component from {interface faults} property of the parent
!                     Interface component whose {name} property is the
                      actual value of the <att>ref</att> &AII;.</td>
  		  </tr>
--- 3602,3607 ----
  		    <td>{interface fault}</td> <td>The Interface Fault
                      component from {interface faults} property of the parent
!                     Interface component, or an Interface component that it directly or indirectly extends,
!                     whose {name} property is the
                      actual value of the <att>ref</att> &AII;.</td>
  		  </tr>
***************
*** 4973,4978 ****
        			component in the {interface faults} property of the
        			Interface component identified by the {interface}
!       			property of the parent Binding component. This is the
!       			Interface Fault component for which binding
        			information is being specified.
        		</p>
--- 4975,4981 ----
        			component in the {interface faults} property of the
        			Interface component identified by the {interface}
!       			property of the parent Binding component, or an Interface component
!       			that that Interface component directly or indirectly extends. 
!       			This is the Interface Fault component for which binding
        			information is being specified.
        		</p>
***************
*** 5215,5219 ****
        			component in the {interface operations} property of
        			the Interface component identified by the {interface}
!       			property of the parent Binding component. This is the
        			Interface Operation component for which binding
        			information is being specified.
--- 5218,5223 ----
        			component in the {interface operations} property of
        			the Interface component identified by the {interface}
!       			property of the parent Binding component, or an Interface
!       			component that that Interface component directly or indirectly extends. This is the
        			Interface Operation component for which binding
        			information is being specified.
***************
*** 5301,5305 ****
  
        <p> For each Binding Operation component in the {binding operations}
!       property of a Binding component, the {operation reference}
        property MUST be unique. That is, one cannot define multiple
        bindings for the same operation within a given Binding
--- 5305,5309 ----
  
        <p> For each Binding Operation component in the {binding operations}
!       property of a Binding component, the {interface operation}
        property MUST be unique. That is, one cannot define multiple
        bindings for the same operation within a given Binding
***************
*** 6133,6140 ****
            <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
            components specified in the {interface operations} property of that Interface
!           component.  Further, consider all Message Reference components specified
            in the {message references} properties of said Interface Operation
            components.  Further, consider all said Message Reference components that
--- 6137,6145 ----
            <head>Operation Name Mapping Requirement</head>
  
!           <p diff="chg">Consider the Interface component specified in the {interface}
            property of a Service component. Further, consider all Interface Operation
            components specified in the {interface operations} property of that Interface
!           component and the Interface component it directly or indirectly extends.  
!           Further, consider all Message Reference components specified
            in the {message references} properties of said Interface Operation
            components.  Further, consider all said Message Reference components that
Received on Friday, 22 April 2005 04:55:31 UTC

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