W3C

- DRAFT -

XForms Users Community Group Teleconference

19 Dec 2018

Agenda

Attendees

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

Contents


Winter pause

Steven: No call for next two weeks. Next call Jan 9th.

ACTION-2207: Merge <signal/> into <dispatch/>

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0009

Steven: Done; see spec for result

Cleaning up attributes

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0012

Steven: Is there a reason that we have no @bind on <bind/>?

Erik: A bind wouldn't be able to refer to itself, or a child of itself.
... or mutual recursion

Steven: So you think it's just to make life easier?

Erik: I don't think there's a need for it, and it would need to be restricted.
... Leave as is.

Steven: I think <submission/> not using "Single node binding" must be an oversight.

Erik: Agree.

<scribe> ACTION: Steven to fix submission to use single item binding

<trackbot> Created ACTION-2210 - Fix submission to use single item binding [on Steven Pemberton - due 2018-12-26].

ACTION-2196: Spec up collapsing sections

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0002

Steven: So it seems like a single attribute stating that it is collapsible is enough and giving the state open/closed.
... I sent some suggestions. Eg:

<group state="closed">

<group state="open">

<group mode="closed">

<group mode="open">

<group state="closed">

<group state="open">

<group collapse="closed">

<group collapse="open">

<group fold="closed">

<group fold="open">

Erik: I'm not sure I like that specifying the state implies the appearance.

Steven: So you want both?

Erik: I think so
... you need something to specify the state

Steven: As an AVT as well?

s/AVT/

Alain: Two values of @appearance?

Steven: That was my suggestion last week, that Erik didn't like.
... That is why we are discussing this this week.

Erik: It might introduce a dynamic appearance, which we don't have at the moment.
... So better to say that it is collapsible, and then add state.
... that is two things instead of oen, I agree.

Alain: So @state would be extensible

Steven: Possible in the future

Erik: The name of the attribute is a different question

Steven: So we have to agree on a value for @appearance, and a name for the other attribute.

Erik: I'm not a fan of using 'appearance="compact"'
... something more explicit is better
... collapsible or synonym.

Steven: I'll come up with some suggestions.

XForms in 3D

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

Steven: I'll put this off until Philip is here.

AOB

[None]

Steven: Have a good break!

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Steven to fix submission to use single item binding
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2018/12/19 14:18:20 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/bough/nough/
Succeeded: s/fiy/fy/
FAILED: s/AVT//
Succeeded: s/ATV/AVT/
Succeeded: s/;/'/
Succeeded: s/;/'/
Succeeded: s/vute/bute/
Succeeded: s/different/different question/
Succeeded: s/SO/So/
Present: Alain Erik Steven
Regrets: Philip
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0016
Found Date: 19 Dec 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]