Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: xml-dev Mailing List <firstname.lastname@example.org>
- Date: Fri, 27 Feb 1998 22:22:16 -0500
James Clark writes:
> 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 Megginson email@example.com
Microstar Software Ltd. firstname.lastname@example.org
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)