Ted Leung wrote:
> My 2 cents on this: I'm not actually convinced that pull parsing the DTD
> is necessary. I think it's much more important to have the document
> pull-parsed.
That's probably true. Once we have a way to parse DTDs separately
into grammar objects, then people might want to do it. I guess we
can address this problem once people start asking for it. As such,
should I change the default in the document parser back to fully
parsing the DTD even if the document is being pull-parsed?
> What are the problems in document parsing -- is it only with the namespace
> binder?
I was just wondering how people thought about a pull parser
always returning only one event per call to parseDocument. I was
highlighting the general problem that the scanner doesn't know
and can't control what happens downstream. For example, if there
were an XInclude component in the pipeline, then it could create
a bunch of extra events. It is the responsibility of the pull
parser at the end to buffer appropriately and only return a
single parsing event.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
