- From: Chris Lilley <chris@w3.org>
- Date: Thu, 2 Sep 2004 10:32:42 +0200
- To: martijn <martijnw@hotpop.com>
- Cc: www svg <www-svg@w3.org>
On Thursday, September 2, 2004, 12:31:59 AM, martijn wrote: m> Quoting here from the abstract: >> sXBL is intended to be an SVG-specific first version of a more >> general-purpose XBL specification (e.g., "XBL 2.0"). The intent is >> that, in the future, a general-purpose and modularly-defined XBL >> specification will be developed which will replace this specification >> and will define additional features that are necessary to support >> scenarios beyond SVG, such as integration into web browsers that >> support CSS. Once a general-purpose XBL is defined, sXBL would just >> become an SVG-specific subset (i.e., a profile) of the larger XBL >> specification. m> My question is: why making an SVG-specific version first and then a more m> general-purpose XBL specification, XBL 2.0? Because a more general purpose one will take longer to make and require input from more groups. The idea is to transition the RCC over to sXBL so that the eventual XBL 2 is an upwards compatible superset of sXBL. m> When will this XBL 2.0 version see the daylight? Certainly. There is in fact already work on a draft of it. m> Anything that will be defined here as sXBL will certainly also be in the m> more general XBL 2.0? Yes - its to be a strict superset. m> So in the near future there will be 3 different XBL versions? Mozilla's m> XBL, sXBL (implemented by Adobe?) and XBL 2.0 (implemented by ???). The plan is that Mozlla XBL will transition over to W3C XBL, and be implemented in other user agents besides Mozilla. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Thursday, 2 September 2004 08:32:42 UTC