- From: Roberto Chinnici <rchinnic@dev.w3.org>
- Date: Mon, 02 Aug 2004 16:10:11 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv8551 Modified Files: wsdl20.html wsdl20.xml Log Message: Action items 3 and 5 from the 2004-07-29 concall. Index: wsdl20.html =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v retrieving revision 1.118 retrieving revision 1.119 diff -C2 -d -r1.118 -r1.119 *** wsdl20.html 2 Aug 2004 14:50:54 -0000 1.118 --- wsdl20.html 2 Aug 2004 16:10:09 -0000 1.119 *************** *** 4294,4304 **** MUST be unique. That is, one cannot define multiple bindings for the same operation within a given Binding component.</p> - <p>For each Binding Message Reference in the {message references} - property of a Binding Operation component, there MUST be an - Interface Message Reference with the same {message label} and - {direction} properties in the corresponding Interface Operation. - Note that the converse is not required; i.e., there need not be a - Binding Message Reference corresponding to each Interface Message - Reference in the Interface Operation component.</p> </div> <div class="div3"> --- 4294,4297 ---- *************** *** 6120,6129 **** <h2><a name="language-extensibility" id= "language-extensibility"></a>6. Language Extensibility</h2> ! <p>The schema for WSDL has a two-part extensibility model based on ! namespace-qualified elements and attributes. The extension is ! identified by the qname consisting of its namespace URI and its ! element name. The meaning of the extension SHOULD be defined ! (directly or indirectly) in a document that is available at its ! namespace URI.</p> <div class="div2"> <h3><a name="eii-extensibility" id="eii-extensibility"></a>6.1 --- 6113,6123 ---- <h2><a name="language-extensibility" id= "language-extensibility"></a>6. Language Extensibility</h2> ! <p>In addition to extensibility implied by the Feature and Property ! components described above, the schema for WSDL has a two-part ! extensibility model based on namespace-qualified elements and ! attributes. An extension is identified by the qname consisting of ! its namespace URI and its element name. The meaning of an extension ! SHOULD be defined (directly or indirectly) in a document that is ! available at its namespace URI.</p> <div class="div2"> <h3><a name="eii-extensibility" id="eii-extensibility"></a>6.1 *************** *** 6184,6192 **** the meaning of any part of the WSDL document. Thus, a NON-mandatory extension merely provides additional description of capabilities of ! the service. Furthermore, any extension that is NOT marked as ! mandatory and which is NOT understood, MUST be ignored. Any NOT ! understood extension attributes MUST be ignored as this ! specification does not provide a mechanism to mark extension ! attributes as being required.</p> <div class="note"> <p class="prefix"><b>Note:</b></p> --- 6178,6184 ---- 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> <div class="note"> <p class="prefix"><b>Note:</b></p> *************** *** 6199,6202 **** --- 6191,6216 ---- document.</p> </div> + <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> + <div class="note"> + <p class="prefix"><b>Note:</b></p> + <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> + </div> </div> <div class="div3"> *************** *** 7507,7510 **** --- 7521,7537 ---- <td colspan="1" rowspan="1">20040802</td> <td colspan="1" rowspan="1">RRC</td> + <td colspan="1" rowspan="1">Removed paragraph added per resolution + of issue 211 (undone per action item 5 of the 2004-07-29 + concall).</td> + </tr> + <tr> + <td colspan="1" rowspan="1">20040802</td> + <td colspan="1" rowspan="1">RRC</td> + <td colspan="1" rowspan="1">Added clarification on the meaning of + required language extensions.</td> + </tr> + <tr> + <td colspan="1" rowspan="1">20040802</td> + <td colspan="1" rowspan="1">RRC</td> <td colspan="1" rowspan="1">Added operation name requirement to the Interface component section.</td> Index: wsdl20.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v retrieving revision 1.129 retrieving revision 1.130 diff -C2 -d -r1.129 -r1.130 *** wsdl20.xml 2 Aug 2004 14:50:54 -0000 1.129 --- wsdl20.xml 2 Aug 2004 16:10:09 -0000 1.130 *************** *** 3833,3845 **** component. </p> - - <p>For each Binding Message Reference in the {message - references} property of a Binding Operation component, there - MUST be an Interface Message Reference with the same {message - label} and {direction} properties in the corresponding Interface - Operation. Note that the converse is not required; i.e., there - need not be a Binding Message Reference corresponding to each - Interface Message Reference in the Interface Operation - component.</p> </div3> --- 3833,3836 ---- *************** *** 5549,5557 **** <div1 id="language-extensibility"> <head>Language Extensibility</head> ! <p> ! The schema for WSDL has a two-part extensibility model based on ! namespace-qualified elements and attributes. ! The extension is identified by the qname consisting of its ! namespace URI and its element name. The meaning of the extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace URI. --- 5540,5550 ---- <div1 id="language-extensibility"> <head>Language Extensibility</head> ! ! <p> ! In addition to extensibility implied by the Feature and Property ! components described above, the schema for WSDL has a two-part ! extensibility model based on namespace-qualified elements and attributes. ! An extension is identified by the qname consisting of its ! namespace URI and its element name. The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace URI. *************** *** 5626,5639 **** <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. Furthermore, any ! extension that is NOT marked as mandatory and which is NOT ! understood, MUST be ignored. Any NOT understood extension ! attributes MUST be ignored as this specification does not ! provide a mechanism to mark extension attributes as being ! required. ! </p> <note> --- 5619,5629 ---- <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> <note> *************** *** 5648,5651 **** --- 5638,5669 ---- </note> + <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> + + <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> + </note> + </div3> *************** *** 6995,6998 **** --- 7013,7027 ---- <td>20040802</td> <td>RRC</td> + <td>Removed paragraph added per resolution of issue 211 (undone per action + item 5 of the 2004-07-29 concall).</td> + </tr> + <tr> + <td>20040802</td> + <td>RRC</td> + <td>Added clarification on the meaning of required language extensions.</td> + </tr> + <tr> + <td>20040802</td> + <td>RRC</td> <td>Added operation name requirement to the Interface component section.</td> </tr>
Received on Monday, 2 August 2004 12:10:38 UTC