W3C home > Mailing lists > Public > public-forms@w3.org > July 2008

RE: XForms 1.1: xforms:submission/@mediatype issue

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Fri, 11 Jul 2008 09:54:08 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF40541FDAD@USA7061MS01.na.xerox.net>
To: "Erik Bruchez" <ebruchez@orbeon.com>, "public-forms (new)" <public-forms@w3.org>

Philip Fennel reminds me again that we discussed some related issues in
2007 at his request:
http://lists.w3.org/Archives/Public/www-forms/2007Sep/0006.html
http://lists.w3.org/Archives/Public/www-forms/2007Oct/0017.html 

The summary is that while XForms 1.1 submission/header gives the ability
to set the Accept header of requests, nothing lets you set the accept
header of instance/@src requests; perhaps we need to look at moving
@mediatype to instance?

Leigh.

-----Original Message-----
From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of Erik Bruchez
Sent: Thursday, July 10, 2008 5:33 PM
To: public-forms (new)
Subject: Re: XForms 1.1: xforms:submission/@mediatype issue


Good point about multipart/related. Needs to be discussed.

-Erik

On Jul 10, 2008, at 4:26 PM, Klotz, Leigh wrote:

> I agree it's a restriction that dates back to XForms 1.0, but we need 
> to explore it further before lifting it.  I think there's an issue 
> with multipart/related as well; would submission/mediatype control the

> type of the envelope ("multipart/related") or the XML part 
> ("application/xml")?
>
> -----Original Message-----
> From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
> On Behalf Of Erik Bruchez
> Sent: Thursday, July 10, 2008 4:01 PM
> To: public-forms (new)
> Subject: Re: XForms 1.1: xforms:submission/@mediatype issue
>
>
>> submission/@mediatype was put in to allow SOAP serialization as 
>> text/xml. ; The restriction to XML types was intentional, as we 
>> wanted
>
>> to make as limited a feature as possible in a short time.  A number 
>> of
>
>> issues and use cases have surfaced since then, and we're now ready to

>> begin thinkinga about non-XML serializations, so I think we should 
>> decide on this issue in that context.
>
> There may be a misunderstanding here: we already have non-XML 
> serializations, namely application/x-www-form-urlencoded and 
> multipart/ form-data. In those cases, the source is always an XML 
> document, but the serialization over the wire is not XML.
>
> The @serialization attribute controls which serialization is used.
> That defines an implicit mediatype (application/x-www-form-urlencoded
> and multipart/form-data).
>
> What I am saying is that in those cases, @mediatype should also be 
> usable to set the Content-Type. Doing otherwise seems an unnecessary 
> restriction dating back to XForms 1.0.
>
> -Erik
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way 
> http://www.orbeon.com/
>
>

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/
Received on Friday, 11 July 2008 16:55:05 UTC

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