W3C home > Mailing lists > Public > public-forms@w3.org > June 2009

Re: Modification of upload handling on multipart submissions also seems unnecessary

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Mon, 1 Jun 2009 14:43:24 -0700
Message-Id: <4E0CAC9D-EA54-45E5-8991-B2FA361A4D4D@orbeon.com>
To: Forms WG <public-forms@w3.org>
John & all,

Regarding these upload-related actions:

http://lists.w3.org/Archives/Public/public-forms/2009Apr/att-0010/2009-04-22.html#ACTION2
http://lists.w3.org/Archives/Public/public-forms/2009Apr/att-0003/2009-04-01.html#ACTION1

I think that the note under "8.1.6 The upload Element", namely:

   "Implementors note that upload must associate the binary content,  
mediatype, and filename
    with that URI for 11.9.6 Serialization as multipart/related and  
11.9.7 Serialization as
    multipart/form-data serialization."

is enough to go to PR. At least, I can see better now how we can  
implement something which
works cross-implementations.

In the future, we might need finer-grained control on multipart  
submissions, but that is
another story.

-Erik

On May 26, 2009, at 10:29 PM, John Boyer wrote:

>
> I have an action item:
> http://lists.w3.org/Archives/Public/public-forms/2009Apr/att-0003/2009-04-01.html#ACTION1
>
> Given the implementation requirements of upload, which associates  
> knowledge of filename and mediatype with the URI of the file, it is  
> not clear why it is necessary to make this change, esp. at this late  
> date.  Even if setvalue is used to change a node, it is either  
> changed to another URI that has an associated filename and  
> mediatype, or it isn't.
>
> The submission serialization appears to be based on filename and  
> mediatype associated with the URI.  These are also placed in data  
> nodes indicated by the upload filename and mediatype elements, if  
> specified, but it is the metadata associated with the URI at the  
> time of submission that feeds the multipart serialization.  If the  
> filename and mediatype data nodes have gotten out of synch, this is  
> the problem of the form author who decided to do a setvalue on the  
> node to which the upload is bound.
>
> This is a more elaborated explanation of why I don't think we need  
> to implement the following action item:
> http://lists.w3.org/Archives/Public/public-forms/2009Apr/att-0010/2009-04-22.html#ACTION2
>
> John M. Boyer, Ph.D.
> STSM, Interactive Documents and Web 2.0 Applications
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@ca.ibm.com
>
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/
Received on Monday, 1 June 2009 21:44:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:51 UTC