Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Megginson wrote: > Lars Marius Garshol writes: > > The DOM's text-normalisation feature does *not* normalise CDATA > sections, but I think that SAX's should. > 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)? To say it a different way, are there other examples of SAX2 providing a high(er) level service on behalf of the applications other than raw notification of lexical and structural events? 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 capability. If there are multiple variations in how the desired capability can be provided (as in the normalization example), then this is an even better indicator that it should be left to a "policy" decision at a high layer. Maybe normalization is a good candidate for an example filter network. The fact that it would need to be configureable (concerning CDATA handling) might make it a more useful pedagogical aid. Gabe Beged-Dov www.jfinity.com xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
