- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 12 Feb 2007 14:01:58 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv11743 Modified Files: wsdl20.xml Log Message: Fix further (and final) occurrence of "feature". Index: wsdl20.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v retrieving revision 1.427 retrieving revision 1.428 diff -C 2 -d -r1.427 -r1.428 *** wsdl20.xml 12 Feb 2007 13:59:50 -0000 1.427 --- wsdl20.xml 12 Feb 2007 14:01:56 -0000 1.428 *************** *** 9294,9304 **** ! <note><p>However, once the client and service both know that an optional feature has been engaged (because the service has received a message explicitly ! engaging that feature, for example), then the semantics of that feature supersede what the WSDL 2.0 document indicated. For example, the WSDL 2.0 document may have specified an XML message schema to be used, but also ! indicated an optional security feature that encrypts the messages. If ! the security feature is engaged, then the encrypted messages will no longer conform to the specified message schema (until they are decrypted).</p></note> --- 9294,9304 ---- ! <note><p>However, once the client and service both know that an optional extension has been engaged (because the service has received a message explicitly ! engaging that extension, for example), then the semantics of that extension supersede what the WSDL 2.0 document indicated. For example, the WSDL 2.0 document may have specified an XML message schema to be used, but also ! indicated an optional security extension that encrypts the messages. If ! the security extension is engaged, then the encrypted messages will no longer conform to the specified message schema (until they are decrypted).</p></note>
Received on Monday, 12 February 2007 14:02:05 UTC