[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX2: relative ordering of startDocument() & startDTD() events?
David Megginson wrote: > > David Brownell writes: > > > Keeping in mind that the most common example of this problem is > > > > <element attribute="some &entity; &references; are here"/> > > > > I'd think basically anyone actually trying to use the start/end entity > > callbacks would conclude that they just can't work. > > How about if we renamed them to start/endExternalEntity and forgot > altogether about signalling internal entity boundaries? That'd work for me. (Just saw this note, sorry -- mailer troubles.) But I don't think I really understand the requirement here. I know that DOM exposes such boundaries. But every time I've tried to do anything with them in a DOM that produced them, I had to write code to rip them out -- they're just trouble. Is there another source of a requirement for such boundaries, other than partial DOM support? Because I'd as soon not reinforce that troublesome part of DOM. Were this feature to stay, would those boundaries need to be reported, or would this be exposed in a feature flag? Or would the meanings of the existing {ex,in}ternal-entities feature flags cover that issue? - Dave *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/threads.html ***************************************************************************
|
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
|