17:16:10 RRSAgent has joined #forms 17:16:10 logging to http://www.w3.org/2009/02/11-forms-irc 17:16:14 wiecha has joined #forms 17:16:16 rrsagent, make log public 17:17:15 Meeting: W3C Forms WG Face to Face Meeting, Day 3, Feb. 11, 2009 17:17:30 Chair: John 17:18:55 Scribe: Leigh 17:19:06 John: Erik has asked about tests that we may have nobody pass. 17:19:16 John: Part of that is conformance triange. 17:19:22 s/triange/triage/ 17:19:25 John: XForms 1.2 17:19:39 John: For the latter half of the day, start on XForms for HTML assertions 17:19:56 Erik: I won't be here this afternoon. 17:20:29 Nick, can you find out Joern meant with tests 5.5.2.a and 5.5.3.a passing? those are not real test cases 17:21:02 John: We got an idea of what we're not doing (on Monday) but we need an idea of what we are doing. 17:21:24 John: Test suite? New report? 1.2 Mod? 17:21:35 Charlie: Let's look quickly at what's important from yesterday. 17:21:49 John: So, XForms 1.1 testing. 17:25:34 John: Chapter 4 had some surprising no-passes. 17:25:50 Charlie: If there are ones people can sign up to implement... 17:26:38 http://lists.w3.org/Archives/Public/public-forms/2009Feb/0031.html 17:28:07 Keith: I made the test case changes to the Ubiquity tests but haven't tested them yet. 17:28:22 Steven has joined #forms 17:28:39 John: So we might get a few more passes. 17:29:07 John: 3.3.4.b more bind element examples 17:30:13 Erik: What should the first one do? There's no nodeset on the bind. 17:30:20 Nick: It is then the default context node, the root. 17:30:34 John: You should get an exception then as it has child elements. 17:30:41 Erik: Binding exception; that's new in 1.1 17:31:13 rrsagent, don't start a new log at midnight 17:31:22 Keith: This was sparked by controversy on the list 17:31:23 rrsagent, pointer? 17:31:23 See http://www.w3.org/2009/02/11-forms-irc#T17-31-23 17:31:29 rrsagent, make minutes 17:31:29 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html Steven 17:31:43 John: The controversy was the second one, a bind with no nodeset, for inner binds. 17:31:56 8.1.1 "Element nodes: If element child nodes are present, then an xforms-binding-exception occurs. " 17:32:21 Leigh: So you should get an error on this whole page because of the first test, which has the wrong label? 17:32:59 Erik: So what does bind with no nodeset mean? 17:33:04 Nick: It's the initial context. 17:33:14 i/John: Erik has asked about tests /Topic: Testing 1.1 17:33:19 rrsagent, make minutes 17:33:19 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html Steven 17:34:08 Present: Raman, Hubble, Uli, Leigh, Charlie, John, Erik, Nick, Steven 17:34:12 Erik: So bind_002 should be "avg" not "/car" 17:34:44 i/scribe: Leigh/scribenick: klotz 17:34:47 Nick: There's no way to see both values at the same time. 17:34:50 rrsagent, make minutes 17:34:50 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html Steven 17:35:05 Leigh: Should we look at the spec to see what this was trying to test? 17:35:26 John: It's testing the in-scope evaluation context node as default for nodeset. 17:35:42 i/Scribe: Leigh/Scribenick: klotz 17:35:49 rrsagent, make minutes 17:35:49 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html Steven 17:36:04 John: [fixes example] 17:36:16 Erik: The /prices/price operates relative to the av element so we need 17:36:17 John: .. 17:36:27 Present+Keith(remote) 17:38:40 Erik: We've lost the first bind 17:38:45 Leigh: That could be a different test. 17:41:11 John: The inner bind has no nodeset. 17:41:29 Leigh: OK. 17:44:27 John: 4.5.2.a xforms-compute-exception 17:46:53 Erik: The event handler is on the model; let me check the spec. 17:47:03 John: 4.5.2.a is a copy-paste error. 17:47:16 Erik: compute is dispatched to the model; there was a different test that was wrong. 17:47:23 John: Why is this a link exception? 17:47:41 Erik: The compute exception is always dispatched to the model; the bind exception is dispatched to the element. 17:48:25 John: It has to be changed to compute exception. 17:49:08 Erik: I think that's not true; it bubbles and stops processing after setting the instance. 17:50:14 Leigh: I think our exception handling is way over engineered for what value it provides. 17:50:22 John: It's under engineered; it just says "processing stops" 17:50:37 Erik: You can't recover from this one so it makes no sense. 17:50:56 John: We should say that the processor is required to dispatch the event but we can't say you can then use XForms markup. 17:51:30 Erik: It should disable xforms after that; the events bubble but no xforms; you could use script for example. We can't require the xforms engine to do anything. 17:51:49 Uli: We say processing stops, but I don't know what that means. What happens to outer events? Is it cut off? 17:51:57 Erik: It's implementation dependent. 17:52:17 John: It does capture, bubble, and then done. Anything after that nobody can have expectation. 17:52:25 Erik: You can set a global flag. 17:52:57 Uli: So how useful is such an exception if you can't handle it? It's the opposite of Java (error/exception) 17:53:17 John: We've changed version; we'll have to change this and some binding tests to "may also see the expression." 17:53:21 Erik: It's more correct. 17:53:32 Erik: Will Ubiquity show it? Too early to say. 17:53:35 John: Too early ot say. 17:53:42 Erik: It depends on the processor. 17:53:51 John: Firefox should now pass this test. 17:54:21 Leigh: What generates it? 17:54:45 John: xf:output value="es@#invalidXpath" 17:54:55 Leigh: I think we've way overspecified what happens with authoring errors. 17:55:25 Erik: We should say that no XForms processing can be done after. 17:55:37 John: The spec says processing halt; the test assumes it doesn't. 17:55:44 Erik: I had never understood. 17:55:57 Uli: So it's useless to attach a message. 17:56:12 John: It says that the default action is to halt processing. 17:56:16 Erik: ... 17:56:20 John: We halt processing after. 17:56:46 Erik: I don't agree. We had this test where we through the exception during model initialization and the XForms processor could ignore any xforms actions that should be run. 17:56:50 FYI: test 4.5.a.xhmtl passes on FF3 when the link is changed to xforms-compute-exception 17:57:13 Erik: It's an edge case, not very useful. There's no way to say what ought to happen with half-initialized models and controls. 17:57:29 Uli: What's the user's expectation? The author? you want to be notified. 17:58:09 Leigh: I think it's a debugger issue, not an xforms issue. 17:58:21 Erik: Look at a javascript error, for example. 17:58:25 Uli: ... 17:59:08 John: This is a design tool mechanism; an xforms processor is required to dispatch the exception but other than dispatching the event and letting it bubble, our processing (actions, ui) is not to be expected. The XForms runtime is reporting an error. 17:59:46 Erik: That's for exceptions; errors are recoverable. So we shouldn't spend too much time on it. The spec should have a note saying that the minimum support is necessary. 18:00:06 Erik: Stop processing once default action is reached. 18:00:16 Charlie: Do you have to go to the default action? Can you dispatch and quit? 18:00:30 Erik: The default action is what stops processing. You could simulate it. 18:01:10 Charlie: It could terminate before bubble captures. 18:01:32 John: I've gone through once before and made sure all exceptions halt processing. 18:01:54 Uli: This says the default action happens after capture/bubble. I've learned it's not necessarily so, in discussions iwth Mark Birbeck. 18:02:09 Steven: XML Events doesn't define it; it's DOM events. 18:02:32 Steven: The DOM 2 spec is vague; as I understand it, it has to happen after capture nad bubble. 18:02:40 s/nad/and 18:02:47 John: None are cancellable. 18:03:08 s/iwth/with/ 18:05:19 Leigh: can we just add a note saying what we "default action halts processing" means with respect to DOM events? 18:05:49 John: I think what we need to say is that the hooked actions won't necessarily run either with exceptions that happen early in model construction. 18:07:12 John: We can make a note in each exception saying implementations need not execute action handlers for each event (nor ui refresh) 18:07:45 John: This test 4.5.2.a is challenging 18:08:01 Erik: We can take out the second part. Just test to see that the exception is thrown. 18:08:11 Charlie: A script handler 18:08:18 John: Which is implementation dependent. 18:13:28 Leigh: Why not take out a "You may seen an output" and take out the Forms markup that runs after the exception. Leave in only the stuff that all implementations should show and just print out "processing should halt" and test the negative: put in markup that ought not happen to show processing has halted. 18:13:38 John: We did that once. Was it link exception? 18:13:43 Nick: 4.5.4.a 18:15:28 John: So all the exception should do like 4.5.4.a and say "You shouldn't see this" and say processor-dependent mechanism is necessary to test. 18:16:01 Leigh: Sounds good. If the xf:message in there isn't causing problems but won't show up necessarily, I'd say remove it, but I can live with it if it's not causing problems. 18:16:10 Erik: It's confusing because it's not required. 18:16:24 John: The xf:output inside xf:message may or may not work in the link exception. 18:16:34 Charlie: It's in the bubble-capture so it should work. 18:17:06 John: Since the link exception is in the instance you might not have an evaluation context, though it could be the default instance; we just don't say the order. 18:17:18 John: So should I amend all the tests now? 18:19:22 ACTION: John Boyer, for each exception event, note that implementations are not required to run XForms action handlers, and user interface update should not occur. 18:19:22 Sorry, amibiguous username (more than one match) - John 18:19:22 Try using a different identifier, such as family name or username (eg. jkugelma, jboyer) 18:19:46 ACTION: jboyer, for each exception event, note that implementations are not required to run XForms action handlers, and user interface update must not occur. 18:19:46 Sorry, couldn't find user - jboyer, 18:20:50 John: In 4.5.4.a we switched to using xhtml:p instead of xf:group because these exceptions halt processing. 18:32:05 ACTION: John Boyer to update exception test cases to make no use of xforms processor after exception and indicate fatal error in prose. 18:32:05 Sorry, amibiguous username (more than one match) - John 18:32:05 Try using a different identifier, such as family name or username (eg. jkugelma, jboyer) 18:35:05 Erik: ... xsi:type ... 18:35:14 Nick: There is a test using id type as xsi:type 18:35:40 Nick: There are 3 tests: name id, bind, and xsi:type 18:35:52 John: I have a preference for things in our namespace. 18:36:41 John: Do we need separate tests? I don't want to get rid of xsi:type, but it looks like many fail. 18:36:54 Erik: We don't pass lots of type tests, just not via xsi:type. 18:38:06 Leigh: Is there a strong reason you don't implement xsi:type now? 18:38:25 Erik: I'd have to look. 18:38:54 John: It's a bit of a performance issue; we create pseudo-mips. 18:39:04 Erik: I could check at control binding. 18:39:21 John: It also affects validation. 18:39:43 Erik: Our validation process applies a schema and the goes through the binds. We are lacking the third one looking for xsi:type. 18:41:22 Leigh: So it's not more deep problems; it's just work. 18:41:24 Erik: Right. 18:45:47 John: What about the chapter 5 tests? 18:46:18 John: So 5.1.a-d uses xsi:type. We need pairs with bind/@type 18:47:54 John: Or change these to use type mip and make one test for xsi:type 19:01:12 http://xformstest.org/2009/02/f2f/tests now has 5.1.a 19:07:29 I added/uploaded a new test 5.1.e that tests datatype validation using xsi:type (in prep for converting the other tests to using the XForms type MIP) 19:12:39 http://xformstest.org/2009/02/f2f/tests now has 5.1.* 19:24:39 unl has joined #forms 19:24:46 http://xformstest.org/2009/02/f2f/tests now has 5.2.1.* 19:51:47 http://xformstest.org/2009/02/f2f/tests now has 5.2.6.a 19:55:54 http://xformstest.org/2009/02/f2f/tests 5.2.1.a has changed the invalid anyURI value to "% 6 7" from " Bogus Data " 19:57:16 Seen this XForms editor before? http://bpt.hpi.uni-potsdam.de/Oryx/XForms 19:57:25 s/5\.\2\,1\.a/5.1.a/ 20:03:27 http://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/Chapt04/4.5/4.5.3/4.5.3.a.xhtml 20:16:10 John: Can we test it in FormsPlayer? 20:16:11 Steven: Yes. 20:16:35 John: It notices and puts up an error message but doesn't run the action, so it seems possible but it's technically not passing. 20:16:40 Leigh: And show=replace 20:16:47 Steven: It shows it in a different place 20:17:13 Leigh: Why not remove the feature and let authors use submission/@replace='none' for testing beforehand and let authors who care rely on GET being idempotent? 20:17:27 John: That doesn't implement it properly because it does two gets. 20:17:39 Leigh: No, remove the feature and let authors do it themselves if they care. 20:17:47 John: It's a 1.0 feature 20:18:04 Erik: The world has changed since then and there are non-native implementations. 20:19:35 Leigh: It's possible to do as an author in HTML using XHR and two gets. 20:19:45 Erik: It's not quite correct because it might fail the second time. 20:20:01 Leigh: Yes, that's the Wile E. Coyote problem. 20:20:10 Erik: right. 20:20:59 Erik: So it optional good enough? 20:21:04 John: Optional means one implementor. 20:21:09 Erik: What's weaker than optional? 20:21:14 John: Nothing. 20:21:38 John: We did not in status distinguish between recommended and optional. Maybe in the future. 20:22:05 Erik: So we can't go to rec. 20:22:09 Leigh: Unless we take it out. 20:22:17 John: We won't have a formal objection then. 20:22:24 Erik: Mark could make it pass. 20:22:36 John: But he's not working on it. 20:23:59 John: So what do you think about removing xforms-link-error? It is a 1.0 feature but nobody is counting on it. 20:24:07 Raman: Remove it and see who screams. 20:24:27 ACTION: John Boyer to remove xforms-link-error from 1.1 on the basis that it is not implemented. 20:24:27 Sorry, amibiguous username (more than one match) - John 20:24:27 Try using a different identifier, such as family name or username (eg. jkugelma, jboyer) 21:56:23 nick has joined #forms 22:02:05 wiecha has joined #forms 22:02:23 John_Boyer has joined #forms 22:03:57 http://inwap.com/pdp10/pclsr.txt 22:04:29 http://www.panda.com/tops-20/pclsr-memo.txt 22:05:11 rrsagent, make minutes 22:05:11 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html John_Boyer 22:08:52 http://lambda-the-ultimate.org/node/463 also on PCLSR 22:09:20 unl has joined #forms 22:10:17 Steven has joined #forms 22:21:23 scribe: steven 22:21:40 Topic: Community building 22:22:46 Charlie: It would be fun to experiment in Ubiquity with different frameworks than Dojo 22:23:26 John: People otuside of this room? 22:23:31 s/tu/ut/ 22:23:40 s/than/in addition to 22:23:48 Leigh: We need to see the current stuff working first 22:24:17 ... I think I can get involved a bit further along, but not yet 22:25:34 Charlie: Is there anyone who wants to help with Ubiquity 22:25:57 Steven: Not out of the question 22:26:10 ... now that Jack Jansen is adding SMIL to Ubiquity 22:26:40 Nick: Noton company time, but maybe in spare time 22:26:47 s/Noton/Not on 22:27:10 [John demos Ubiquity] 22:27:35 [with outputs with images in the labels] 22:32:47 [Group debugs example :-) ] 22:37:49 John: Howmuch further along do we need to be? 22:37:56 s/How/How / 22:38:31 Leigh: There are things that don't work that stop me from trying it out sufficiently 22:38:53 John: Couldn't you just fix it? It's open source 22:39:01 Leigh: Not enough resources 22:39:16 ... I would like to see custom controls being possible 22:40:18 STeven: What's the process of joining 22:40:40 John: Join the contributors'group 22:40:52 s/group/ group/ 22:40:54 http://groups.google.com/group/ubiquity-xforms-eng 22:41:26 John: There is more information on that page 22:41:34 ... including licensing 22:42:07 STeven: Install SVN? 22:42:14 John: Yes 22:42:21 Raman: There is a web interface 22:49:27 [John explains mechanics of Google code] 22:54:13 [Leigh tries following the instructions] 22:55:05 try this: http://code.google.com/p/ubiquity-xforms/source/browse/trunk/samples/purchaseOrder/purchaseOrder.html 22:59:17 oops: this one http://ubiquity-xforms.googlecode.com/svn/trunk/samples/purchaseOrder/purchaseOrder.html 23:02:52 Topic: Modularisation 23:03:36 http://www.w3.org/MarkUp/Forms/wiki/XForms_1.2_Modularization 23:04:08 John: We had a discussion Monday, but I'm not sure what the resolution of that was 23:05:52 ... is there a higher-level view? How do we move forward? 23:06:01 Leigh: Are we doing the modularization or not? 23:06:10 John: I think not, not at the spec level 23:06:30 ... there is a modularization at the script level 23:11:32 John: We published XForms for HTML in December 23:11:49 Raman: What's stopping us from going to last call? 23:12:20 John: Last call in June would be good 23:12:35 ... taking us to CR 23:12:46 Steven: Who will implement? 23:12:54 John: Ubiquity 23:13:08 ... success will be over different browsers 23:13:42 ... since getting it to work in different browsers is a lot of work 23:14:31 ... it takes a lot of work to get through the rec track process, 23:14:41 ... another test suite on top of the current one 23:14:57 Leigh: We should write some samples 23:17:39 Charlie: There are some in the Ubiquity project 23:18:49 [John shows an example] 23:21:26 Leigh: We don't want to do full modularization, but we are happy if it gets done for us by Ubiquity. 23:21:47 ... The first example we should look for is an instance module 23:22:23 Charlie: Functionally that works today, but the modules are not available yet 23:29:49 Raman: Show how to do the Google suggest equivalent 23:33:59 Leigh: Pick an Ajax library, and look to see what it means for the instance module to work with it 23:34:21 Charlie: I am about to implement the data island module 23:40:30 Raman: You can sell it to people who like the model, and to people who need controls 23:42:22 John: Do people bind controls to JSON objects now? 23:42:37 Charlie: ... 23:43:07 ... there are data providers that give notifications 23:44:49 Charlie: The repeat module is clearly missing elsewhere, so is a strength for us 23:53:52 unl has joined #forms 23:59:38 John: So are we done? 00:00:01 Uli: Well, there's XForms 2.0 00:00:21 Leigh: We still have to deliver on the charter 00:01:00 ... but modularization is not directly serving anyone 00:01:23 ... we should be open to take the modules from outside, but we don't have to do it ourselves 00:06:58 work items going forward, then, are 00:06:59 1) advancing xforms for html (examples, assertions, test suite), 00:07:27 2) some new xforms 1.2 features to support xforms for html, such as context everywhere and json submissions 00:08:44 3) start analyzing ajax programming and how parts or all of xforms might fit in 00:08:54 4) XForms 2.0 00:11:49 5) Finish XForms 1.1 00:13:35 Leigh: Why do we have to do Basic? 00:13:49 Steven: We can't leave it; either a note or take it to rec 00:14:12 Leigh: 1.1 has subsumed basic in a profile 00:15:30 Raman: Just do it, it is the same amount of work 00:15:52 Leigh: We should add something to the status that points to 1.1 basic profile 00:17:57 John: I favour a note, as being less work 00:22:25 opic: Future meetings 00:22:32 Topic: Future meetings 00:24:09 Steven: Amsterdam or London? 00:24:18 Leigh: Amsterdam is easier to argue for 00:24:30 Charlie: I'd like to go somewhere new 00:25:31 Steven: Well, we don't have to decide now. We can just say AMsterdam/London 00:25:35 s/AM/Am/ 00:25:45 Uli: London will be more expensive 00:26:46 Raman: But in London Mark will come 00:27:22 Steven: He may well come to Amsterdam 00:27:30 ... it's not too far 00:27:47 Steven: ANd then there's TPAC 00:27:52 s/AN/An/ 00:28:01 Steven: Dates for Europe? 00:28:14 Nick: 8-10 June 00:28:35 ... 4 June is the vday 00:31:17 John: London for preference? 00:31:20 Uli: Yes 00:31:29 Leigh: Slightly harder for me then 00:32:20 John: When and where is TPAC? 00:32:39 Uli: San Francisco area, 2-6 November 00:33:39 ... 2-6 November 00:33:39 TPAC2009, Santa Clara Marriott, Santa Clara, CA, USA (in conjunction with AC Meeting) 00:33:47 http://www.w3.org/Consortium/meetings 00:35:49 http://www.w3.org/Member/Eventscal 00:36:25 http://www.w3.org/Member/#foryourcal 00:36:54 http://www.w3.org/Consortium/meetings 00:37:01 http://letmegooglethatforyou.com/?q=w3c+technical+plenary+2009 00:37:57 http://www.w3.org/2002/09/TPOverview.html 00:39:14 EOM? 00:42:48 [ADJOURN] 00:42:57 rrsagent, make minutes 00:42:57 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html Steven 00:43:25 11.10.a 00:43:25 11.4.b Corrected instance reference 00:43:25 5.1.a Changed xsi:type to MIPs 00:43:32 5.1.b Changed xsi:type to MIPs 00:43:33 5.1.c Changed xsi:type to MIPs 00:43:37 5.1.d Changed xsi:type to MIPs 00:43:37 5.2.1.a Changed xsi:type to MIPs 00:43:39 5.2.1.b Changed xsi:type to MIPs 00:43:39 5.2.1.c Changed xsi:type to MIPs 00:43:55 s/STeven/Steven/G 00:43:56 Updated those action items 00:43:57 got them 00:44:07 also previously checked in new 5.1.e 00:44:17 rrsagent, make minutes 00:44:17 I have made the request to generate http://www.w3.org/2009/02/11-forms-minutes.html John_Boyer 00:45:08 John_Boyer has left #forms 01:26:55 nick has joined #forms