XML supports two kinds of external identifiers and I think that an
interface that supports them both is actually simpler than one that does
not -- in the sense that it mirrors the language structure better. If we
leave publid identifiers out, then users must guess at our reason for
doing so. Being different from XML is non-intuitive.
> We could simplify things further for most users if the XmlAppBase
> class implemented final versions of these handlers and maintained its
> own entity stack, providing an additional getCurrentEntity() query
> method (not part of the interface).
We could replace "getCurrentEntity()" with "getCurrentLocation(Entity
entity, int linenum, int colnum, int offset)" and kill two birds with
one stone.
Paul Prescod
-- http://itrc.uwaterloo.ca/~paprescoArt is always at peril in universities, where there are so many people, young and old, who love art less than argument, and dote upon a text that provides the nutritious pemmican on which scholars love to chew. -- Robertson Davies in "The Cunning Man"
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)