This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Suppose that a document is processed in streaming mode, and there is an accumulator that is not declared streamable and perhaps is actually not streamable. What happens? I imagine it should be a dynamic error to invoke the accumulator functions in a non-streamable accumulator when the context node is a node in a streamed document.
We (Abel+MK) reviewed this and decided that a dynamic error was the appropriate response.