W3C home > Mailing lists > Public > www-forms-editor@w3.org > January 2002


From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 22 Jan 2002 12:53:09 -0800
To: www-forms-editor@w3.org
Message-ID: <20020122125309.A5569@mnot.net>

In the last call draft of XForms 1.0, submitInfo [1] defines the
characteristics of an XForms submission. One of the attributes is:

  method - Optional indicator as to the protocol to be used to
           transmit the serialized instance data.

Possible values include:

 method = "post" | "get" | qname-but-not-ncname : "post"

The exclusion of 'put' from this list limits the power of XForms. PUT
is used to update the state of a resource with a representation; in
other words, if you PUT something somewhere, you can then GET the
same thing from there later. POST is less specific; its semantics are
that of submitting data to a process.

Allowing PUT will enable XForms that can be used to update a site's
content directly, rather than being processed by a script. There is
also the potential for resources which accept both PUT and POST that 
will not be able to fully interoperate with XForms if PUT is not

For more information, see [2].


[1] http://www.w3.org/TR/2002/WD-xforms-20020118/slice3.html#structure-model-submit
[2] http://www.ietf.org/internet-drafts/draft-baker-http-resource-state-model-01.txt

Mark Nottingham
Received on Tuesday, 22 January 2002 15:53:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:38:04 UTC