See also: IRC log
http://www.timeanddate.com/worldclock/fixedtime.html?msg=XForms+Call&iso=20161102T09&p1=43&ah=1
Steven: Don't forget!
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0029.html
Steven: I'm assuming we want to
agree with this, but I want to record it
... with both ref and value *anywhere*, the value is used, but
in context of the ref.
... OK?
[Yes]
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0031.html
Steven: Do we agree that using toggle has an effect of setting the thing caseref points to?
<ebruchez> "Changes to the selected case can also be performed by the toggle action, but these are performed by performing a setvalue action if the caseref attribute is specified and indicates a node. If the node is readonly, if the caseref attribute does not indicate a node, or if the toggle action does not indicate a case in the switch, then no value change occurs and therefore no change of the selected case occurs."
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_switch_Element
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_toggle_Element
"If the switch has a caseref attribute which identifies a node, and that node is not readonly, then the node is set to the value of the case identifier as if by a setvalue action."
Erik: Agreed
Steven: So resolved
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0034.html
Steven: My proposal in this case is that @label takes precedence; the general rule is that the newer thing takes precedence over the older thing (which may be the same as saying the attribute wins over the elemen).
Erik: I'm fine with that.
Philip: I'm happy
Steven: Also with the general rule
Philip: I'm happy with that.
Steven: So resolved
<alain> mike problem...
<alain> Yes I agreed
Steven: Great
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0035.html
Steven: Can you add properties to any event?
Erik: I don't see why not
... our implementation everything is custom, so it's not a
problem
Steven: Alain says it works in the browser, so I will fix the wording.
<scribe> ACTION: Steven to fix wording for property element [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action01]
<trackbot> Created ACTION-2079 - Fix wording for property element [on Steven Pemberton - due 2016-11-02].
<scribe> ACTION: Steven to change priorities to attribute over element [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action02]
<trackbot> Created ACTION-2080 - Change priorities to attribute over element [on Steven Pemberton - due 2016-11-02].
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0038.html
"If the Single Item Binding is given in addition to one of the
<code> resource</code> attribute or <code>resource</code> element, then the
action has no effect."
<trackbot> Error finding 'has'. You can review and register nicknames at <https://www.w3.org/2005/06/tracker/xforms/users>.
Steven: I'm suggesting to change this so that the resource is evaluated in the context of the ref
Erik: Right. Good.
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0039.html
Steven: I don't understand why we say it is implementation dependent
Erik: Maybe because you don't have entire control.
<load ref="../document" target="_blank"/>
Steven: In a case like that we say that the processor keeps running
Erik: Maybe not
... there might not be a method of linking back.
Steven: How about saying it is impl dependent but that we encourage implementations to use xforms-link-error if possible
<alain> You are right. It is not possible
Steven: OK
Still there?
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0041.html
Steven: I think we answered
this
... input controls are allowed to bind to atomic values, as if
they are read-only
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0042.html
Steven: I think the answeer is "who cares"; all controls have @incremental, and if it doesn't have an effect, then no problem
<alain> Yes
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0050.html
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0056.html
Steven: Why can't a string type also be 'open'?
Erik: I think it should be.
Steven: I agree. I will change the text.
<scribe> ACTION: Steven to allow select on a string to be allowed to be open [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action03]
<trackbot> Created ACTION-2081 - Allow select on a string to be allowed to be open [on Steven Pemberton - due 2016-11-02].
Steven: The second link is more a discussion issue, rather than a solution for right now
Erik: There are potential solutions. It arises often
Steven: I just wanted to record that it's an issue
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0022.html
Steven: I had an action item to find where we discussed this or something similar. I couldn't find it. So do we want to support this, or leave it as is?
Erik: It makes sense
... I don't have a problem.
<alain> No problem
Steven: OK.
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0024.html
Steven: Already resolved
evaluation of function/result@value fails
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0012.html
Erik: Not done yet.
Steven: I'm going to the ODF plugfest in Paris to talk about XForms
<alain> Bye
[ADJOURN]
<scribe> ACTION: Steven to allow @ref and @value to work together [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action04]
<trackbot> Created ACTION-2082 - Allow @ref and @value to work together [on Steven Pemberton - due 2016-11-02].
<scribe> ACTION: Steven to specify precedence of @label over <label> [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action05]
<trackbot> Created ACTION-2083 - Specify precedence of @label over <label> [on Steven Pemberton - due 2016-11-02].
<scribe> ACTION: Steven to allow load@resource to work in combination with @ref [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action06]
<trackbot> Created ACTION-2084 - Allow load@resource to work in combination with @ref [on Steven Pemberton - due 2016-11-02].
<scribe> ACTION: Steven to specify that input controls bound to an atomic value are read-only [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action07]
<trackbot> Created ACTION-2085 - Specify that input controls bound to an atomic value are read-only [on Steven Pemberton - due 2016-11-02].
<scribe> ACTION: Steven to allow PCdata as content of item/value [recorded in http://www.w3.org/2016/10/26-forms-minutes.html#action08]
<trackbot> Created ACTION-2086 - Allow pcdata as content of item/value [on Steven Pemberton - due 2016-11-02].
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/rul/rule/ Succeeded: s/"/:/ Succeeded: s/oe/e/ Succeeded: s/;/'/ Succeeded: s/v/lv/ Succeeded: s/controld/controls/ No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Present: Steven Alain Erik Philip Regrets: None Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0057 Found Date: 26 Oct 2016 Guessing minutes URL: http://www.w3.org/2016/10/26-forms-minutes.html People with action items: steven[End of scribe.perl diagnostic output]