- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Mon, 29 Apr 2002 10:18:55 +0200
- To: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
- CC: www-ws-desc@w3.org
Jeff, thanks for the clearer titles, and breaking up issue 6 into manageable pieces. Do you want to update [1] yourself to reflect these changes (as an ed, you should have RW access), or would you prefer me to do it? Obviously, I have a slight preference for the former, but would be willing to do the latter... Jean-Jacques. Jeffrey Schlimmer wrote: > 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 Monday, 29 April 2002 04:19:57 UTC