W3C

- DRAFT -

XForms Users Community Group Teleconference

20 Jun 2018

Agenda

Attendees

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

Contents


Summer break

[This is the last call until August 17th. However, we will remain active

on the mailing list.]

State change events

https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0020

ttps: //lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0020

https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0020

Steven: Different notification events are targeted to different places:

Erik: A group can be bound to other elements
... so just wanting to know the validity
... MIPs are easy to ask.
... but for a value, it makes no sense to dispatch value changed
... a group can be bound to a parent node, but an input can't.

Steven: Even if group binds to a child, it still doesn't get value-changed

Erik: Value-changed is only of use to controls that bind to values
... switch is like a group

<ebruchez> 5.4.9 Refresh

Steven: 2) Since the second group of events are the result of properties defined

in the model, maybe we should be able to catch those on binds as well.

Steven: I'm not sure yet if I'm proposing that (yet) but we should consider it.
... 3) We use the phrase "bound value" several times in the spec, without

formally defining it. We should.

<scribe> ACTION: Steven to define "bound value"

<trackbot> Created ACTION-2189 - Define "bound value" [on Steven Pemberton - due 2018-06-27].

Steven: I'm going to think about this a bit more and see if we can make some unifying text before we decide one way or another.

The control Element

https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0024

Steven: [describes the email]
... should we do relevance trimming?

Erik: Not sure. On submission it is an option.
... there's not much of use on submission, no serialisation for instance.
... maybe add it as an attribute.

<scribe> ACTION: Steven add relevance attribute to return action

<trackbot> Created ACTION-2190 - Add relevance attribute to return action [on Steven Pemberton - due 2018-06-27].

Test Suite 2.0

https://lists.w3.org/Archives/Public/public-xformsusers/2018Apr/0051

Steven: No developments this week

AOB

[None]

Steven: Speak in 6 weeks. But we'll still be communicating via email.

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Steven add relevance attribute to return action
[NEW] ACTION: Steven to define "bound value"
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/06/20 13:19:42 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/[This is the last call until August 17th. However, we will remain active//
Succeeded: s/on the mailing list.]//
Present: Alain Erik Steven
Regrets: Philip
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Jun/0025
Found Date: 20 Jun 2018
People with action items: add attribute relevance steven

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]