Re: external parsed entites (was: A unique ID question ?)
On 11 Nov 99, at 1:44, David Brownell wrote: > Perhaps the general issue is that whenever DOM starts to offer > APIs for populating a DOM Document, there need to be options > about what features should be exposed. For my usage, things > like EntityReference and CDATASection (vs normal Text) would > hardly ever be used. > > Or perhaps there should be variants of Element.normalize() that > give you other options for getting rid of extra tree nodes. > "No adjacent text nodes" is covered. How about flags for cases > like "don't use EntityReference", "don't use CDATASection", > and "don't use Comment"? That seems like an idea worth tossing around. We'll be starting to figure out requirements for Level 3 shortly - how about you write up this proposal in a little more detail? We have in the past discussed "normalizing" CDATA sections, but didn't find enough compelling use cases, and it only takes a couple of steps for the user to do it themselves, so it wasn't added. If you can add some compelling use cases, that would help the case for adding yet another set of methods to the DOM :-) Please send any proposal to www-dom@w... so it's archived in the right place, and I'll make sure the DOM WG discusses it when we get that far. thanks, Lauren 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 unsubscribe, mailto:majordomo@i... the following message; unsubscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
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