4430 2007-03-29 17:27:32 +0000 Endpoint address ? and # note 2007-04-26 13:01:14 +0000 1 1 1 Unclassified WSDL Core 2.0 All All CLOSED FIXED http://lists.w3.org/Archives/Member/w3c-ws-desc/2007Mar/0009 resolved P2 normal --- 1 jonathan plh www-ws-desc oldest_to_newest 14594 0 jonathan 2007-03-29 17:27:32 +0000 [[ 2.13.1 The Endpoint Component The properties of the Endpoint component are as follows: * {address} OPTIONAL. An xs:anyURI. This xs:anyURI MUST be an absolute IRI as defined by [IETF RFC 3987]. If present, the value of this attribute represents the network address at which the service indicated by the parent Service component's {interface} property is offered via the binding referred to by the {binding} property. Note that the presence in this property of the characters "?" and "#" can conflict with those potentially added by the mapping to the SOAP-Response message exchange pattern, section 6.8.2, [WSDL 2.0 Adjuncts]. ]] Re the last note, does this not also apply to the HTTP binding? And does this still hold with the resolution of CR157 (and prior related issues)? 14765 1 plh 2007-04-19 14:56:02 +0000 [[ Note that the presence in this property of the characters "?" and "#" can conflict with those potentially added by the mapping to the SOAP-Response message exchange pattern, section 6.8.2, [WSDL 2.0 Adjuncts]. ]] > does this not also apply to the HTTP binding? Yes, it does. In fact, section 6.8.2 isn't about SOAP-Response MEP, but about "6.8.2 Serialization as application/x-www-form-urlencoded", which is linked from section 5.10.4.2 "WSDL In-Out to SOAP SOAP-Response", and other necessary places in the HTTP binding. So I propose the following change: [[ Note that the presence in this property of the characters "?" and "#" can conflict with those potentially added by the query string serialization mechanism, section 6.8.2, Serialization as "application/x-www-form-urlencoded", [WSDL 2.0 Adjuncts]. ]] > And does this still hold with the resolution of CR157 (and prior related issues)? Looking at issue CR157 http://www.w3.org/2002/ws/desc/5/cr-issues/#CR157, this seems about WSDL authors SHOULD encode those characters, as mentioned in section 6.8.1.1. The sentence recommends caution if one does not do so. I believe no further change is necessary. 14772 2 jonathan 2007-04-19 15:38:02 +0000 Philippe's proposal accepted.