Lists Home |
Date Index |
- From: "Bill la Forge" <firstname.lastname@example.org>
- To: "John Cowan" <email@example.com>, <firstname.lastname@example.org>
- Date: Fri, 26 Mar 1999 08:52:04 -0500
From: John Cowan <email@example.com>
>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]"
>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.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)