- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 02 May 2005 03:11:57 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv9377
Modified Files:
wsdl20.xml
Log Message:
Fixed typos reported by Lawrence Mandel.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.237
retrieving revision 1.238
diff -C2 -d -r1.237 -r1.238
*** wsdl20.xml 2 May 2005 03:06:54 -0000 1.237
--- wsdl20.xml 2 May 2005 03:11:55 -0000 1.238
***************
*** 2387,2391 ****
cannot be identified solely by their QName. Indeed, two Interface components
whose {name} property value has the same namespace name, but different local names,
! can contain Interface Fault components wich the same {name} property value. Thus,
the {name} property of Interface Fault components is not sufficient to form the unique
identity of an Interface Fault component.</p></note>
--- 2387,2391 ----
cannot be identified solely by their QName. Indeed, two Interface components
whose {name} property value has the same namespace name, but different local names,
! can contain Interface Fault components with the same {name} property value. Thus,
the {name} property of Interface Fault components is not sufficient to form the unique
identity of an Interface Fault component.</p></note>
***************
*** 2740,2744 ****
cannot be identified solely by their QName. Indeed, two Interface components
whose {name} property value has the same namespace name, but different local names,
! can contain Interface Operation components wich the same {name} property value. Thus,
the {name} property of Interface Operation components is not sufficient to form the unique
identity of an Interface Operation component.</p></note>
--- 2740,2744 ----
cannot be identified solely by their QName. Indeed, two Interface components
whose {name} property value has the same namespace name, but different local names,
! can contain Interface Operation components with the same {name} property value. Thus,
the {name} property of Interface Operation components is not sufficient to form the unique
identity of an Interface Operation component.</p></note>
***************
*** 4006,4010 ****
within the fault reference component, those
within the parent interface operation component and
! those withing its parent interface component.</p></item>
<item><p>Binding component: all features asserted within
--- 4006,4010 ----
within the fault reference component, those
within the parent interface operation component and
! those within its parent interface component.</p></item>
<item><p>Binding component: all features asserted within
Received on Monday, 2 May 2005 03:12:00 UTC