Cart
[Home] [By Thread] [By Date] [Recent Entries]
I think this is all useful discussion, but I also think that it's
getting too monolithic. In our experience with using a simple API to
access a (normalised) SGML document stream, which led to our LT XML
tool, we found that most of the quick and simple tools (often
DTD-specific) we wanted to build were most easily constructed on top
of an I/O model, not and event model or a grove model. That is, one
where the basic APPLICATION structure was
while (bit=GetBit(xmlStream)) {
select (bit.type) {
case startTag: ...
case endTag: ...
case textData: ...
case PI: ...
}
}
I'd be sorry to lose this level, but am not clear where it fits in the
developing picture. Is this the 'XML Parser API'?
ht
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@i... the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa@i...)
|
