W3C home > Mailing lists > Public > www-forms@w3.org > September 2008

RE: XForms, the xf:header and the HTTP Accept header.

From: Klotz, Leigh <Leigh.Klotz@XEROX.COM>
Date: Tue, 2 Sep 2008 10:50:12 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF405A56694@USA7061MS01.na.xerox.net>
To: "Philip Fennell" <Philip.Fennell@bbc.co.uk>, <www-forms@w3.org>

Thanks Philip.  Replies below.

>From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On
Behalf Of Philip Fennell
>Sent: Monday, September 01, 2008 6:57 AM
>To: www-forms@w3.org
>Subject: RE: XForms, the xf:header and the HTTP Accept header.
>
>
>Apologies Leigh for the late response, I was on holiday last week and
have only just had the chance to catch-up with your and Aaron's
conversation. Rotten timing or what!
>
>> I'm leaning towards combine="prepend|append|replace|error" and then
we
>need to decide what the default is.
>
>For my two penn'orth I'm quite happy with the 'combine' attribute.
>
>
>I'm sure it's too late to look at this now but I briefly toyed with the
idea of dropping the 'combine' attribute and making the combination of
values explicit by making use of multiple xf:value elements and having
something like a default() function as follows:
>
><xf:header>
>    <xf:name>Accept</xf:name>
>    <xf:value>application/sparql-results+xml;q=0.95</xf:value>
>    <xf:value value="default()/>
>    <xf:value>application/atom+xml;q=0.6</xf:value>
></xf:header>
>
>With this structure you could explicitly prepend, append, a combination
of the two, or just replace; in order to build the header value as you
wish and you wouldn't need the extra 'combine' attribute. However, I'm
not sure what all the consequence would be when creating multiple
headers using the nodeset attribute.

I am concerned this would be hard to implement.  I believe values could
be likely tagged as prepend, append, and replace, but getting at the
default value during xf:header processing, or creating a future object
for it might prove difficult.  I didn't see Aaron comment on this but
I'll ask in my next message, which will be a response to him.

>Is the assumption that where multiple xf:value elements are used, any
delimiting characters like commas are added when the HTTP request is
built?

Yes, that would be the proposal.
Leigh.
Received on Tuesday, 2 September 2008 17:51:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:14 GMT