- From: David Orchard <dorchard@bea.com>
- Date: Wed, 21 Apr 2004 14:10:40 -0700
- To: <www-ws-desc@w3.org>
A revised issue 54 resolution text, after Jonathan pointed out that the current solution isn't extensible. I have added PUT, DELETE, and name extensbility. It proposes that a bare name name must have xml inputs and outputs, and qname name is undefined but allowed. Text for 3.1.1 table. Table 3-1. Methods, serialization format, and HTTP methods Method Input serialization Output serialization HTTP Method Message Patterns Operation Style "post" application/xml application/xml HTTP POST In-Only, Robust In-Only, In-Out any "get" application/x-www-form-urlencoded application/xml HTTP GET In-Only, Robust In-Only, In-Out URI style "form-data-post" multipart/form-data application/xml HTTP POST In-Only, Robust In-Only, In-Out Multipart style "put" application/xml application/xml HTTP PUT In-Only, Robust In-Only, In-Out any "delete" application/x-www-form-urlencoded application/xml HTTP DELETE In-Only, Robust In-Only, In-Out URI style (any) application/xml application/xml HTTP (any) In-Only, Robust In-Only, In-Out any (any) any QNAME with a prefix implementation-defined implementation-defined The methods "multipart-post", and "urlencoded-post", as defined in "Submission Options" ([XForms 1.0], Section 11.2) are not supported by this specification. Cheers, Dave
Received on Wednesday, 21 April 2004 17:11:31 UTC