13:46:19 RRSAgent has joined #forms 13:46:19 logging to http://www.w3.org/2016/11/30-forms-irc 13:46:21 RRSAgent, make logs public 13:46:21 Zakim has joined #forms 13:46:23 Zakim, this will be 13:46:23 I don't understand 'this will be', trackbot 13:46:24 Meeting: XForms Users Community Group Teleconference 13:46:24 Date: 30 November 2016 13:46:41 Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0114 13:46:46 Chair: Steven 13:46:59 Steven has changed the topic to: Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0114 13:59:44 pfennell has joined #forms 14:02:27 It's not letting me in. 14:02:33 ANyone else already in? 14:02:38 The Connect to Audio button is garyed out for me 14:02:56 For me too... 14:03:35 damn 14:03:46 Let me try something else 14:03:48 just a moment 14:03:54 calling in it says the access code is not coirrect 14:06:36 For me too 14:06:40 liam? 14:08:54 I can't join the meeting until the host joins, but I AM the host... 14:10:10 how does WebEx know you are the host? 14:10:35 Usually there is a button to claim the host role 14:10:47 but I'm using the mobile app, and it doesn't have that button 14:10:55 before today I could just phone in 14:12:48 I see a Reclaim Host Role menu in the desktop app 14:12:55 it requires a Host key 14:13:58 it's 192124 14:14:20 ok if I claim that it seems I can join the audio 14:14:46 Great. I'll try diallin in again 14:15:24 Still not valid. 14:15:29 Anyone else in? 14:15:35 Phlip 14:15:47 Philip is in 14:17:52 Topic: Rewrite 14:17:52 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0054 14:18:49 Steven: Please take a look, and send comments as necessary. 14:18:58 Topic: ACTION-2076: Propose text for what value is used when the 14:18:58 evaluation of function/result@value fails 14:18:58 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0012.html 14:18:58 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0093.html 14:20:22 Erik: It's simple, because in XPath errors propagate 14:21:28 ... I've treated both var and function results. 14:22:08 Steven: So in other words, we don 't produce a value, we just give an error 14:22:11 Erik: Yes 14:22:49 Erik: We're doing the same as XPath basically 14:22:54 Erik: ANother problem 14:23:11 ... what happens if the syntax of the function signature is 14:23:11 incorrect. 14:23:17 s/AN/An/ 14:26:06 Erik: I am suggesting we do something similar to how we treat missing functions in the @functions attribute on model 14:26:43 Erik: I'll add the error paragraph for @value, and I'll suggest text for the signature 14:26:53 Topic: 14:26:53 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0106.html 14:27:35 Steven: Are we ok with @value on message? 14:27:46 [general agreement] 14:28:00 Topic: JSON: characters below \u0020 14:28:00 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0112.html 14:28:49 Steven: Which would you prefer? 14:28:54 Erik: Be specific 14:29:19 ACTION: Steven to tighten description of equivalent XML charactors for JSON serialisation 14:29:20 Created ACTION-2092 - Tighten description of equivalent xml charactors for json serialisation [on Steven Pemberton - due 2016-12-07]. 14:29:37 Topic: The constraint Property 14:29:37 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0111 14:30:56 Erik: So where would you like to see the error? 14:31:16 ... we can't set an alert on a repeat. 14:32:04 ... so we set the constraint on the wish element 14:32:17 ... so it shows up on the input for the wish 14:32:35 ... but it wouldn't show up with minimum number of wishes 14:32:57 ... I guess there's a bigger story. 14:33:30 ... you could provide a 'dummy' control 14:33:38 Steven: Do we do alert on output? 14:33:41 Erik: WE do! 14:33:46 ... let's check the spec 14:34:14 ... yes output inludes help hint and alert 14:35:10 ACTION: Steven to update constrain note, and change it to an example. 14:35:10 Created ACTION-2093 - Update constrain note, and change it to an example. [on Steven Pemberton - due 2016-12-07]. 14:35:19 Topic: Focus on container controls 14:35:19 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0047.html 14:36:38 Erik: Focus can be tricky. 14:36:51 ... but I think what you suggest is fine 14:37:12 ... there is a recursive aspect 14:38:04 Alain: Looks OK for me. 14:38:16 ... I'm not sure what we do now, but it's OK 14:38:34 Topic: xforms-next/previous 14:38:34 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0073.html 14:39:58 Steven: In other words xforms-next would work in a similar way to setfocus 14:40:14 Erik: We don't implement this event 14:41:30 Steven: It would typically be bound to the tab key 14:45:30 Erik: THere's no example in the spec, I don't see the use case. 14:45:49 ACTION: Produce example for xforms-next 14:45:49 Error finding 'Produce'. You can review and register nicknames at . 14:45:56 ACTION: Steven to Produce example for xforms-next 14:45:56 Created ACTION-2094 - Produce example for xforms-next [on Steven Pemberton - due 2016-12-07]. 14:47:14 Erik: My problem is not why you need a nav order, just when would you use this event. 14:47:23 Steven: I'll try and produce some use cases 14:47:33 Topic: The xforms-rebuild Event 14:47:33 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0057.html 14:49:29 Steven: I think that "Any child bind elements are recursively processed as described in the 14:49:29 three points of this list." 14:49:29 is redundant 14:49:46 ... since the inner bind is already covered by the rules 14:49:54 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0061.html 14:51:08 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0070.html 14:55:15 Steven: If you think it's fine as it is, then we leave it as is. 14:55:45 Alain: I agree with Erik 14:55:51 Steven: FIne, I was wrong. 14:56:01 Topic: xforms-refresh 14:56:01 https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0067.html 14:57:42 Steven: It seems wasteful. I don;t know why we require this 14:57:48 Erik: We don't do it. 14:57:53 Alain: I don;t know what we do 14:58:10 Steven: How about "events that change MUST be sent, others MAY be sent" 14:58:24 Erik: I think we should be explicit about what may and may not be sent 14:58:41 s/;/'/ 14:59:17 ... if the control should change state it should be dispatched only in that case, 14:59:33 Alain: I'd agree with that. 14:59:42 Philip: Me too 15:00:03 ACTION: Steven to tighten definition of which events get sent on value changed 15:00:03 Created ACTION-2095 - Tighten definition of which events get sent on value changed [on Steven Pemberton - due 2016-12-07]. 15:00:29 Erik: What happens when the control becomes relevant? 15:00:50 https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Relevance 15:02:39 alain1 has left #forms 15:02:55 [ADJOURN] 15:03:05 Present: Alain, Erik, Philip, Steven 15:03:10 rrsagent, make minutes 15:03:10 I have made the request to generate http://www.w3.org/2016/11/30-forms-minutes.html Steven 16:51:03 ebruchez has joined #forms 17:26:00 Zakim has left #forms