2002/ws/desc/wsdl20 wsdl20.xml,1.130,1.131

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

Modified Files:
	wsdl20.xml 
Log Message:
Clean-up


Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.130
retrieving revision 1.131
diff -C2 -d -r1.130 -r1.131
*** wsdl20.xml	2 Aug 2004 16:10:09 -0000	1.130
--- wsdl20.xml	2 Aug 2004 16:13:33 -0000	1.131
***************
*** 1,3 ****
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
--- 1,3 ----
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
***************
*** 5619,5627 ****
  
  	  <p>
!           An extension that is NOT marked as mandatory MUST NOT invalidate the 
!           meaning of any part of the WSDL document. Thus, a NON-mandatory extension 
!           merely provides additional description of capabilities of the 
!           service. This specification does not provide a mechanism to mark 
!           extension attributes as being required. Therefore, all extension attributes 
            are NON-mandatory.	  
            </p>
--- 5619,5627 ----
  
  	  <p>
!           An extension that is NOT marked as mandatory MUST NOT invalidate the 
!           meaning of any part of the WSDL document. Thus, a NON-mandatory extension 
!           merely provides additional description of capabilities of the 
!           service. This specification does not provide a mechanism to mark 
!           extension attributes as being required. Therefore, all extension attributes 
            are NON-mandatory.	  
            </p>
***************
*** 5639,5655 ****
  
  	<p>
!         If a WSDL document declares an extension, Feature or Property as optional 
!         (i.e., NON-mandatory), then the provider agent MUST NOT assume that the 
!         requester agent supports that extension, Feature or Property, _unless_ the 
!         provider agent knows (through some other means) that the requester agent 
!         has in fact elected to engage and support that extension, Feature or 
!         Property.
  	</p>
! 
  	<p>
!         On the other hand, a requester agent MAY engage an extension, Feature or 
!         Property that is declared as optional in the WSDL document. Therefore, the 
!         provider agent MUST support every extension, Feature or Property that is 
!         declared as optional in the WSDL document, in addition to supporting every 
          extension, Feature or Property that is declared as mandatory.
  	</p>
--- 5639,5655 ----
  
  	<p>
!         If a WSDL document declares an extension, Feature or Property as optional 
!         (i.e., NON-mandatory), then the provider agent MUST NOT assume that the 
!         requester agent supports that extension, Feature or Property, <emph>unless</emph> the 
!         provider agent knows (through some other means) that the requester agent 
!         has in fact elected to engage and support that extension, Feature or 
!         Property.
  	</p>
! 
  	<p>
!         On the other hand, a requester agent MAY engage an extension, Feature or 
!         Property that is declared as optional in the WSDL document. Therefore, the 
!         provider agent MUST support every extension, Feature or Property that is 
!         declared as optional in the WSDL document, in addition to supporting every 
          extension, Feature or Property that is declared as mandatory.
  	</p>
***************
*** 5657,5665 ****
  	<note>
  	<p>
!         If finer-grain, direction-sensitive control of extensions, Features or 
!         Properties is desired, then such extensions, Features or Properties may be 
!         designed in a direction-sensitive manner (from requester or from provider) 
!         so that either direction may be separately marked required or 
!         optional. For example, instead of defining a single extension that governs 
          both directions, two extensions could be defined -- one for each direction.
  	</p>
--- 5657,5665 ----
  	<note>
  	<p>
!         If finer-grain, direction-sensitive control of extensions, Features or 
!         Properties is desired, then such extensions, Features or Properties may be 
!         designed in a direction-sensitive manner (from requester or from provider) 
!         so that either direction may be separately marked required or 
!         optional. For example, instead of defining a single extension that governs 
          both directions, two extensions could be defined -- one for each direction.
  	</p>

Received on Monday, 2 August 2004 12:13:57 UTC