Re: Revised proposed Issue 54 resolution

Looks good for the most part, but shouldn't more specific XML media
types (*/*+xml) be supported, even if you're only describing XML
in/out?

I know this was part of Hugo's proposal, I just wasn't able to respond
at the time he made it.

Mark.

On Wed, Apr 21, 2004 at 02:10:40PM -0700, David Orchard wrote:
> 
> 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
> 

-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Received on Wednesday, 21 April 2004 20:22:24 UTC