This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4430 - Endpoint address ? and # note
Summary: Endpoint address ? and # note
Status: CLOSED FIXED
Alias: None
Product: WSDL
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: WSDL Mailing List
URL: http://lists.w3.org/Archives/Member/w...
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2007-03-29 17:27 UTC by Jonathan Marsh
Modified: 2007-04-26 13:01 UTC (History)
0 users

See Also:


Attachments

Description Jonathan Marsh 2007-03-29 17:27:32 UTC
[[
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)?
Comment 1 Philippe Le Hegaret 2007-04-19 14:56:02 UTC
[[
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.
Comment 2 Jonathan Marsh 2007-04-19 15:38:02 UTC
Philippe's proposal accepted.