Announcement: SAX Java Implementation (pre-release)

[Michael Kay]

>I have put together a new, beta version of SAX with quite a few
>changes; here are some change highlights...

Only one technical comment: if we allow a character stream
to be passed to the parser as the primary input, it does seem
inconsistent that resolveEntity() cannot return a character stream
for other entities, e.g. the DTD. (In fact, if resolveEntity() could return
a stream/reader, one could rely on this to provide a stream/reader
for the primary input as well, simplifying the main parse() interface).

Other comments are on the documentation:

- I think we should recommend people implementing the callback
handlers to subclass from the base implementation, as this allows
their code to remain compatible if the interface is widened in a
later SAX version.

- The specifications tend to say "you" when they mean the application
writer, and "the parser" when they mean the parser writer. It would be
useful to spell out the roles more clearly (call them the parser and the
application) and make it very clear for each interface whether it is
supplied by the parser or by the application.

Mike Kay, ICL


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