> I agree that SAX ought to provide access to unparsed entities but I
> don't think this is the right way to achieve it. For a start, I can
> have an ENTITIES attribute, so all these methods would need two
> arguments (the index of the attribute in the attribute list, and the
> index of the token in the value).
An excellent point, and one that I missed in the original SAX.
> I think a better approach is for the processor at the end of the prolog
> to pass an object to the application that provides information about all
> the declared notations and unparsed entities.
>
> XP has a DTD object that does this, but it might be better to call it
> something else (like UnparsedEntitySet) since SAX might someday be
> extended to provide full DTD access.
This is a good idea, but I need to find a way to avoid using the
Java-specific Enumeration class that your example uses (since I've
already eliminated it from AttributeList).
All the best,
David
--
David Megginson ak117@freenet.carleton.ca
Microstar Software Ltd. dmeggins@microstar.com
http://home.sprynet.com/sprynet/dmeggins/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)