See also: IRC log
<John_Boyer> Scribe: Leigh
<Steven> Mark says: I will be there...but about 15-20 minutes late.
<John_Boyer> scribenick: Leigh_Klotz
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008May/0067.html
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Apr/0100.html
<unl> i'm experiencing many drop outs. call back in again
<klotz> nic1 do you hear us?
<klotz> John: What does "NameTest" mean? I think what we ended up with, two Septembers ago, is that as an XPath expression is getting evaluated, any time we match a NameTest, we add that node to the list of nodes that are being referred to by the XPath expression. I think we did that so there would be more responsiveness of the compute system to predicate changes ("dynamic"), so if certain changes to the XPath happened, the various calculations would be able to detect
<klotz> that a change of referencing it happened and would know to get recalculated. Nick has an example, and has run into some problems. If you execute the XPath expression he gives, you'll notice that it matches both of the 'a' nodes; if you read the expression from left to right, and look at the predicate next to the 'a', you'll notice it's trying to match 'a' whose attr value is 'X', but the way we've written the spec, it puts a in with x. So if any of the a elem
<klotz> ents change, we respond to that; more importantly, if any of the attr nodes in any of the a's change, we'll respond to that as well, and that's part of the key. For any 'a' value that we match, we have a NameTest against each of those attributes as well, so all of the nodes that feed a predicate are considered. This seemed like a good idea. The alternative was that we would only register the register as dependencies those identified by a completed Location St
<klotz> ep of an XPath expression, so from the predicate of the first 'a' step we might record only the element 'a' that matched the predicate. So the question was should we record only the matched nodes, or feed in all those that are tested. We went with the broader test, the one that keeps all references; that means we will follow all calculations. If you notice in the 'a' element, if you imagine that being changed to 'X', we detect that change and re-run whatever
<klotz> calculates might have that full expression; whereas with narrower references (location step) only the 'a' that has attribute 'X' would have been recorded and if you change the value 'Z
<nic1> http://lists.w3.org/Archives/Public/public-forms/2008Apr/0086.html
<markbirbeck> waves back! :)
<markbirbeck> akim, i am aaaa
<klotz> http://xformstest.org/klotz/2008-05-28.txt
<Charlie> * me too
<unl> I'm feeling fine
<nic1> I don't like to drop does extra dependencies, because I hate to add a rebuild to fix it
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Apr/0100.html
<nic1> (but that is my opinion)
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Apr/0086.html
<nic1> for the record, I don't have anything against the current wording, it adds the correct nodes to the dependency list in most cases I guess. And personally I only would like only to make changes if the change that __doesn't__ add extra cases where a manual rebuild is necessary.
<nic1> (but this is what John is saying also)
<nic1> agree with that
<unl> i would like to keep the current behaviour, because this way can handle some dynamic dependencies just by static analysis
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Apr/0086.html
<nic1> yes
<nic1> unmute me
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008May/0047.html
<klotz> ACTION: John Boyer to write a clarifying note in XForms 1.1 regarding dependencies and http://lists.w3.org/Archives/Public/public-forms/2008Apr/0100.html and http://lists.w3.org/Archives/Public/public-forms/2008Apr/0086.html [recorded in http://www.w3.org/2008/05/28-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)
<nic1> I would expect also block-level elements
<nic1> you can style for example a <span> as a block level element
<klotz> <xf:message><xhtml:p><xf:input...
<nic1> UI.textOrStructureOrAnything
<nic1> (in XSL-FO flow is an element, containing all the flo stuf....)
<John_Boyer> UI.Inline
<John_Boyer> UI.Flow
<nic1> UI.Contents ?
<klotz> ACTION: John_Boyer to change XForms 1.1 document and Schema to rename UI.Inline to UI.Content and UI.Content.Extension as a non-normative, editorial change. [recorded in http://www.w3.org/2008/05/28-forms-minutes.html#action02]
<trackbot-ng> Sorry, couldn't find user - John_Boyer
<nic1> but don't have a hard feeling about it ;)
<Charlie> i can do that
<Steven> http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415/
<nic1> XmlHttpRequest
<Charlie> i can take events then
<klotz> link for events?
<klotz> ACTION: Mark Birbeck to review http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415/ and present straw set of comments for discussion and approval at F2F. [recorded in http://www.w3.org/2008/05/28-forms-minutes.html#action03]
<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> <p rel="foaf:homePage" about="[ex:home.html]">home</p>
<Charlie> * Leigh, are you doing the action for me to review XML events too?
<klotz> Charlie I need the URI for the document for you to review.
<unl> xml events 2: http://www.w3.org/TR/2007/WD-xml-events-20070216/
<Charlie> * i was looking too!
<klotz> ACTION: Charlie Wiecha to review http://www.w3.org/TR/2007/WD-xml-events-20070216/ and present straw set of comments for discussion and approval at F2F. [recorded in http://www.w3.org/2008/05/28-forms-minutes.html#action04]
<trackbot-ng> Sorry, couldn't find user - Charlie
<Steven> http://www.w3.org/TR/xml-events2/
<Steven> is the generic name
<Steven> http://www.w3.org/TR/2008/WD-curie-20080506/
<klotz> ACTION: Leigh Klotz to review http://www.w3.org/TR/2008/WD-curie-20080506/ by June 10th. [recorded in http://www.w3.org/2008/05/28-forms-minutes.html#action05]
<trackbot-ng> Created ACTION-463 - Klotz to review http://www.w3.org/TR/2008/WD-curie-20080506/ by June 10th. [on Leigh Klotz, Jr. - due 2008-06-04].
<klotz> http://rdfa.info/
<markbirbeck> http://planetxforms.org/
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008May/0043.html
<Steven> ACTION: Steven to post http://lists.w3.org/Archives/Public/public-forms/2008May/0043.html to news [recorded in http://www.w3.org/2008/05/28-forms-minutes.html#action06]
<trackbot-ng> Created ACTION-464 - Post http://lists.w3.org/Archives/Public/public-forms/2008May/0043.html to news [on Steven Pemberton - due 2008-06-04].
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008May/0060.html
<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008May/0061.html
<nic1> I started to write XForms 1.2 spec text, and it is taking quite some time to just change anything, probably bcz. it is the first time
<nic1> so I don't think I will have much time beside that before the ftf
<Charlie> i would love to help implement the simplified stuff
<markbirbeck> You might not have a choice Charlie. ;)
<nic1> In the future I can also allocate some time to work on it (during my employers time)
<markbirbeck> Excellent nic1! :)
<markbirbeck> I've also had interest from one of the big Ajax library creators, who has their own XML language.
<markbirbeck> (Interest to add people to work on the library, that is.)
<Steven> We don't have an announcement of Ubiquity on our homepage either
<Steven> Anyone want to suggest text?
<markbirbeck> Steven...would rather get a nicer looking sample available first. :)
<klotz> http://xformstest.org/klotz/shibumiscript/2008/05/ubiquity-xforms.html
<nic1> 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) Succeeded: s/UI.Flow/UI.Content and UI.Content.Extension/ Found Scribe: Leigh Found ScribeNick: Leigh_Klotz WARNING: No scribe lines found matching ScribeNick pattern: <Leigh_Klotz> ... WARNING: 0 scribe lines found (out of 161 total lines.) Are you sure you specified a correct ScribeNick? WARNING: No "Topic:" lines found. Default Present: Charlie, John_Boyer, wellsk, unl, Steven, Roger, Leigh_Klotz, Nick_van_den_Bleeken, +1.208.761.aaaa, markbirbeck Present: Charlie John_Boyer wellsk unl Steven Roger Leigh_Klotz Nick_van_den_Bleeken +1.208.761.aaaa markbirbeck Regrets: Erik Agenda: http://lists.w3.org/Archives/Public/public-forms/2008May/0067.html Got date from IRC log name: 28 May 2008 Guessing minutes URL: http://www.w3.org/2008/05/28-forms-minutes.html People with action items: birbeck boyer charlie john john_boyer klotz leigh mark steven wiecha 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]