- From: Jon Ferraiolo <jonf@adobe.com>
- Date: Tue, 31 Jan 2006 00:18:00 -0800
- To: "Bjoern Hoehrmann" <derhoermi@gmx.net>, "Maciej Stachowiak" <mjs@apple.com>
- Cc: "Charles McCathieNevile" <chaals@opera.com>, <public-cdf@w3.org>
Bjoern, Very minor correction - sXBL does not define its own handler element. It inherits script and handler elements from its host language. sXBL does define an sxbl:handlerGroup element, but this is to allow a component developer to create event handler "templates" which cause the enclosed event handlers to be attached to each instance of a component. With sXBL, the contents of sxbl:handlerGroup are event handlers from the host language, such as svg:handler. It looks as if the Mozilla XBL2 spec has something similar to sxbl:handerGroup with xbl2:handlers (http://www.mozilla.org/projects/xbl/xbl2.html#handlers0), but Mozilla XBL2 also defines its own xbl2:handler element (http://www.mozilla.org/projects/xbl/xbl2.html#the-handler). My guess is that Ian&friends recognized that it makes sense to have a handler element that is different than html:script and that it is easier to add a handler element to the XBL2 spec (and sell XBL2 to the W3C) than the more general-purpose approaches of adding a handler element to XHTML or adding a handler element to XML Events (and thereby making XML Events a prerequisite for XBL2). Given progress on CDF/WICD, I expect that XML Events will get universalized in the not-too-distant future such that it works across both XHTML and SVG within the context of WICD, in which case my vote would be to add a handler element to XML Events rather than the future W3C XBL spec. Jon -----Original Message----- From: public-cdf-request@w3.org [mailto:public-cdf-request@w3.org] On Behalf Of Bjoern Hoehrmann Sent: Monday, January 30, 2006 11:30 PM To: Maciej Stachowiak Cc: Charles McCathieNevile; public-cdf@w3.org Subject: Re: CDR: Event-related markup * Maciej Stachowiak wrote: >> Note that there is no XML Events Working Group. The HTML Working Group >> was chartered to maintain XML Events, but the charter expired long ago >> in 2004 as you can read on http://www.w3.org/MarkUp/Activity so there >> wasn't and isn't any maintenance of the Recommendation. Which is quite >> a problem, I recently implemented XML Events plus the modifications >> defined in SVG Tiny 1.2 and most of it did not make much sense at all, >> XML Events alone even less. > >In that case it seems like a major problem for any other spec to >depend on XML Events. Yes, I'm very worried about the SVG Working Group's decision to somehow adopt vanilla XML Events, just like I was and still am worried about the http://www.w3.org/mid/42b4d54f.193020078@smtp.bjoern.hoehrmann.de new similar but different <handler> elements, XHTML 2.0 has one, XBL2 has another, sXBL has its own, then SVG 1.2 joins the club, and so on. It's a pity but it seems it's less work to reinvent this for each format rather than to invent it just once. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 31 January 2006 08:20:36 UTC