ModSAX: Proposed Core Properties

[David Megginson]

MikeDacon at aol.com writes:

 > So, what I'm saying is that I would like to be able to choose
 > whether to interface to the Parser via events or via a DOM.  If you
 > agree with this, I believe using the return type is more
 > appropriate than getting a resultant property (as I suggest next).

This is easy enough to build on top of SAX, but I think that it's
probably out of scope for SAX itself.  SAX is meant to be a relatively 
simple, low-level layer that people can build on.

 > If for some reason the above is not palatable, the same could be 
 > accomplished under the current scheme if we added a 
 > property:
 > 
 > http://xml.org/sax/properties/dom-document <org.w3c.dom.Document> (read-only)

The nice thing about ModSAX is that you're free to try this yourself
-- just define a property like

  http://www.aol.com/mdaconta/props/dom-document

(or whatever URL you can use based on your AOL account) and let the
market decide whether to support it.  Perhaps one of the people who
has written a higher-level utility package that supports both SAX and
DOM would like to use this or something like it.


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)