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

2002/ws/desc/wsdl20 wsdl20.xml,1.217,1.218

From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 20 Apr 2005 09:55:11 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DOBvL-0001gv-Vs@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20.xml 
Log Message:
LC 78, part 4 (uniquely identifying interface operation components)

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.217
retrieving revision 1.218
diff -C2 -d -r1.217 -r1.218
*** wsdl20.xml	20 Apr 2005 09:48:42 -0000	1.217
--- wsdl20.xml	20 Apr 2005 09:55:09 -0000	1.218
***************
*** 2436,2442 ****
          <p>An Interface Operation component describes an operation
          that a given interface supports. An operation is an
!         interaction with the service consisting of a set (ordinary and
          fault) messages exchanged between the service and the other
!         roles involved in the interaction, in particular the client.
          The sequencing and cardinality of the messages
          involved in a particular interaction is governed by the
--- 2436,2442 ----
          <p>An Interface Operation component describes an operation
          that a given interface supports. An operation is an
!         interaction with the service consisting of a set of (ordinary and
          fault) messages exchanged between the service and the other
!         parties involved in the interaction.
          The sequencing and cardinality of the messages
          involved in a particular interaction is governed by the
***************
*** 2552,2570 ****
          <p diff="chg">For each Interface Operation component in the {interface operations}
  	property of an Interface component, the {name} property MUST be unique.</p>
! 
!         <p>Interface Operation components are local to Interface
! 	components; they cannot be referred to by QName, despite
! 	having a {name} property
! 	(see <specref ref='frag-ids' />). That is,
! 	two Interface components whose {name} property share the same namespace name
! 	but with different local names MAY contain
! 	Interface Operation components which share the same {name}
! 	property. Thus, the {name} property
! 	of the Interface Operation components are not sufficient to
! 	uniquely identify an Interface Operation component.
! 	In order to uniquely identify an Interface Operation
! 	component, one must first identify the Interface component (by
! 	QName) and then identify the Interface Operation within that
! 	Interface component (by a further QName).</p>
  
  	<p>In cases where, due to an interface extending one or more
--- 2552,2566 ----
          <p diff="chg">For each Interface Operation component in the {interface operations}
  	property of an Interface component, the {name} property MUST be unique.</p>
!     
!         <p>Interface Operation components are uniquely identified by the
!     the QName of the enclosing Interface component and QName of the
!     Interface Operation component itself.</p>
!     
!         <note><p>Despite having a {name} property, Interface Operation components
!     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>
  
  	<p>In cases where, due to an interface extending one or more
Received on Wednesday, 20 April 2005 09:55:12 UTC

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