- From: Roberto Chinnici via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 01 Mar 2005 14:45:10 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv26608 Modified Files: wsdl20.html wsdl20.xml Log Message: Implemented LC48a. Index: wsdl20.html =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v retrieving revision 1.152 retrieving revision 1.153 diff -C2 -d -r1.152 -r1.153 *** wsdl20.html 24 Feb 2005 01:57:14 -0000 1.152 --- wsdl20.html 1 Mar 2005 14:45:07 -0000 1.153 *************** *** 4,8 **** <head> <meta name="generator" content= ! "HTML Tidy for Linux/x86 (vers 1st February 2005), see www.w3.org" /> <meta http-equiv="Content-Type" content= "text/html; charset=utf-8" /> --- 4,8 ---- <head> <meta name="generator" content= ! "HTML Tidy for Cygwin (vers 1st August 2004), see www.w3.org" /> <meta http-equiv="Content-Type" content= "text/html; charset=utf-8" /> *************** *** 159,181 **** 1.1 <a href="#intro_ws">Web Service</a><br /> ! 1.2 <a href="#notation">Notational Conventions</a><br /> ! 1.2.1 <a href= "#rfc2119keywords">RFC 2119 Keywords</a><br /> ! 1.2.2 <a href= "#rfc3986namespaces">RFC 3986 Namespaces</a><br /> ! 1.2.3 <a href= "#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br /> ! 1.2.4 <a href= "#xmlinfosetproperties">XML Infomation Set Properties</a><br /> ! 1.2.5 <a href= "#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br /> ! 1.2.6 <a href= "#znotation">Z Notation</a><br /> ! 1.2.7 <a href= "#bnfpseudoschemas">BNF Pseudo-Schemas</a><br /> ! 1.3 <a href="#terminology">WSDL Terminology</a><br /> 2. <a href="#component_model">Component Model</a><br /> --- 159,183 ---- 1.1 <a href="#intro_ws">Web Service</a><br /> ! 1.2 <a href="#meaning">The Meaning of a ! Service Description</a><br /> ! 1.3 <a href="#notation">Notational Conventions</a><br /> ! 1.3.1 <a href= "#rfc2119keywords">RFC 2119 Keywords</a><br /> ! 1.3.2 <a href= "#rfc3986namespaces">RFC 3986 Namespaces</a><br /> ! 1.3.3 <a href= "#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br /> ! 1.3.4 <a href= "#xmlinfosetproperties">XML Infomation Set Properties</a><br /> ! 1.3.5 <a href= "#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br /> ! 1.3.6 <a href= "#znotation">Z Notation</a><br /> ! 1.3.7 <a href= "#bnfpseudoschemas">BNF Pseudo-Schemas</a><br /> ! 1.4 <a href="#terminology">WSDL Terminology</a><br /> 2. <a href="#component_model">Component Model</a><br /> *************** *** 607,620 **** describing the concrete details of a service description. It also defines criteria for a conformant processor of this language. The ! <em>WSDL Version 2.0 Part 2: Message Exchange Patterns</em> specification [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined ! Extensions</a></cite>] defines the sequence and cardinality of ! abstract messages sent or received by an operation. The <em>WSDL ! Version 2.0 Part 3: Bindings</em> specification [<cite><a href= ! "#WSDL-PART3">WSDL 2.0 Bindings</a></cite>] defines a language for ! describing such concrete details for SOAP 1.2 [<cite><a href= ! "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>], ! HTTP [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>] and MIME ! [<cite><a href="#RFC2045">IETF RFC 2045</a></cite>].</p> <div class="div2"> <h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3> --- 609,623 ---- describing the concrete details of a service description. It also defines criteria for a conformant processor of this language. The ! <em>WSDL Version 2.0 Part 2: Predefined Extensions</em> specification [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined ! Extensions</a></cite>] describes extensions for Message Exchange ! Patterns, features, SOAP modules and bindings of features. The ! <em>WSDL Version 2.0 Part 3: Bindings</em> specification ! [<cite><a href="#WSDL-PART3">WSDL 2.0 Bindings</a></cite>] defines ! a language for describing such concrete details for SOAP 1.2 ! [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging ! Framework</a></cite>], HTTP [<cite><a href="#RFC2616">IETF RFC ! 2616</a></cite>] and MIME [<cite><a href="#RFC2045">IETF RFC ! 2045</a></cite>].</p> <div class="div2"> <h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3> *************** *** 640,644 **** </div> <div class="div2"> ! <h3><a name="notation" id="notation"></a>1.2 Notational Conventions</h3> <p>All parts of this specification are normative, with the --- 643,667 ---- </div> <div class="div2"> ! <h3><a name="meaning" id="meaning"></a>1.2 The Meaning of a Service ! Description</h3> ! <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 document describes. For example, as ! further explained in section <a href="#mandatoryext"><b>6.1.1 ! Mandatory extensions</b></a>, if the WSDL document specifies a ! particular optional extension, the functionality implied by that ! extension is only optional to the client. But it needs to be ! supported by the Web service.</p> ! <p>A WSDL 2.0 interface describes potential interaction with a ! service -not required interaction. The declaration of an operation ! in a WSDL 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> ! </div> ! <div class="div2"> ! <h3><a name="notation" id="notation"></a>1.3 Notational Conventions</h3> <p>All parts of this specification are normative, with the *************** *** 646,650 **** explicitly marked as “Non-Normative”.</p> <div class="div3"> ! <h4><a name="rfc2119keywords" id="rfc2119keywords"></a>1.2.1 RFC 2119 Keywords</h4> <p>The keywords “MUST”, “MUST NOT”, “EQUIRED”, “SHALL”, “SHALL --- 669,673 ---- explicitly marked as “Non-Normative”.</p> <div class="div3"> ! <h4><a name="rfc2119keywords" id="rfc2119keywords"></a>1.3.1 RFC 2119 Keywords</h4> <p>The keywords “MUST”, “MUST NOT”, “EQUIRED”, “SHALL”, “SHALL *************** *** 654,658 **** </div> <div class="div3"> ! <h4><a name="rfc3986namespaces" id="rfc3986namespaces"></a>1.2.2 RFC 3986 Namespaces</h4> <p>Namespace names of the general form:</p> --- 677,681 ---- </div> <div class="div3"> ! <h4><a name="rfc3986namespaces" id="rfc3986namespaces"></a>1.3.2 RFC 3986 Namespaces</h4> <p>Namespace names of the general form:</p> *************** *** 669,673 **** </div> <div class="div3"> ! <h4><a name="nsprefixes" id="nsprefixes"></a>1.2.3 Prefixes and Namespaces Used in This Specification</h4> <p>This specification uses predefined namespace prefixes --- 692,696 ---- </div> <div class="div3"> ! <h4><a name="nsprefixes" id="nsprefixes"></a>1.3.3 Prefixes and Namespaces Used in This Specification</h4> <p>This specification uses predefined namespace prefixes *************** *** 744,748 **** <div class="div3"> <h4><a name="xmlinfosetproperties" id= ! "xmlinfosetproperties"></a>1.2.4 XML Infomation Set Properties</h4> <p>This specification refers to properties in the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. --- 767,771 ---- <div class="div3"> <h4><a name="xmlinfosetproperties" id= ! "xmlinfosetproperties"></a>1.3.4 XML Infomation Set Properties</h4> <p>This specification refers to properties in the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. *************** *** 752,756 **** <div class="div3"> <h4><a name="wsdlcomponentmodelproperties" id= ! "wsdlcomponentmodelproperties"></a>1.2.5 WSDL Component Model Properties</h4> <p>This specification defines and refers to properties in the WSDL --- 775,779 ---- <div class="div3"> <h4><a name="wsdlcomponentmodelproperties" id= ! "wsdlcomponentmodelproperties"></a>1.3.5 WSDL Component Model Properties</h4> <p>This specification defines and refers to properties in the WSDL *************** *** 760,764 **** </div> <div class="div3"> ! <h4><a name="znotation" id="znotation"></a>1.2.6 Z Notation</h4> <p>This specification uses Z Notation [<cite><a href= "#ZNotationReferenceManual">Z Notation Reference Manual</a></cite>] --- 783,787 ---- </div> <div class="div3"> ! <h4><a name="znotation" id="znotation"></a>1.3.6 Z Notation</h4> <p>This specification uses Z Notation [<cite><a href= "#ZNotationReferenceManual">Z Notation Reference Manual</a></cite>] *************** *** 773,782 **** [<span class="zi">ID</span>], which conflicts with their use to denote XML Information Set properties <a href= ! "#xmlinfosetproperties"><b>1.2.4 XML Infomation Set Properties</b></a>. Also, in Z Notation, curly brackets are used to denote set display and set comprehension, e.g. {1<span class= "zprefix">,</span> 2<span class="zprefix">,</span> 3}, which conflicts with their use to denote WSDL Component Model properties ! <a href="#wsdlcomponentmodelproperties"><b>1.2.5 WSDL Component Model Properties</b></a>. However, the intended meaning of square and curly brackets should be clear from their context and this --- 796,805 ---- [<span class="zi">ID</span>], which conflicts with their use to denote XML Information Set properties <a href= ! "#xmlinfosetproperties"><b>1.3.4 XML Infomation Set Properties</b></a>. Also, in Z Notation, curly brackets are used to denote set display and set comprehension, e.g. {1<span class= "zprefix">,</span> 2<span class="zprefix">,</span> 3}, which conflicts with their use to denote WSDL Component Model properties ! <a href="#wsdlcomponentmodelproperties"><b>1.3.5 WSDL Component Model Properties</b></a>. However, the intended meaning of square and curly brackets should be clear from their context and this *************** *** 799,803 **** </div> <div class="div3"> ! <h4><a name="bnfpseudoschemas" id="bnfpseudoschemas"></a>1.2.7 BNF Pseudo-Schemas</h4> <p>Pseudo-schemas are provided for each component, before the --- 822,826 ---- </div> <div class="div3"> ! <h4><a name="bnfpseudoschemas" id="bnfpseudoschemas"></a>1.3.7 BNF Pseudo-Schemas</h4> <p>Pseudo-schemas are provided for each component, before the *************** *** 824,828 **** </div> <div class="div2"> ! <h3><a name="terminology" id="terminology"></a>1.3 WSDL Terminology</h3> <p>This section describes the terms and concepts introduced in Part --- 847,851 ---- </div> <div class="div2"> ! <h3><a name="terminology" id="terminology"></a>1.4 WSDL Terminology</h3> <p>This section describes the terms and concepts introduced in Part *************** *** 6287,6290 **** --- 6310,6333 ---- means) that the client has in fact elected to engage and support that extension, Feature or Property.</p> + <div class="note"> + <p class="prefix"><b>Note:</b></p> + <p>A key purpose of an extension is to formally indicate (i.e., in + a machine-processable way) that a particular feature or convention + is supported or required. This enables toolkits that understand the + extension to engage it automatically, while toolkits that do not + yet understand a required extension may be able to flag it to an + operator for manual support.</p> + <p>If a Web service requires the client to follow a particular + convention that is likely to be automatable in WSDL toolkits, then + that convention SHOULD be indicated in the WSDL document as a + wsdl:required extension, rather than just being conveyed out of + band, even if that convention is not currently implemented in WSDL + toolkits.</p> + <p>This practice will help prevent interoperability problems that + could arise if one toolkit requires a particular convention that is + not indicated in the WSDL document, while another toolkit does not + realize that that convention is required. It will also help + facilitate future automatic processing by WSDL toolkits.</p> + </div> <p>On the other hand, a client MAY engage an extension, Feature or Property that is declared as optional in the WSDL document. *************** *** 6349,6352 **** --- 6392,6407 ---- <div class="note"> <p class="prefix"><b>Note:</b></p> + <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 supercede what the WSDL document + indicated. For example, the WSDL 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> + </div> + <div class="note"> + <p class="prefix"><b>Note:</b></p> <p>Authors of extensibility elements should avoid altering the existing semantics in ways that are likely to confuse users.</p> *************** *** 7754,7757 **** --- 7809,7835 ---- </tr> <tr> + <td rowspan="1" colspan="1">20050228</td> + <td rowspan="1" colspan="1">JJM</td> + <td rowspan="1" colspan="1"><a href= + "http://lists.w3.org/Archives/Public/www-ws-desc/2005Feb/0006.html"> + X</a> and <a href= + "http://lists.w3.org/Archives/Public/www-ws-desc/2004Dec/0022.html"> + Y</a>: Added note clarifying extensibility semantics.</td> + </tr> + <tr> + <td rowspan="1" colspan="1">20050228</td> + <td rowspan="1" colspan="1">JJM</td> + <td rowspan="1" colspan="1"><a href= + "http://lists.w3.org/Archives/Public/www-ws-desc/2005Feb/0006.html"> + X</a>: Added note clarifying extensibility semantics.</td> + </tr> + <tr> + <td rowspan="1" colspan="1">20050228</td> + <td rowspan="1" colspan="1">JJM</td> + <td rowspan="1" colspan="1"><a href= + "http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0026.html"> + X</a>: Added text on the meaning of a service description.</td> + </tr> + <tr> <td rowspan="1" colspan="1">20050218</td> <td rowspan="1" colspan="1">RRC</td> *************** *** 8694,8698 **** <td rowspan="1" colspan="1">MJG</td> <td rowspan="1" colspan="1">Added text to <a href= ! "#notation"><b>1.2 Notational Conventions</b></a> regarding normative nature of schema and validity of WSDL documents</td> </tr> --- 8772,8776 ---- <td rowspan="1" colspan="1">MJG</td> <td rowspan="1" colspan="1">Added text to <a href= ! "#notation"><b>1.3 Notational Conventions</b></a> regarding normative nature of schema and validity of WSDL documents</td> </tr> Index: wsdl20.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v retrieving revision 1.181 retrieving revision 1.182 diff -C2 -d -r1.181 -r1.182 *** wsdl20.xml 28 Feb 2005 17:23:39 -0000 1.181 --- wsdl20.xml 1 Mar 2005 14:45:08 -0000 1.182 *************** *** 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' ?> *************** *** 110,116 **** It also defines criteria for a conformant processor of this language. The <emph>WSDL Version 2.0 ! Part 2: Message Exchange Patterns</emph> specification <bibref ref="WSDL-PART2"/> ! defines the sequence and cardinality of abstract ! messages sent or received by an operation. The <emph>WSDL Version 2.0 Part 3: Bindings</emph> specification <bibref ref="WSDL-PART3"/> defines a language for describing such concrete details for SOAP 1.2 <bibref --- 110,116 ---- It also defines criteria for a conformant processor of this language. The <emph>WSDL Version 2.0 ! Part 2: Predefined Extensions</emph> specification <bibref ref="WSDL-PART2"/> ! describes extensions for Message Exchange Patterns, features, SOAP modules ! and bindings of features. The <emph>WSDL Version 2.0 Part 3: Bindings</emph> specification <bibref ref="WSDL-PART3"/> defines a language for describing such concrete details for SOAP 1.2 <bibref
Received on Tuesday, 1 March 2005 14:45:11 UTC