Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Handling internal general entities with SAX
 > Yes, I realize that I want to "break" the XML rules, but I feel like my > intentions are good. I guess I'm of the camp that believes that kind of rule breaking is not good, since it necessarily ties applications to particular, and nonconformant, parser implementations. Neither of those consequences seems to me like a good thing in the least. > We definitely fall into the "no DTD" group for our data exchange. I had > considered chaining an InputStream in before the Reader to "import" the > entity declarations. This handles the case for all of the known entities, > but not for unknown ones. Sounds to me like you'd be better off using some magic syntax that's not part of XML. You can't use XInclude for two reasons: first, it doesn't work inside attributes; second, the latest drafts still have that annoying XPointer support. And you can't use XML entities, since you're saying that you can't constrain your data language closely enough to preclude unknown entities. You could cleanly layer a syntax like "$name;" on top of any XML processor. In fact, it'd be simple enough to implement some sort of SAX pipeline component that'd postprocess all attribute values and character content to substitute "$name;" values. The cost would be an extra scan over most characters in the input data, but in terms of layering it's clean. - Dave 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
