See also: IRC log
https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0001.html
Steven: I've got most of the text done, but need a little more time.
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Container_Form_Controls
https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0015
Erik: I'm about half-way through the review of this section
Steven: Thanks for the changes you made
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_group_Element
Steven: I made another change
there
... I propose that we use the attribute form for labels in the
majority of examples
<scribe> ACTION: Steven to review use of labels in examples [recorded in http://www.w3.org/2016/09/21-forms-minutes.html#action01]
<trackbot> Created ACTION-2071 - Review use of labels in examples [on Steven Pemberton - due 2016-09-28].
"4. Speaking of `caseref`, I don't remember if I raised this before but it
is limiting to depend on the `id` of the `<case>`. In our implementation,
we added an optional `value` attribute on `<case>` which can be used to
associate a value with each `<case>` element.
"
Erik: The spec uses @id to store
the reference to the node
... this loses control over the value that matches the
case
... you might have two switches with some values that are
shared, but you can't have duplicate ids
<ebruchez> <switch caseref="">
<ebruchez> <case id="apple"></case>
<ebruchez> <case id="tomato"></case>
<ebruchez> </switch>
<ebruchez> <switch caseref="">
<ebruchez> <case id="lettuce"></case>
<ebruchez> <case id="tomato"></case>
<ebruchez> </switch>
Steven: I see what you mean
... in fact it is a really bad idea to use id for caseref
Erik: So we use @value (as well
as @id)
... the value is an expression
<ebruchez> <switch caseref="">
<ebruchez> <case value="'apple'"></case>
<ebruchez> <case value="'tomato'"></case>
<ebruchez> </switch>
<ebruchez> <switch caseref="">
<ebruchez> <case value="'lettuce'"></case>
<ebruchez> <case value="'tomato'"></case>
<ebruchez> </switch>
<ebruchez> Or:
Steven: What if two cases have the same value?
<ebruchez> <switch caseref="">
<ebruchez> <case name="apple"></case>
<ebruchez> <case name="tomato"></case>
<ebruchez> </switch>
<ebruchez> <switch caseref="">
<ebruchez> <case name="lettuce"></case>
<ebruchez> <case name="tomato"></case>
<ebruchez> </switch>
Steven: everytime we use the wod value, it's an expression, right?
Erik: yes
... We take the first case in document order that matches the
value
<scribe> ACTION: Erik to change text for caseref/case to use @value [recorded in http://www.w3.org/2016/09/21-forms-minutes.html#action02]
<trackbot> Created ACTION-2072 - Change text for caseref/case to use @value [on Erik Bruchez - due 2016-09-28].
[None]
[ADJOURN]
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: Steven_ Inferring Scribes: Steven_ Present: Steven Erik Alain Philip. Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Sep/0016 Found Date: 21 Sep 2016 Guessing minutes URL: http://www.w3.org/2016/09/21-forms-minutes.html People with action items: erik steven[End of scribe.perl diagnostic output]