12:39:53 RRSAgent has joined #forms 12:39:53 logging to http://www.w3.org/2016/10/12-forms-irc 12:39:55 RRSAgent, make logs public 12:39:55 Zakim has joined #forms 12:39:57 Zakim, this will be 12:39:57 I don't understand 'this will be', trackbot 12:39:58 Meeting: XForms Users Community Group Teleconference 12:39:58 Date: 12 October 2016 12:40:20 Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0011 12:40:32 Steven has changed the topic to: Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0011 12:40:44 Chair: Steven 12:42:33 alain has joined #forms 12:58:46 ebruchez has joined #forms 13:03:21 Present: Steven, Alain, Erik 13:05:50 https://www.kadaster.nl/web/english/About-Kadaster.htm 13:07:12 Topic: Advance warning, call with be at 14:00 in Europe on 2 Nov 13:07:12 http://www.timeanddate.com/worldclock/fixedtime.html?msg=XForms+Call&iso=20161102T09&p1=43&ah=1 13:07:29 Steven: Only one week this year. 13:07:43 ... one hour earlier in Europe 13:07:56 Topic: Section 9 13:07:56 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0009.html 13:08:10 Steven: I'm assuming Section 9 is now done. 13:08:20 Topic: @value 13:08:20 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0010.html 13:09:50 Steven: Surprising amount of work. Many differences are just difference in text, which I can put right. But I still have questions. 13:09:53 ... Deprecate submission/header/name, submission/header/value? 13:11:08 ... I realise now that you can generate several headers with one name using several values. 13:11:25 ... So that is reason enough to keep header/value 13:12:08 Erik: Header/name /value look like item/name /value 13:12:12 pfennell has joined #forms 13:12:27 ... I have no strong feelings about deprecating 13:12:36 Steven: Fine. I thought it was worth mentioning. 13:12:56 Steven: What happens if the evaluation of @value that has type ANY fails? 13:13:06 Present+Philip 13:14:41 Erik: Hmm, good question 13:15:06 ... for bindings we fall back, and dispatch an error 13:15:19 ... for actions we have xforms-action-error 13:15:57 ... we don't want actions to silently fail 13:16:41 ... one solution would be to dispatch an event 13:16:53 ... maybe we already do this already at a general level 13:17:11 10.5.2 Error Recovery Inside Actions 13:17:47 "Any error taking place during action processing stops the outermost action handler. Errors include: 13:17:47 expression errors 13:17:47 binding errors with the bind or model attribute 13:17:47 binding errors with complex or readonly content 13:17:48 missing mandatory attributes or unsupported attribute values on action elements 13:17:48 The xforms-action-error event is dispatched to the observer of the action. Observers include: controls and the model, instance, and submission elements. 13:17:48 Note: 13:17:48 Some actions silently ignore error conditions and are not subject to the processing above, including: 13:17:49 setvalue pointing to the empty sequence or to an atomic item (such as a string) instead of a node 13:17:51 delete with the empty sequence or an empty overridden context 13:17:52 insert with an empty or non-element insert context, an empty overridden context, or an empty origin 13:17:54 actions with AVTs evaluating to the empty sequence 13:17:55 dispatch, send, setfocus, setindex, and toggle when the target element is not found" 13:17:57 https://www.w3.org/community/xformsusers/wiki/index.php?title=XForms_2.0#Error_Recovery_Inside_Actions 13:19:39 Steven: So that covers action/param, and dispatch/property. What about function/param 13:19:42 ? 13:19:56 s/param/result 13:20:42 Erik: I propose that we use the same processing as bind errors 13:23:09 s/I propose that we use the same processing as bind errors// 13:24:15 Erik: Right now it is implementation dependent for when the function elements are processed. 13:26:01 ... there can be preprocessing, that spots errors, or a dynamic error 13:30:04 Steven: There are lots of places where preprocessing could occur already, and we don't say what to do in those cases. 13:36:40 Steven: We say that a string @value returns the empty string if evaluation fails 13:37:07 ... what should we say for other types? 13:37:15 Erik: There is no good default value 13:37:35 Steven: Then just say "it is undefined"? 13:45:33 ACTION: Erik to propose text for what value is used when the evaluation of function/result@value fails 13:45:33 Created ACTION-2076 - Propose text for what value is used when the evaluation of function/result@value fails [on Erik Bruchez - due 2016-10-19]. 13:46:25 Steven: I think we can make @value a Common attribute 13:46:32 ... along these lines: 13:46:33 Generalise more?: 13:46:33 * Returns a string or any type as specified 13:46:33 * Evaluated in in-scope context, unless there is a binding, and then it 13:46:33 uses that context. 13:46:34 * If the element can have PCDATA content, then @value overrides it 13:46:34 * If evaluation fails, for strings the empty string is used; for ANY ??? 13:46:34 (decision) 13:47:35 Steven: Then I can put the description of @value in one central place, and all the places where it is used, they use that Common attribute 13:47:48 Erik: Finer to do that. 13:47:54 s/Finer/Fine/ 13:50:00 Erik: I would prefer it if section 10.5.2 supercedes "returning the empty string". 13:50:06 Steven: That's fine. 13:51:18 Topic: AOB 13:51:22 [None] 13:51:39 [ADJOURN] 13:51:44 rrsagent, make minutes 13:51:44 I have made the request to generate http://www.w3.org/2016/10/12-forms-minutes.html Steven 15:17:45 Zakim has left #forms 15:55:29 ebruchez has joined #forms