At 09:26 AM 6/24/2003, you wrote:
It provides an a couple utilities over SAX and DOM that allow you to only
build DOM fragments for the subtrees of the Document you'll actually be
transforming against. It currently has a simple facility that reads the
XSLT template for matches and keys to build a list of elements, it then
passes matched sax events onto a DOMBuilder to build a DOM fragment, this
DOM fragment can then can be transformed against using the same XSLT.
The problem with this approach in the general case is that there are many
occasions when there is an expectation for a node to match a built-in
template: the absence of a template to match a given node is not sufficient
warrant for removing that node.
It sounds like a pretty cool idea for situations where this is checked
against, however. (If I understand correctly.)
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list