David Brownell wrote: > That is, does this spec increase parsing costs by requiring such > state to be stacked even in event-based parsers which currently > don't need to record such state? They already have to maintain a stack of open element type names. > My suggestion would be to specify the behaviour of a "namespace > processor" -- distinct from an XML processor! -- and define its > behaviours in terms of the data provided to it by an XML processor > (driven either by parsing events or by some parse tree). This > processor would only need markup related data as input. This has to wait until we have a spec for what the output of an XML processor is, but I agree this would be a good way to explain it. JamesReceived on Sunday, 16 August 1998 05:39:05 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.30 : Tuesday, 12 April 2005 12:17:16 GMT