- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Sun, 26 Apr 2020 22:27:53 +0200
- To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
So, reminder: @serialization is not meaningful for some values of @method. Looking at the table at https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Submission_Protocols 1) Any method that supplies the data as part of the URL (and therefore has a default of application/x-www-form-urlencoded) should only be allowed to use that, since specifying something else has no meaning. You can't do a GET with serialization application/xml. 2) multipart-post, form-data-post, and urlencoded-post all specify the serialization in the method, so there's no point in using @serialization, since otherwise you could have just used method="post". 3) This only leaves the other two (put and post), which have a default of application/xml. So my proposal is to say that @serialization only applies to those two cases, since only for those two does it make any sense. Steven On Wed, 22 Apr 2020 15:03:42 +0200, XForms Users Community Group Issue Tracker <sysbot+tracker@w3.org> wrote: > ACTION-2281: Fix description of @serialization > > https://www.w3.org/2005/06/tracker/xforms/actions/2281 > > Assigned to: Steven Pemberton
Received on Sunday, 26 April 2020 20:28:09 UTC