[whatwg] Web Forms 2.0 methods and enctypes

[Ben Meadowcroft]

> -----Original Message-----
> From: whatwg-whatwg.org-bounces at lists.whatwg.org 
> [mailto:whatwg-whatwg.org-bounces at lists.whatwg.org] On Behalf 
> Of Asbjørn Ulsberg
> Sent: 11 July 2004 17:25
> To: Ian Hickson
> Cc: WHAT WG
> Subject: Re: [whatwg] Web Forms 2.0 methods and enctypes
> 
> 
> On Sun, 4 Jul 2004 14:28:19 +0000 (UTC), Ian Hickson 
> <ian at hixie.ch> wrote:
> 
> >> Would it be possible for Web Forms 2.0 to allow at least PUT and 
> >> DELETE
> >> in addition to GET and POST as methods for the <form> element?
> >
> > Already there are defined in depth:
> >
> >    http://whatwg.org/specs/web-forms/current-work/#methodAndEnctypes
> 
> Ah, ok. Great.
> 
> >> Would it also be possible that the Web Forms 2.0 specification 
> >> allowed additional '@enctype' values, like 'application/atom+xml'?
> >
> > If the Atom spec specifies how to convert a Web Forms 2.0 form data 
> > set into an 'application/atom+xml' encoded form data set, 
> then UAs can 
> > implement it.
> 
> Ok, I'll see if I can specify that somehow. What would your initial  
> thoughts be on how to get the WF2 data set into this format:
> 
> 
>    <entry version="0.3"
>      xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-00">
>      <title>Atom 0.3 snapshot</title>
> 
>      <id>tag:example.org,2003:3.2397</id>
>      <issued>2003-12-13T08:29:29-04:00</issued>
>      <modified>2003-12-13T18:30:02Z</modified>
> 
>      <content type="application/xhtml+xml" mode="xml">
>        <div xmlns="http://www.w3.org/1999/xhtml">
>          <h1>Atom 0.3 snapshot!</h1>
>        </div>
>      </content>
>    </entry>
> 
> > Here is one example of such a specification:
> >
> >    http://whatwg.org/specs/web-forms/current-work/#x-www-form-xml
> 
> Ok, this is a very simple serialization; Atom is much more 
> complicated  
> than this. I'm not sure that converting from WF2 data set to Atom is  
> possible. What do you think?

Transforming WF2 data to atom would be a mapping that would be best
defined by the form author surely? Perhaps one way to do this would be to
allow a form submitting x-www-form-xml encoded data to be transformed
using XSLT on the data, this could be done on the server or it could be
done on the client, e.g.

<form
	action="http://example.com/atom.endpoint"
      enctype="application/x-www-form+xml"
	target-enctype="application/atom+xml"
	transformation="http://example.com/atom.transform.wf2"
      method="post">

This would then provide an extensible mechanism for advanced uses of XML
submission in a variety of domain specific XML languages such as atom.

-- 
Ben Meadowcroft
http://www.benmeadowcroft.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3034 bytes
Desc: not available
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20040711/f3f703cc/attachment-0001.bin>