relation between DOM, SAX, and Schema?
This current thread regarding data vs. API prompts a few questions I've had for a while. 1. Is the difference between DOM and SAX one of programming style only (implementation efficiency aside)? http://www.megginson.com/SAX/event.html seems to say so. Or is there more to it than "trees vs. events": that SAX is in the end a driver API that must accomodate anything a low-level parser wants to offer, while in the end DOM is a least-common-denominator procedural model for browsers? 2. How does/will metadata affect either? Once the many XML-based schema proposals (DCD, XSchema, etc.) are consolidated, when I parse some XML with respect to a schema, I would like my annotated tree (grove, whatever) to be able to tell me meta-info about the nodes using that schema (what is its default, is this optional, what is the description string for this data type or this element type, etc.). I would like to use the very same API to ask questions not just about element values, but about the element metadata as well. It seems that right now neither DOM nor SAX is ready for this? -mda 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/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe 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