Event-based textual filtering

Like SAX, XML components are reported as events Developers familiar with SAX and similar approaches should be able to work with this logic quite easily.
A filtering foundation Because events include a return value, consumers of these events may be (but are not required to be) filters for content, acting as pre-processors.
A foundation on which to build a modular parser Given this set of events, an "XML parser" processor could perform all the work normally done by an XML 1.0 parser in the context of a more open framework for rule-setting, processing style, and result reporting.
Context as a tree These filters can lean on the context object anytime they need to know about information that has arrived previously.