- From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
- Date: Fri, 26 Apr 2002 19:00:29 -0700
- To: <www-ws-desc@w3.org>
The following is a list of WSDL issues for non-SOAP HTTP binding culled from [1]. For the sake of clarity, I revised the issue titles and broke out Issue 6 into separate parts. To get things going, I'm going to start up a thread for one or two of these. 6a. Define encoding of complex types in a request URL 6d. Define encoding for URL-sensitive characters in a request URL 41. Define encoding of attributes in a request URL 6b. Define encoding for characters outside ASCII in a request URL 6e. Define behavior if an http:urlReplacement search pattern does not have a corresponding named part in the message 53. Allow operations within a binding to use different HTTP methods 54. Allow binding to any HTTP method 55. Define binding to HTTP headers 56. Define means to specify an authentication requirement FYI, the following issues are listed in [1] as related to the non-SOAP HTTP binding, but they do not seem to be specific to that binding. 6c. Allow a part to reference a global element declaration (GED) versus type 52. Allow operation addresses to be absolute --Jeff [1] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.xml
Received on Friday, 26 April 2002 22:04:16 UTC