W3C

- DRAFT -

Forms Working Group Teleconference

04 Apr 2012

Agenda

See also: IRC log

Attendees

Present
+44.782.483.aaaa, Steven, +1.323.425.aabb, nvdbleek1, ebruchez
Regrets
Chair
Steven
Scribe
Steven

Contents


<trackbot> Date: 04 April 2012

<scribe> Scribe: Steven

Editorial meeting

Steven: Nick, you and I should get together; maybe on a Weds/Thurs, and then use the Forms call for discussion

Erik: Next week?

Nick: A bit early; do you think we should have a longer call?

Erik: Sure

Steven: So the action is for Nick and I to settle on a date, and then the group know so that we can extend the call.

Community group

Steven: Maybe Leigh is a good candidate

Nick: Yes, though it has to go to a vote

Steven: I'll ask him if he's interested

Erik: He mentioned he was interested

Nick: There are facilities in CGs to set up polls

Steven: I'll check
... I moved the implementation list to the CG http://www.w3.org/community/xformsusers/wiki/XForms_Implementations
... Please keep your entries up-to-date

Nick: Poll page is https://www.w3.org/community/xformsusers/wp-admin/admin.php?page=wp-polls/polls-manager.php

Public WD

<scribe> ACTION: Nick to update WD according to http://lists.w3.org/Archives/Public/public-forms/2012Apr/0002.html [recorded in http://www.w3.org/2012/04/04-forms-minutes.html#action01]

<trackbot> Created ACTION-1884 - Update WD according to http://lists.w3.org/Archives/Public/public-forms/2012Apr/0002.html [on Nick Van Den Bleeken - due 2012-04-11].

[Discussing the element function comment in the above mail]

[Whether it should be the same as XSLT, because it looks similar, or just explain the difference]

[Erik, and Philip don't feel strongly about it]

<nvdbleek1> https://www.w3.org/MarkUp/Forms/Group/Drafts/WD-xforms-xpath-20120504/#The_element.28.29_Function

Erik: The current text isn't ambiguous
... unless we want to put a restriction

Nick: It mentions attributes and content

Erik: An implementor can trivially do the right thing
... if there is a risk that an implementor may not do it right, we should add text (about attributes coming after content)

Nick: I can add an extra example

Philip: I agree with that

<scribe> ACTION: Nick to add an extra example to https://www.w3.org/MarkUp/Forms/Group/Drafts/WD-xforms-xpath-20120504/#The_element.28.29_Function to show that attributes may come after element content [recorded in http://www.w3.org/2012/04/04-forms-minutes.html#action02]

<trackbot> Created ACTION-1885 - Add an extra example to https://www.w3.org/MarkUp/Forms/Group/Drafts/WD-xforms-xpath-20120504/#The_element.28.29_Function to show that attributes may come after element content [on Nick Van Den Bleeken - due 2012-04-11].

<nvdbleek1> http://lists.w3.org/Archives/Public/public-xformsusers/2012Apr/0000.html

Repeat over values

<nvdbleek1> <xf:repeat ref="1 to 5">

Erik: About repeat over values

<nvdbleek1> http://lists.w3.org/Archives/Public/public-xformsusers/2012Apr/0008.html

Nick: Only on bind and submission do we restrict what @ref may contain

Erik: Clearly an XPath expression can return a seq of nodes, we need to be explicit what should happen
... it is not obvious from the spec that it is allowed
... we should say something

Nick: I don't recall if we had a resolution on this
... but if a control binds to a node that is not part of an instance data, it becomes read-only

Erik: If it's a node, you can write to it, why not? Why make it read-only?

Nick: Too surprising for the user, on a refresh, the changed values would be replaced with something else

Erik: Maybe it's the right thing to do
... but it would be silly for a form author to do that in the first place
... transform() could be said to return read-only results. Not sure if it's needed for element() or attribute()
... if you can't use bind on it, there would be no MIPs on it

Nick: You could have a simple checking implementation
... not hard to implement

Erik: I'd have to think about it
... but I understand the rationale
... You could create an element, store it in a variable. It is not in an instance, but it should be mutable
... therefore it shouldn't be read-only
... unless we decide that copying into a variable makes them mutable
... XPath doesn't have mutability

Steven: I don't hear consensus

Nick: I'm not sure anyway

Erik: I can send out an email summarising the two sides, and we can take it from there.

Nick: Which list?

Erik: Both, the CG and the WG

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Nick to add an extra example to https://www.w3.org/MarkUp/Forms/Group/Drafts/WD-xforms-xpath-20120504/#The_element.28.29_Function to show that attributes may come after element content [recorded in http://www.w3.org/2012/04/04-forms-minutes.html#action02]
[NEW] ACTION: Nick to update WD according to http://lists.w3.org/Archives/Public/public-forms/2012Apr/0002.html [recorded in http://www.w3.org/2012/04/04-forms-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/04/04 15:57:21 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Eric/Erik/
Succeeded: s/Nevt/Next/
Succeeded: s/FOrms/Forms/
Succeeded: s/SVG and XForms/Repeat over values/
No ScribeNick specified.  Guessing ScribeNick: Steven_
Found Scribe: Steven
Default Present: +44.782.483.aaaa, Steven, +1.323.425.aabb, nvdbleek1, ebruchez
Present: +44.782.483.aaaa Steven +1.323.425.aabb nvdbleek1 ebruchez
Agenda: http://lists.w3.org/Archives/Public/public-forms/2012Apr/0003
Found Date: 04 Apr 2012
Guessing minutes URL: http://www.w3.org/2012/04/04-forms-minutes.html
People with action items: nick

[End of scribe.perl diagnostic output]