- From: Asir Vedamuthu <asirveda@microsoft.com>
- Date: Mon, 12 Sep 2005 16:30:31 -0700
- To: <www-ws-desc@w3.org>
> Action Item: Asir to put such a proposal together (making {soap mep} > optional property, specify the error for SOAP 1.2 In brief, LC321 [1] points out that LC98 [2] resolution fell through. For LC98, WG decided to move the statement - 'it is an error if {soap mep} property does not have a value' - from section 5.8.2 to SOAP 1.2 Binding section [2]. This e-mail is a concrete proposal to resolve LC321. There are two parts, (a) CHANGE - Section 5.8.2 Relationship to WSDL Component Model FROM "{soap mep} REQUIRED. A xs:anyURI, which is an absolute IRI as defined by [IETF RFC 3987], to the Binding Operation component. The value of this property identifies the SOAP Message Exchange Pattern (MEP) for this specific operation. If no specific value is assigned, then the value assigned by the default rules apply (for SOAP 1.2, see 5.11.3 Default Binding Rules). It is an error for this property to not have a value (which MAY happen if the default rules are not applicable)." TO "{soap mep} OPTIONAL. An xs:anyURI, which is an absolute IRI as defined by [IETF RFC 3987], to the Binding Operation component. The value of this property identifies the SOAP Message Exchange Pattern (MEP) for this specific operation. If no specific value is assigned, then a value may be assigned via default binding rules (for SOAP 1.2, see 5.11.3 Default Binding Rules)." (b) CHANGE - Section 5.11.2 Description FROM Default rules in section 5.11.3 Default Binding Rules define the relationship between SOAP message exchange patterns defined in [SOAP 1.2 Part 2: Adjuncts] and WSDL message exchange patterns defined in 2. Predefined Message Exchange Patterns. TO Default rules in section 5.11.3 Default Binding Rules define the relationship between SOAP message exchange patterns defined in [SOAP 1.2 Part 2: Adjuncts] and WSDL message exchange patterns defined in 2. Predefined Message Exchange Patterns. It is an error if the Binding Operation component's {soap mep} property is either absent or has no value, when the Interface Operation component's {message exchange pattern} property has a value other than "http://www.w3.org/2005/08/wsdl/in-out". [1] http://www.w3.org/2002/ws/desc/5/lc-issues/#LC321 [2] http://www.w3.org/2002/ws/desc/4/lc-issues/#LC98 Regards, Asir S Vedamuthu, Microsoft
Received on Monday, 12 September 2005 23:30:41 UTC