Lists Home |
Date Index |
- From: "Bill la Forge" <firstname.lastname@example.org>
- To: <MikeDacon@aol.com>, <email@example.com>, <firstname.lastname@example.org>
- Date: Sun, 7 Mar 1999 21:51:12 -0500
From: MikeDacon@aol.com <MikeDacon@aol.com>
>I like the idea of SAX filters but still feel that you should allow
>access to a DOM Document if the implementing Parser can supply one.
>I won't restate the suggestion here as it was covered in a previous email.
>However; that could greatly simplify a filter-writer's job.
Well, that might depend on the job of the filter. You may want to use a filter
to prune out the parts of the document you are not interested in BEFORE
the DOM is built.
In general, I see several places where you might want to use a filter:
o Transform events from a parser into something to be output.
o Transform events from a parser before being accessed by an application.
o Between a parser and the DOM.
o Transform events from a DOM walker into something to be output.
Note that in the last case, if the DOM walker shares its internal state (position in
the DOM tree) with the filters that come after it (using something like MDSAX),
we get a lot of XSL-like capabilities.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)