SAX: Next Round

david at david at
Thu Jan 21 22:07:48 GMT 1999

Lars Marius Garshol writes:

 > | 2. Lexical Event Handler
 > | ------------------------
 > | 
 > | What do we really need here?
 > An event to signal the end of the internal subset would be nice, in
 > addition to what you listed.

You'd get that through the start/endExternalEntity event -- the
external subset is just a special entity, read after the internal
subset (we might want to use the special name '[dtd]' for it).

 > | Now, the best way to find out about namespace prefixes is to introduce 
 > | a new handler interface:
 > | 
 > |   public interface NamespaceHandler
 > |   {
 > |     public void startNamespacePrefix (String prefix, String uri)
 > |       throws SAXException;
 > |     public void endNamespacePrefix (String prefix)
 > |       throws SAXException;
 > |   }
 > This looks slightly bothersome to me at first sight, but maybe it's
 > the way to go, since the solution I think best isn't backwards
 > compatible anyway:

SAX in general is designed to be bothersome, in part to encourage
people to build decent, friendly interfaces (SAXON, MDSAX,
DocuverseSDK, Sun's XML library) on top of it.  The idea is to defer
any design decisions that we can defer.

All the best,


David Megginson                 david at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list