Lists Home |
Date Index |
- From: Lars Marius Garshol <email@example.com>
- To: "XML Developers' List" <firstname.lastname@example.org>
- Date: 25 Mar 1999 19:14:58 +0100
* Gabe Beged-Dov
| Are there other cases (other than text-normalization ) in SAX2 that
| require the parser to aggregate notifications and save state (other
| than that required for well-formedness checking)?
Not right now, no.
| My impression is that SAX(2) is intended to be minimalist. If a
| filter network can be composed on top of SAX2 that provides the
| desired capabilities, then SAX2 doesn't need to provide that
This is true, and personally I was of the opinion that normalize-text
was better left to external filters.
| Maybe normalization is a good candidate for an example filter
Maybe, but we still need to reject invalid combinations of
LexicalHandler and normalize-text, so somehow the filter and/or parser
will need to handle this.
This whole issue just strengthens my conviction that we need to
specify filter handling within the SAX2 core. This will need to deal
very carefully with parser encapsulation for approaches like this one
to be really feasible in implementations.
It wouldn't be much fun if a filter did the normalization without
telling the parser and thus caused trouble with the LexicalHandler,
and no hint of this trouble ever reaching the application.
| The fact that it would need to be configureable (concerning CDATA
| handling) might make it a more useful pedagogical aid.
As to how filters work, you mean? Well, we should let ourselves be
affected by that. And, besides, whitespace normalization is a far
better example, I think.
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)