This is a fantastic discussion. Thanks everyone.
I think the discussion is zeroing in on the keys to XML-design-for-streaming.
That's exciting!
Wendell, you made these two fantastic statements:
(1) Streaming is useful when branches of
the document can be processed without
reference to other branches.
(2) The smaller your branches (each of
which offers a discrete processing context),
the more you benefit.
I understand (1). But I am not clear how (2) logically follows from (1). Would
you explain further please?
You are saying, "Flatter is better" when it comes to XML-design-for-streaming,
right? Why? I sense that may be right, but I can't articulate why, I am hoping
you can.
What certainly seems to be true is this, "Design XML such that processing its
nodes does not require knowledge of any preceding nodes" (Ken, excellent
observation about preceding axis). But what does that mean, practically? What
practical guidelines could be written to achieve that design goal?
/Roger
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--