W3C

- DRAFT -

XForms Users Community Group Teleconference

07 Sep 2016

Agenda

See also: IRC log

Attendees

Present
Steven, Alain, Philip, Erik
Regrets
Nick
Chair
Steven
Scribe
Steven

Contents


Errors vs. exceptions

https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0000.html

Steven: So you think we should call everything -error?

Erik: Yes

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Events_Overview

Erik: There is little backward-compatibility problem, since you can't do anything with them.

Steven: You can't keep them both since you would then have to catch both

Erik: As far as naming is concerned, I see no reason to mark the fatal ones specially.
... and I like the shorter names
... On one hand we have the events that come from the old exceptions like xforms-expression-error
... where we stopped processing by default, but now we allow for recovery.
... to allow for more robust applications
... Not sure if the default should be fatal.

Steven: I think if we changed that, forms would be less robust.
... at least the author can catch it and do something sensible.
... In summary, the spec is nw as we want it, and therefore there are no actions arising from this decision

Steven In the events overview

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Events_Overview

Steven: I have added links to the events, and will change the Yesses and Noes to something more readable.

Action-1430 - Repeat with automatic controls

https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0001.html

Erik: You always want more with repeat

<ebruchez> http://doc.orbeon.com/form-runner/component/grid.html

Erik: is the current set useful enough?
... We do this with a higher-level construct
... we can specify extra constraints
... what we do in any case should be future-prroof.

Steven: I think the proposed use cases are the basic simple ones that would make the user's life easier

Erik: Limit to number of items is a use case, and templating
... where would you get the fragment of XML that you would add?

Steven: XForms 1's method was horrible

Erik: 'origin' was a poor choice of name
... we have a template atttribute called 'origin', though 'template' makes it clearer

Steven: So you would like an attribute thatt in the case of inserts states where the template comes from.

Erik: Exactly

Steven: Ok, I'll work on that.
... we can discuss further in the email, and I will work on it further.

AOB

Steven: Please read section 9, and comment.

[ADJOURN]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/09/07 13:32:25 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
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: Steven
Inferring Scribes: Steven
Present: Steven Alain Philip Erik
Regrets: Nick
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0002
Found Date: 07 Sep 2016
Guessing minutes URL: http://www.w3.org/2016/09/07-forms-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]