<scribe> Scribe: Leigh

<nic1> starts the week after

<nic1> yes

<nic1> 2 weeks later I think

<nic1> March 30

<nic1> we have the call one hour earlier

<nic1> starting from Marh 11

<nic1> sorry 12

<nic1> and then the next 3

US/Canada change time March 9, so calls on march 12, 19, 26 are one hour earlier in Europe

<nic1> looks good

<wellsk> http://www.w3.org/MarkUp/Forms/wiki/January-February_2008_Newsletter

http://lists.w3.org/Archives/Public/www-forms-editor/2008Feb/0002.html

<klotz> ACTION: John Boyer to fix schema issue http://lists.w3.org/Archives/Public/www-forms-editor/2008Feb/0002.html [recorded in http://www.w3.org/2008/02/27-forms-minutes.html#action01]

<trackbot-ng> Sorry, amibiguous username (more than one match) - John

<trackbot-ng> Try using a different identifier, such as family name or username (eg. jkugelma, jboyer)

<klotz> ACTION: Mark Birbeck to note check fix in prototype modularized Schema for http://lists.w3.org/Archives/Public/www-forms-editor/2008Feb/0002.html [recorded in http://www.w3.org/2008/02/27-forms-minutes.html#action02]

<trackbot-ng> Sorry, amibiguous username (more than one match) - Mark

<trackbot-ng> Try using a different identifier, such as family name or username (eg. mseaborn, mbirbeck)

<nic1> http://www.w3.org/MarkUp/Forms/wiki/Unified_evaluation_context

<nic1> http://lists.w3.org/Archives/Public/public-forms/2008Feb/0076.html

bind nodeset="purchaseorder/items/item/lineTotal"

calculate context=".." value="quantity * price"

calculate= "../quantity * ../price"

input [readonly] name="result" calculate="a+b"

input name="a"

input name="b"

calculate="../a + ../b" conversion is hard because you have to parse XPath expression

<nic1> http://www.w3.org/MarkUp/Forms/wiki/Add_model_item_properties_to_UI_level

http://lists.w3.org/Archives/Public/public-forms/2008Feb/0022.html

<bind nodeset="X"> <constraint operator="and" value="expr"/>

scribe:

<bind nodeset="X"> <constraint value="expr"/> (default is and)

<nic1> <bin nodeset="//*[@type='b']" constriant=".."/>

<nic1> <bin nodeset="//*[@class='c']" constriant=".."/>

<nic1> these can have nodes in common

<bind nodeset="X" constraint=". > 10"/>

<bind nodeset="X" constraint=". &lt; 100"/>

<Charlie> agree with Leigh...worried about creating a new expression language in angle brackets

<Charlie> can get ugly quickly

<Steven> +1 to that

<unl> i'm worried too. they will laugh at us

<nic1> I only needed and in the past ;)

<nic1> so lets only combine them with and, that will solve all my past use cases... no really maybe we need to check what the use cases are for needing us to create our own expression language

<Charlie> sounds like it's going in the right direction...keep it simple

<unl> we should use the same logical operations for combining mips which are already used in inheritance rules

constraint="A or B"

valid="A or B"

invalid="not(A)"

invalid="not(B)"

valid="A" operator="or"

valid"B" operator="or"

<klotz> http://lists.w3.org/Archives/Public/public-forms/2008Feb/0022.html

<nic1> <bind nodeset="//*[@type='b']" constriant=".."/>

<nic1> <bind nodeset="//*[@class='c']" constriant=".."/>

http://www.w3.org/MarkUp/Forms/wiki/Unified_evaluation_context

<nic1> these can have nodes in common

<nic1> with .. an arbitrary xpath expression (not just parent)

<nic1> read-only/read-write valid/invalid

<nic1> http://www.w3.org/MarkUp/Forms/wiki/Add_model_item_properties_to_UI_level

http://lists.w3.org/Archives/Public/public-forms/2008Feb/0063.html

<klotz> ref='.[x=y]'

<Charlie> +1 for example-driven approach

<Steven> +1

<markbirbeck> <input name="first-name" />

<Charlie> otherwise it's hard to follow the details

<markbirbeck> <input name="surname" />

<markbirbeck> <output name="full-name" value="concat($first-name, ' ', $surname)" />

<markbirbeck> This is what we discussed before, but the difference now is that "full-name" could also be referred to in the same way.

<markbirbeck> (Possibly...... :))

<klotz> ACTION: John Boyer and Mark Birbeck to put together simplified syntax straw proposal for purchase order example to make sure we have repetition capability and non-trivial calculation. [recorded in http://www.w3.org/2008/02/27-forms-minutes.html#action03]

<trackbot-ng> Sorry, amibiguous username (more than one match) - John

<trackbot-ng> Try using a different identifier, such as family name or username (eg. jkugelma, jboyer)

<Charlie> admin items?

<nic1> Input Mode Issues http://lists.w3.org/Archives/Public/public-forms/2008Feb/0074.html

<nic1> http://www.w3.org/TR/xforms-11-req/

<Roger> bye

<nic1> bey

<jturner> bye

<Schnitz> bye

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)

No ScribeNick specified.  Guessing ScribeNick: John_M_Boyer
Found Scribe: Leigh

WARNING: No "Topic:" lines found.

Default Present: wellsk, Charlie, unl, +0049308322aaaa, jturner, Nick_van_den_Bleeken, Susan_Borgrink, ebruchez, Andrew, Leigh_Klotz, Rafael, Schnitz, Steven, markbirbeck
Present: wellsk Charlie unl +0049308322aaaa jturner Nick_van_den_Bleeken Susan_Borgrink ebruchez Andrew Leigh_Klotz Rafael Schnitz Steven markbirbeck
Regrets: None
Agenda: http://lists.w3.org/Archives/Public/public-forms/2008Feb/0078.html
Got date from IRC log name: 27 Feb 2008
Guessing minutes URL: http://www.w3.org/2008/02/27-forms-minutes.html
People with action items: birbeck boyer john mark

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