- From: Mark Birbeck <mark.birbeck@x-port.net>
- Date: Tue, 5 Apr 2005 17:23:47 +0100
- To: "'John Boyer'" <JBoyer@PureEdge.com>
- Cc: <www-forms@w3.org>, "'Klotz, Leigh'" <Leigh.Klotz@xerox.com>
Hi John, > I also agree with (and don't see what I said earlier as not > agreeing with) the assertion that it is the handlers and not > the events themselves that are conditionally occuring. It wasn't that you were saying that handlers were not the answer -- in fact I think the opposite, you *were* saying that the functionality you wanted needed to be at the handler level. However, I felt the need to clarify because you said that my solution was "too coarse grained", implying that it was operating at the event level, and I wanted to show that I too was looking at the handler level. > Therefore, I also agree that a syntax like the one you showed > here: > > <xf:action ev:event="my-delete"> > <xf:delete ... /> > <xf:insert ev:condition="[empty nodeset]" /> > </xf:action> > > is workable. I.e. putting the condition attribute in the > events namespace is just a matter of namespacing, and the > essential detail of having fine grain control of action > execution is achieved. Great. > But putting 'condition' in the events namespace seems to be > incongruous with what XML events does, currently at least. > Unlike Section 3.5 of the current spec, is it the case that > the next version of XML events intends to "require an > application that uses XML events to use" a "particular method > for specifying handlers"? > > What I'm getting at is simply that the condition attribute > indicates what a handler should be doing, and this is the > domain of the language that consumes XML events, not of XML > events (1.0 anyway). I understand, although you could argue that all of this is in the domain of DOM 2 Events (since both handlers and events are defined there), so any separation at the level of the mark-up should really be for convenience of presentation, rather than creating a division where this isn't one -- and so one namespace is sufficient. (A draft for 'XML Handlers' uses the XML Events namespace, even thought it is a separate document to XML Events, which is why I used it in my examples.) But I certainly wouldn't have a problem with a different namespace. Regards, Mark Mark Birbeck CEO x-port.net Ltd. e: Mark.Birbeck@x-port.net t: +44 (0) 20 7689 9232 w: http://www.formsPlayer.com/ b: http://internet-apps.blogspot.com/ Download our XForms processor from http://www.formsPlayer.com/
Received on Tuesday, 5 April 2005 16:24:03 UTC