W3C

- DRAFT -

Forms Working Group Teleconference

28 Nov 2012

Agenda

See also: IRC log

Attendees

Present
Steven, +1.323.425.aaaa, nvdbleek1, [IPcaller], Erik
Regrets
Philip
Chair
Steven
Scribe
nvdbleek1

Contents


<trackbot> Date: 28 November 2012

zakm, who is here?

<scribe> scribe: nvdbleek1

Meetings next month

Steven: I take december off
... I'm willing to come to calls
... We need to get XForms 2.0 to LC
... Nobody in the community list responded

XForms 2.0 proto Last call draft

<Steven> http://lists.w3.org/Archives/Public/public-forms/2012Nov/0025.html

Steven: We need people in the group to agree to go forward

<Steven> Diff version http://www.w3.org/MarkUp/Forms/Drafts/WD-xforms20-20130117/Overview-diff.html

Steven: anyone have feelings about this

Erik: I have to go through the changes

nvdbleek1: We have couple of issues that still need to be addressed

Element name for specifying properties on dispatch action

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

Steven: We called this property, at the time some people didn't liked the name that much
... This is the last change to propose a different name, if nobody responds it will be property

alain: It is already implemented as property in xsltforms

Lighter syntax for the function element

<Steven> http://lists.w3.org/Archives/Public/public-forms/2012Nov/0024.html

nvdbleek1: It was mainly Erik wanting a shorter syntax

Erik: Will have a look at it

Format token parameter on serialize

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

nvdbleek1: I'm a bit concerned about the format parameter on serialize() and parse()[2] functions, because I think that the format token only allows boolean properties.
... And on the submission element and xslt output options you have properties that take other type of values.

Erik: It's on my list, will try to look at this today

<Steven> I think it would be good to have another, fuller, example for the serialize section

nvdbleek1: In XSLT they have an element syntax, they re-use the output element

erik: The xslt way feels a bit hacky
... In javascript you just pass an object
... In the future the closest we can get will be the map construct

alain: I'm wondering what the use case is today
... Because I only implemented the version without parameters in xslt forms
... maybe we can leave it implementation defined

Steven: Is this taken from XPath 3.0

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

<Steven> Example:

<Steven> <output:serialization-parameters>

<Steven> <output:omit-xml-declaration>yes</output:omit-xml-declaration>

<Steven> </output:serialization-parameters>

We are discussing the the xpath3 version

Erik: The indirection is not ideal, but until we have the map in xpath the element is the best solution

Steven: I imagine that it is very irritating that you have to create the element if you want to specify the serialisation parameters

Erik: The main drawback is not being compatible to XPath 3.0

Steven: The usage of serialization function is to transform the XML to string, couldn't we use a submission for this

nvdbleek1: A function should be pure

Steven: Couldn't we point to a submission and ignore certain parameters

Erik: We should disable a lot in submission: revalidation, sending events

Steven: It should just point to a submission and take the parameters from a submission

Erik: That is the approach xslt takes, it uses the ouput element. But the drawback is that we are discarding a lot attributes

Steven: The drawback of a different element is that we have to keep the elements in sync

Erik: It uses only the serialisation part of the submission, which is only a small subset

Steven: The author already knows how to do this with submission

target/targetid on load and submission

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

<Steven> Moot.

nvdbleek1: This issue is no longer valid, I should remove the target attribute

<scribe> ACTION: Remove the target attribute from the submission element because we don't have load embed anymore [recorded in http://www.w3.org/2012/11/28-forms-minutes.html#action01]

<trackbot> Sorry, couldn't find Remove. You can review and register nicknames at <https://www.w3.org/2005/06/tracker/xforms/users>.

<Steven> ACTION: Nick to Remove the target attribute from the submission element because we don't have load embed anymore [recorded in http://www.w3.org/2012/11/28-forms-minutes.html#action02]

<trackbot> Created ACTION-1915 - Remove the target attribute from the submission element because we don't have load embed anymore [on Nick Van Den Bleeken - due 2012-12-05].

Summary of Action Items

[NEW] ACTION: Nick to Remove the target attribute from the submission element because we don't have load embed anymore [recorded in http://www.w3.org/2012/11/28-forms-minutes.html#action02]
[NEW] ACTION: Remove the target attribute from the submission element because we don't have load embed anymore [recorded in http://www.w3.org/2012/11/28-forms-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2012-11-28 17:15:56 $

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)

Succeeded: s/* Topic/Topic/G
Found Scribe: nvdbleek1
Inferring ScribeNick: nvdbleek1
Default Present: Steven, +1.323.425.aaaa, nvdbleek1, [IPcaller], Erik
Present: Steven +1.323.425.aaaa nvdbleek1 [IPcaller] Erik
Regrets: Philip
Agenda: http://lists.w3.org/Archives/Public/public-forms/2012Nov/0027.html
Found Date: 28 Nov 2012
Guessing minutes URL: http://www.w3.org/2012/11/28-forms-minutes.html
People with action items: nick remove

[End of scribe.perl diagnostic output]