& XSLT A. Pagaltzis wrote:
>  But why not allow the caller to omit the prefix if he so chooses?
>  Why shouldnâ??t I be able to do the sensible thing and leave
>  prefixes to be managed by the serialiser when I know that the
>  code Iâ??m writing is part of a toolchain which is *not* broken?

What's normally expected from a SAX stream is that all fields be 
defined. I know it's painful, but it's the only approach that can be 
guaranteed interoperable with everything. SAX -- especially at the event 
production side -- is meant as a common layer for module writers to use 
more than something which people more at the end-user side of the 
spectrum would use. In other words, it tends to be a little bit too 
low-level to be practical, again especially if you're creating events.

That being said XML::SAX::Writer does make a number of fair efforts to 
try to simplify this for its users, if only because many SAX streams 
aren't really conformant. However, while still stable and generally 
fine, it hasn't seen enhancements that had been planned in a long while. 
Hopefully, someone will pick up maintenance soon enough and start 
applying that kind of patch. So feel free to patch it to behave more 
like you would expect, and send the patch here. I'm sure someone will 
want to pick up the ball.

-- 
Robin Berjon
   Senior Research Scientist
   Expway, http://expway.com/


_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs