See also: IRC log
<John_Boyer> Scribe: Leigh
<Rafael> ??P8 is Rafael
<John_Boyer> scribenick: klotz
great, you're in practice!
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Mar/0058.html
<wellsk> The W3C XForms 1.1 test suite can be found here: http://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/driverPages/html/index.html
<wellsk> http://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/zip/TestCases11.zip
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Mar/att-0026/actions-2008-03-05.html
Action 2008-02-13.1 done
Action 2007-12-12.1 done
Action 2007-11-28.2 done
Action 2007-10-10.3
Action 2007-08-8.1
<John_Boyer> Remove three of the four occurrences of Action 2008-01-16.1
Action 2007-03-14.5 done
2007-09-12 open http://www.w3.org/2007/09/12-forms-minutes.html#action01 done
Action 2007-10-03.1 done
Action 2007-10-10.4 done
Action 2007-10-31.1 done
<John_Boyer> Done Action 2007-10-31.1
<John_Boyer> Done Action 2007-10-24.5
<ebruchez> Done too: 2007-10-24.2, http://www.w3.org/2007/09/19-forms-minutes.html#action03, http://www.w3.org/2007/09/19-forms-minutes.html#action01, http://www.w3.org/2007/05/30-forms-minutes.html#action04
<ebruchez> and Action 2007-05-16.4, as I think we had solved the event order issue
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Mar/att-0026/actions-2008-03-05.html#landwehrdavid
<John_Boyer> David's list
<John_Boyer> Remove Action 2007-03-07.3
<John_Boyer> Remove Action 2006-07-5.8 because known issue now that is moved to 2.0 to architect a new solution based on smarter controls
<John_Boyer> Remove Action 2006-07-5.6 because John already did the work and added to 1.1
<John_Boyer> Remove Action 2006-01-31.3 because future feature for 2.0
<John_Boyer> Remove Action 2005-09-08.15 because done in 1.1 (if and while on actions)
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Mar/0055.html
<John_Boyer> <select1 name="X" readonly="some/expression"
<John_Boyer> <readonly context=".." value="some/expression"/>
<nick> <select1 ref="X" readonly=".."> should become <readonly value=".."/>
<nick> _NO_ context=".."
<markbirbeck> <output id="bonusmsg" value="$BonusMsg" relevant="$Subtotal > 100" />
<markbirbeck> <output id="bonusmsg" value="$BonusMsg" relevant="Subtotal > 100" />
<markbirbeck> <input name="GiftMsg" relevant="$Gift = true()" />
<markbirbeck> <input name="GiftMsg" relevant="Gift = true()" />
<John_Boyer> <input name"Gift"> ...
<nick> and you should use <input ref="GiftMsg" relevant="../Gift = true()" />
<nick> if you have <input name="Gift" /> or <bind nodeset="GiftMsg"/>
<John_Boyer> <group name="X"><input name="Gift">...</group>
<John_Boyer> <input name="GiftMsg" relevant="boolean-from-string($Gift)">...
<John_Boyer> <input name="GiftMsg" relevant="boolean-from-string(X/Gift)">...
<Steven> I had Mark S on the line, and he said that our call clashes with the Oasis one, but he will be back soon (OoM 1 month)
<John_Boyer> <group ref="../.."> <output name="LineTotal" calculate="$something"
<John_Boyer> Proposal: use of name attribute implies the following
<John_Boyer> 1) create an instance node at "current" level of XML corresponding to UI structure
<John_Boyer> 2) create bind with id same as the name
<John_Boyer> 3) move all MIP attributes from named UI control to child elements of bind with context=".."
<nick> I think we need to be able to mix it
<nick> I agree with Mark
<nick> In my opinion I would also call it a failure if you can mix it
<John_Boyer> Nick, Do you mean failure if you *cannot* mix it?
<nick> sorry yes, if you can __not__
<nick> but I think what we now have, works
<nick> <group ref="../.."> <output ref="LineTotal" calculate="$something"/> should work if you provided your instance data, if we decide that lazy authoring doesn't allows ".." (like it is today)
<John_Boyer> sure
<nick> ref="a[1]" and ref="a[2]" but supporting lazy authoring with predicates is nearly impossible (if you want to support more then only position()= <constant>
<ebruchez> I have to go, talk to you next week
<John_Boyer> bye, Erik
<John_Boyer> 4) the UI control is converted from name attr to having a bind attr
<John_Boyer> <output bind="LineTotal" ...>
<John_Boyer> <output bind="LineTotal" calculate="...."
<John_Boyer> <output name="blah" relevant="$X"
<John_Boyer> $X is still interpreted in context of the output even when you do this
<John_Boyer> <output bind="blah" relevant="$X"
<markbirbeck> <output ref="x" relevant="boolean-from-string(../blah)" />
<John_Boyer> So if MIP attributes stay on the controls, then they can't be evaluated in context of UI binding
i have to go in 2 minutes.
<John_Boyer> ok
calculate sounds like xsl:variable
<John_Boyer> If there are alternate proposals to http://lists.w3.org/Archives/Public/public-forms/2008Mar/0055.html, then we need to get them out there so we can settle the syntax and semantics.
<SusanB> ok, bye
<nick> bye, it was a good call
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ref/bind/ Found Scribe: Leigh Found ScribeNick: klotz WARNING: No "Topic:" lines found. Default Present: Nick_van_den_Bleeken, ebruchez, +1.919.254.aaaa, John_Boyer, wellsk, Leigh_Klotz, Rafael, Susan_Borgrink, unl, Steven, markbirbeck Present: Nick_van_den_Bleeken ebruchez +1.919.254.aaaa John_Boyer wellsk Leigh_Klotz Rafael Susan_Borgrink unl Steven markbirbeck Regrets: Charlie Joern Agenda: http://lists.w3.org/Archives/Public/public-forms/2008Mar/0058.html Got date from IRC log name: 19 Mar 2008 Guessing minutes URL: http://www.w3.org/2008/03/19-forms-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]