- From: John Boyer <boyerj@ca.ibm.com>
- Date: Fri, 8 Aug 2008 16:23:36 -0700
- To: public-forms <public-forms@w3.org>
- Message-ID: <OFD35F1F1B.E74B6F81-ON8825749F.007F2C5B-8825749F.00808153@ca.ibm.com>
An updated editor's draft of XForms 1.1 is now available from the working group home page. It contains the change requested by the working group to SOAP submission. However, the focus of discussion by the working group was on the charset placed into the Accept header, which is specific to the GET operation. But the same charset operations happen for the Content-Type header in the POST case, so I assumed it was appropriate to make the analogous change there. This affects the test suite. Also, it should be clear that, due to this change, the Accept header (get) and the Content-type header (post) will *always* have a charset MIME parameter because the encoding attribute has a default of UTF-8. I don't think this is a problem, just an observation that hopefully everyone else also doesn't think is a problem. Cheers, John M. Boyer, Ph.D. Senior Technical Staff Member Lotus Forms Architect and Researcher 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 Friday, 8 August 2008 23:24:22 UTC