& XSLT * Robin Berjon <robin.berjon@[...].fr>  [2005-10-17 12:15]:
>  Ideally, this sort of functionality which turns a
>  non-conformant stream into a conformant one should be
>  abstracted into a separate module (a filter) so that other
>  pieces of the SAX infrastructure could reuse it. 

I thought about this but didnâ??t want to suggest it yet. A problem
with this approach is that the behaviour of serialisers when used
directly is left undefined. It would be good to know for definite
sure what the serialisers are expected to do. If a serialiser is
*supposed* to infer the missing information, then serialisers
should implement this behaviour directly, not in the form of a
wrapper. They donâ??t need to implement this themselves; it could
be done inside something like XML::SAX::Base (maybe
XML::SAX::Writer::Base?) which a serialiser can then inherit
from.

It might well be that the spec says â??a serialiser must expect all
the information and must not infer anything�, which is fine too.
Then inference would be implemented in XML::Filter::SAXNormalize
or some such.

But itâ??s important to know precisely how a serialiser is supposed
to behave, otherwise weâ??ll have interoperability problems. Err,
in fact, we already do â?? I canâ??t give XML::SAX::Writer the same
events I need to give XML::Genx::SAXWriter (and I havenâ??t tried
libxmlâ??s SAX-to-DOM interface yet, so I expect more surprises).
This may be a bug in ::SAX::Writer or ::Genx::SAXWriter, or both,
but we need a clear spec to decide.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/> 
_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs