Proposed new kind of SAX2 thing, with example

[Bill la Forge]

From: John Cowan <cowan at locke.ccil.org>

>I believe there should be some way within SAX2 to ask for
>parser properties (in the JavaBeans sense).  One example is the
>architectural DTD public ID, which XAF provides access to
>but can't report because it doesn't fit the SAX event model.


Why not use the get(featureID)?

>Another case is the current element stack.  Every parser (or almost
>every parser) has to keep one of these around, and it would be
>useful to have "currentStackDepth" and "stackedElementType[n]"
>properties.
>
>What's needed is to have some means of discovery.  Perhaps it's just
>enough to use the JavaBeans mechanism.


One of the ideas behind MDSAX was to have a shared element stack.
But if SAX2 developed such a concept, then:

    1. A parser has the option of sharing its element stack and 
    2. When a parser doesn't share its element stack, a filter could be used.

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)