W3C

- DRAFT -

Forms Working Group Teleconference

10 Apr 2013

See also: IRC log

Attendees

Present
pfennell, ebruchez, nvdbleek
Regrets
Chair
Nick
Scribe
nick

Contents


<trackbot> Date: 10 April 2013

Reminder: Deadline for Balisage XForms Symposium is 19th April

http://www.balisage.net/XML-Interfaces/index.html

ACTION-1932: Erik to edit the spec for load/@show and @target

<scribe> scribe: nick

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0004.html

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0001.html

http://lists.w3.org/Archives/Public/public-forms/2013Mar/0020.html

http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3781&oldid=3780

http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3782&oldid=3781

nvdbleek: for me those changes were fine

pfennell: I didn't have a change to have a look yet

nvdbleek: We give people one week to send in comments

ebruchez: The changes are minimal

[ACTION-1934] Completed (Update the XML and relax-ng schema (change

mediatype to accept on upload))

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0006.html

ACTION-1934?

<trackbot> ACTION-1934 -- Nick Van Den Bleeken to update the XML and relax-ng schema (change mediatype to accept on upload) -- due 2013-02-27 -- PENDINGREVIEW

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1934

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0006.html

ebruchez: If it is deprecated it should not be removed from the schema

nvdbleek: OK, I will add it back to the XML and Relax schema
... I will do the update later today

ACTION-1939: Add the xforms:HTMLFragment data type and add text to

the text area control similar like it is done for xs:date on xf:input

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0007.html

nvdbleek: Spec changes http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3791&oldid=3789
... ebruchez, pfennell are you going to read it now or should we put it on the agenda for next week

ebruchez: I had a first glance at it now, it looks good, but I want to have a closer look

nvdbleek: OK we will leave it on the agenda, and ask other people to comment before next call

The function Element

http://lists.w3.org/Archives/Public/public-forms/2013Mar/0018.html

http://lists.w3.org/Archives/Public/public-forms/2013Mar/0019.html

http://lists.w3.org/Archives/Public/public-forms/2013Jan/0028.html

http://lists.w3.org/Archives/Public/public-forms/2013Apr/0013.html

http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3795&oldid=3791

nvdbleek: I made as less changes as possible maybe we need to make more

ebruchez: I definitely want to review this

nvdbleek: We will keep on the agenda for next week. Everybody should review it and send in comments before next call

Element name for specifying properties on dispatch action

http://lists.w3.org/Archives/Public/public-forms/2012Nov/0023.html

nvdbleek: Does anybody wants another name then property?

pfennell: property is reasonable

ebruchez: property as element name is fine
... They use property in javascript
... In our implementation we initially had context

nvdbleek: and we already use the name context for the xpath context

Format token parameter on serialize

http://lists.w3.org/Archives/Public/public-forms/2012Nov/0012.html

http://www.w3.org/MarkUp/Forms/wiki/XPath_Expressions_Module#The_serialize.28.29_Function

ebruchez: Steven had a proposal to use a submission element

nvdbleek: On submission you can specify more parameters then the output format parameters, you would ignore those then I guess?

http://www.w3.org/TR/xpath-functions-30/#func-serialize

http://www.w3.org/TR/xslt-xquery-serialization-30/#serparams-in-xdm-instance

nvdbleek: In xpath 3.0 they use an element output:serialization-parameters

ebruchez: They chose a name that is so large...
... I don't think the element has to have a particular name

nvdbleek: Wouldn't that be for validation

ebruchez: You only need the attributes
... Ideally you have named parameters, but you can't do that in XPath
... If we go for submission, we probably have to make a lot of changes for allowing only a subset of attributes
... I'm proposing to pass in an element and only look at the attributes on the element (we will ignore the element name)
... I will send a reply with the proposal

<scribe> ACTION: Erik to send his proposal about passing an element to the serialise and parse functions for the format options and only look at the attributes on the element (we will ignore the element name) [recorded in http://www.w3.org/2013/04/10-forms-minutes.html#action01]

<trackbot> Created ACTION-1942 - Send his proposal about passing an element to the serialise and parse functions for the format options and only look at the attributes on the element (we will ignore the element name) [on Erik Bruchez - due 2013-04-17].

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: Erik to send his proposal about passing an element to the serialise and parse functions for the format options and only look at the attributes on the element (we will ignore the element name) [recorded in http://www.w3.org/2013/04/10-forms-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013/04/10 15:41:05 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: nvdbleek
Found Scribe: nick
Default Present: pfennell, ebruchez, nvdbleek
Present: pfennell ebruchez nvdbleek
Found Date: 10 Apr 2013
Guessing minutes URL: http://www.w3.org/2013/04/10-forms-minutes.html
People with action items: erik

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]