- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 12 Apr 2007 15:47:36 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv9343 Modified Files: wsdl20.xml Log Message: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4424 Switched 1.2 <-> 1.3 Index: wsdl20.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v retrieving revision 1.455 retrieving revision 1.456 diff -C 2 -d -r1.455 -r1.456 *** wsdl20.xml 12 Apr 2007 15:43:25 -0000 1.455 --- wsdl20.xml 12 Apr 2007 15:47:33 -0000 1.456 *************** *** 159,162 **** --- 159,185 ---- <!-- +++++++++ --> + <div2 id="meaning"> + <head>The Meaning of a Service Description</head> + + <p>A WSDL 2.0 service description indicates how potential clients are + intended to interact with the described service. It represents an + assertion that the described service fully implements and conforms to + what the WSDL 2.0 document describes. For example, as further + explained in section <specref ref="mandatoryext"/>, + if the WSDL 2.0 document specifies a particular + optional extension, the functionality implied by that extension is only + optional to the client. It must be supported by the Web service.</p> + + <p>A WSDL 2.0 interface describes potential interactions with a Web service, not + required interactions. The declaration of an operation in a WSDL 2.0 + interface is not an assertion that the interaction described by the + operation must occur. Rather it is an assertion that if such an + interaction is (somehow) initiated, then the declared operation + describes how that interaction is intended to occur.</p> + + </div2> + + <!-- +++++++++ --> + <div2 id="markup"> <head>Document Conformance</head> *************** *** 195,221 **** <!-- +++++++++ --> - <div2 id="meaning"> - <head>The Meaning of a Service Description</head> - - <p>A WSDL 2.0 service description indicates how potential clients are - intended to interact with the described service. It represents an - assertion that the described service fully implements and conforms to - what the WSDL 2.0 document describes. For example, as further - explained in section <specref ref="mandatoryext"/>, - if the WSDL 2.0 document specifies a particular - optional extension, the functionality implied by that extension is only - optional to the client. It must be supported by the Web service.</p> - - <p>A WSDL 2.0 interface describes potential interactions with a Web service, not - required interactions. The declaration of an operation in a WSDL 2.0 - interface is not an assertion that the interaction described by the - operation must occur. Rather it is an assertion that if such an - interaction is (somehow) initiated, then the declared operation - describes how that interaction is intended to occur.</p> - - </div2> - - <!-- +++++++++ --> - <div2 id="notation"> <head>Notational Conventions</head> --- 218,221 ----
Received on Thursday, 12 April 2007 15:47:43 UTC