W3C

- DRAFT -

Weekly Forms WG Teleconference

01 Apr 2009

Agenda

See also: IRC log

Attendees

Present
John_Boyer, unl, wiecha, prb, Leigh_Klotz, ebruchez
Regrets
Nick, Steven
Chair
John
Scribe
Leigh

Contents


 

 

<John_Boyer> Scribe: Leigh

<John_Boyer> scribenick: klotz

http://xformstest.org/2009-03-31

http://xformstest.org/2009-03-31.txt

<John_Boyer> http://www.w3.org/MarkUp/Forms/specs/XForms1.2/XFormsForHTML/index-all.html#form-containment

<John_Boyer> http://www.w3.org/MarkUp/Forms/specs/XForms1.2/XFormsForHTML/index-all.html#intro-reading

<wiecha> http://ubiquity-xforms.googlecode.com/svn-history/r2616/changes/cwiecha@gmail.com/svg-custom-repeat/samples/svg/svg-loan.xhtml

<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2009Mar/0021.html

<John_Boyer> http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#serialize-form-data

<John_Boyer> Element nodes of any datatype populated by upload are serialized as the specified binary content. In the case of xsd:anyURI and derived types, the serialization content is obtained from the URI. For xsd:base64Binary, xsd:hexBinary, and derived types, the serialization content is obtained by decoding the element string value.

<John_Boyer> fifth bullet is where the problem is

<John_Boyer> quoted above

<John_Boyer> It says element nodes of any datatype populated by upload...

<John_Boyer> rather than element nodes which *are* populated by upload

<John_Boyer> http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#serialize-form-data

<John_Boyer> Leigh, are you entering that action item into your minutes, or here?

<scribe> ACTION: John Boyer to clarify http://www.w3.org/TR/xforms/#serialize-multipart and http://www.w3.org/TR/xforms/#serialize-form-data to show that for upload content serialization to occur, the node must have been directly populated by an upload; subsequent setvalue operations will negate the upload; a node copied by some operation such as insert or select/copy will not copy the uploaded content, only the lexical value of the node. [recorded in http://www.w3.org/2009/04/01-forms-minutes.html#action01]

<trackbot> Sorry, amibiguous username (more than one match) - John

<trackbot> Try using a different identifier, such as family name or username (eg. jkugelma, jboyer)

RESOLUTION: We agree to consider control of serialization of attachments in a future version of XForms.

<John_Boyer> RESOLUTION: Working group agrees to consider for a future version of XForms how to better control serialization of attachments in multipart-formdata submission

Summary of Action Items

[NEW] ACTION: John Boyer to clarify http://www.w3.org/TR/xforms/#serialize-multipart and http://www.w3.org/TR/xforms/#serialize-form-data to show that for upload content serialization to occur, the node must have been directly populated by an upload; subsequent setvalue operations will negate the upload; a node copied by some operation such as insert or select/copy will not copy the uploaded content, only the lexical value of the node. [recorded in http://www.w3.org/2009/04/01-forms-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/04/01 16:26:40 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Leigh
Found ScribeNick: klotz

WARNING: No "Topic:" lines found.

Default Present: John_Boyer, unl, wiecha, prb, Leigh_Klotz, ebruchez
Present: John_Boyer unl wiecha prb Leigh_Klotz ebruchez
Regrets: Nick Steven
Agenda: http://lists.w3.org/Archives/Public/public-forms/2009Mar/0057.html
Got date from IRC log name: 01 Apr 2009
Guessing minutes URL: http://www.w3.org/2009/04/01-forms-minutes.html
People with action items: boyer john

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]