Lark 0.90 available, with an application

Norbert Mikula nmikula at
Fri Jun 27 16:33:01 BST 1997

On Fri, 27 Jun 1997, W. Eliot Kimber wrote:

> At 05:04 PM 6/26/97 -0700, Tim Bray wrote:
> >For Xh, I also, after getting it working, realized that I had re-used
> >Peter Murray-Rust's trick of just having a .class per element-type
> >(Class.forName() and Class.newInstance(), gotta love 'em) - I wonder if
> >this is just a coincidence or is this the basic paradigm on which XML 
> >software is going to be built?  If so, it might make sense to wire
> >a standard class-finder call into XAPI.
> It makes sense to have one class per element type (after all, you usually
> have distinct types because they have distinct semantics and thus distinct
> behavior). You can take this one step further if you add architectures:
> your element-type-specific classes can themselves be derived from
> arch-form-specific classes.

I have also had a similar idea a few days ago.*1
I would like to know whether you guys think it makes
sense to go even further and have also this kind of
calls for attributes and other potential "nodes" in 
our parse tree. I would think so.

Now the question remains if this approach should substitute
the event base stream that built the bottom layer of
our XAPI-J discussion. I think the event based approach
should still form the base. Many people, I believe,
feel still very comfortable with it.


Best regards,
Norbert H. Mikula

= SGML, XML, DSSSL, Intra- & Internet, AI, Java 
= mailto:nmikula at 

xml-dev: A list for W3C XML Developers
Archived as:
To unsubscribe, send to majordomo at the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa at

More information about the Xml-dev mailing list