The example is not convincing.
Apart from the loss of flexibility (for future enhancements) you incur
when you demote an element to an attribute you'll also have to modify
other programs, frequently not your own. Expect protests.
Most importantly, note the important feature described in the XSLT 3.0 draft:
"An effective design pattern is to write a streaming transformation
that takes a snapshot of each element in turn, processing the snapshot
using the full power of the XSLT language. Each snapshot is a tree
built in memory and is therefore fully navigable. For details see the
snapshot and copy-of functions."
Tweak the processing, not the data.
-W
On 24/11/2013, Costello, Roger L. <costello(_at_)mitre(_dot_)org> wrote:
Hi Folks,
I created a few slides that discuss the issue of designing XML for
streamability:
http://www.xfront.com/XML-Design-for-Streamability.pptx
I am interested in hearing your thoughts on the slides. Do you agree with
them? Is there anything else you would add to them?
/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>
--~--
--~------------------------------------------------------------------
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>
--~--