W3C

- DRAFT -

XForms Users Community Group Teleconference

09 May 2018

Agenda

Attendees

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

Contents


ACTION-2180: Add -output-error to alert hint help and label

https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0005

Steven: I did this

ACTION-2181: Fix optional ref on itemset/copy

https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0006

Steven: Also done

ACTION-2170: Suggest spec change for class on repeat

https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0011

Steven: So are we OK with formalising that?

Alain: Yes

Erik: I'm OK

Philip: Yep

<scribe> ACTION: Steven to implement change for class on repeat

<trackbot> Created ACTION-2182 - Implement change for class on repeat [on Steven Pemberton - due 2018-05-16].

ACTION-2169: Add actions for non-notification interaction events

https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0013

Steven: Do we want to do all 5?

Erik: Previous and next are obvious
... help and hint are interesting
... let me check the spec
... The help is typically something separate
... But hint has lots of different representations, such as minimal hint
... I don't think these two are important
... nor for activate
... I would say for the first two yes, and the last three don't bother.

Alain: Activate could be useful for testing, but dispatch is enough.

Steven: OK

<scribe> ACTION: Steven implement next and previous focus actions

<trackbot> Created ACTION-2183 - Implement next and previous focus actions [on Steven Pemberton - due 2018-05-16].

Structural constraints

https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0003

Steven: A discussion item.
... It would be useful forseveral cases for me.

Alain: I am in favour pf such improvements
... an effective constraint for us.

Steven: I don't think it asks a lot of an implementation, it already uses facilities that are therere.
... just makes them easier

Erik: I understand the use case
... not sure about the particular proposed solution

Alain: Maybe it's a constraint on minimum or maximum items

Steven: How should we move further on this

Erik: Let's think of some use cases.

Steven: I'll gather my use cases and post them.

<scribe> ACTION: Steven to post use cases for structural constraints

<trackbot> Created ACTION-2184 - Post use cases for structural constraints [on Steven Pemberton - due 2018-05-16].

Test Suite 2.0

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

Steven: I will try and post a new version this week.

AOB

[None]

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Steven implement next and previous focus actions
[NEW] ACTION: Steven to implement change for class on repeat
[NEW] ACTION: Steven to post use cases for structural constraints
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/05/09 13:16:58 $

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/erik/Erik/
Succeeded: s/gn/ng/
Present: Alain Erik Philip Steven
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018May/0014
Found Date: 09 May 2018
People with action items: 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]