- From: John Boyer <boyerj@ca.ibm.com>
- Date: Tue, 26 May 2009 22:29:17 -0700
- To: public-forms@w3.org
- Message-ID: <OFE1DE54A3.A3BC2DBE-ON882575C3.001C6261-882575C3.001E1F1D@ca.ibm.com>
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
Received on Wednesday, 27 May 2009 05:29:57 UTC