[snip]
> You can always built a more powerful layer
> on top of an event stream. Furthermore we
> should also consider the work of the DOM
> group. Their results will have a considerable
> impact on our work as well.
>
> If we can provide a flexible low level
> layer, we can always add more fancy and
> specialized post-processors on top
> of it.
I believe it it is important not only to design the low-level
interface such that a grove (or other-high level interface) can be
implemented on top of it, but also to design the low-level interface
such that _it_ (at least the relevant portions of it: i.e. the event
stream and associated classes) can be implemented on top of a grove
interface.
Another concern I have is that the terminology used for the two
interfaces (low and high) be consistent. A programmer who learns one
interface should not have to learn a different vocabulary in order to
use the other. This is also true across languages: a person using
an XML parser in Java should not have to learn a different vocabulary
in order to use an XML parser from C++ or Perl.
As the SGML property set has already been published (in DSSSL, and
soon in the HyTime 2nd Edition) and is in use, I suggest that it be
used as a terminology reference for new SGML and XML interface
design.
-peter
-- Peter Newcomb TechnoTeacher, Inc. 233 Spruce Avenue P.O. Box 23795 Rochester, NY 14611-4041 USA Rochester, New York 14692-3795 USA +1 716 529 4303 (home) +1 716 464 8696 (direct) +1 716 755 8698 (cell) +1 716 271 0796 (main) +1 716 529 4304 (fax) +1 716 271 0129 (fax) peter@petes-house.rochester.ny.us peter@techno.com http://www.petes-house.rochester.ny.us http://www.techno.com