ModSAX: Proposed Core Features (heretical?)

[Bill la Forge]

From: Simon St.Laurent <simonstl at simonstl.com>
>I like the filters approach very much.  Perhaps it might be possible to
>implement that approach, and control it through options set with ModSAX -
>among other things, being able to order the parser to use a particular
>DTD/schema to process a document would get this poor DB admin out of his
>nightmare.  Hmmm....


Remember that some applications might want to process more than one
type of document. Validation and processing may vary depending on
document type, so long as the application (or its associated filter complex)
gets to decide which document types are valid and how they are to be 
validated/processed. In terms of events, this would require a document
router of some kind.

Bill


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)