<kenneth> the conference code is 36767 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), kenneth

<ebruchez> all, I'll be a few minute late as I am in a call

<ebruchez> so don't wait for me to start

<John_Boyer> scribe: Leigh

<John_Boyer> scribenick: klotz

<John_Boyer> http://htmlwg.mn.aptest.com/cgi-bin/xforms-issues/XPath?id=67;user=guest;statetype=4;upostype=-1;changetype=-1;restype=-1

<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2007Jul/0080.html

<John_Boyer> http://htmlwg.mn.aptest.com/cgi-bin/xforms-issues/XPath?id=68;user=guest;statetype=4;upostype=-1;changetype=-1;restype=-1

<nick> if we drop the multiple variants we should use the ones from the specs

<John_Boyer> http://htmlwg.mn.aptest.com/cgi-bin/xforms-issues/XPath?id=70;user=guest;statetype=4;upostype=-1;changetype=-1;restype=-1

<John_Boyer> http://www.w3.org/TR/xforms11/#fn-get-seconds-from-duration

<nick> it can be me, but can't check my computer is really slow

<John_Boyer> seconds("P1Y2M")

<John_Boyer> return 0?

<nick> it was me ;) seconds("P1Y2M") returns 0 and not NaN because the input is a valid duration but

<nick> the seconds function doesn't takes months and years into account.

<Roger_> Rafael sent an email about this issue giving and aditional sample

<John_Boyer> link?

<Roger_> seconds("P1Y2M3DT10H30M1.5S") returns 297001.5

<John_Boyer> http://htmlwg.mn.aptest.com/cgi-bin/xforms-issues/XPath?id=71;user=guest;statetype=4;upostype=-1;changetype=-1;restype=-1

<John_Boyer> 28http://www.w3.org/TR/xforms11/#fn-choose <http://www.w3.org/TR/xforms11/>

<John_Boyer> http://www.w3.org/TR/xforms11/#fn-choose

<nick> http://www.w3.org/TR/xpath20/#doc-xpath-IfExpr

<nick> Conditional expressions have a special rule for propagating dynamic errors. If the effective value of the test expression is true, the conditional expression ignores (does not raise) any dynamic errors encountered in the else-expression. In this case, since the else-expression can have no observable effect, it need not be evaluated. Similarly, if the effective value of the test expression is false, the conditional expression ignores any dynamic errors encountere

<nick> do we need to specify this for our choose function?

<lars> who is playing tetris?!?

<nick> I persanally feel better with the current wording too, but can't give a good reason

<nick> but you know the type in front, only when you have extension functions that return an object

<nick> bye

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Leigh
Found ScribeNick: klotz
WARNING: No scribe lines found matching ScribeNick pattern: <klotz> ...

WARNING: 1 scribe lines found (out of 96 total lines.)
Are you sure you specified a correct ScribeNick?


WARNING: No "Topic:" lines found.

Default Present: John_Boyer, kenneth, Nick_van_den_Bleeken, +091211aaaa, unl, Roger, lars, Leigh_Klotz, +1.541.754.aabb, Blake, ebruchez
Present: John_Boyer kenneth Nick_van_den_Bleeken +091211aaaa unl Roger lars Leigh_Klotz +1.541.754.aabb Blake ebruchez
Regrets: Steven Keith MarkB Charlie Rafael Sebastian
Agenda: http://lists.w3.org/Archives/Public/public-forms/2007Jul/0139.html
Got date from IRC log name: 1 Aug 2007
Guessing minutes URL: http://www.w3.org/2007/08/01-forms-minutes.html
People with action items: 

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