Cart
[Home] [By Thread] [By Date] [Recent Entries]
> I am curious of whether it is possible to still approach a > special tailored > tree approach, which is popular among processors and which I have > understanding for, while still being collaborative with plain DOM. Sure, that's exactly what Saxon does. Michael Kay http://www.saxonica.com/ > > Let's say a hypotethical XSLT engine was to be used in a > DOM-based(ref > counted, impl separated) web-browser for ordinary client-side > processing, as > well as a support component in arbitrary applications such as > exporting > Office formats, is there then any hopes for doing something > significant at > the tree structure? In short, the engine may be passed a DOM > structure, and, > for example in the case of a web browser, must deliver. > > Is there any approaches of supporting multiple tree-backends? > E.g, when the > engine is used for "pure" XSLT processing, it can take care > of all steps, and > build a tree tailored for its own purposes. > > It's vague, but perhaps someone can deepen the topic.. > > > Cheers, > > Frans > > > ----------------------------------------------------------------- > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > initiative of OASIS <http://www.oasis-open.org> > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > To subscribe or unsubscribe from this list use the subscription > manager: <http://www.oasis-open.org/mlmanage/index.php> > >
|
