[
Lists Home |
Date Index |
Thread Index
]
> Going the other way might require reordering the groups of records to place all with
> identical attributes together. Or the stylesheet could explicitly state the matching
> attributes that cause a <g><e/></g> block and that would be pretty easy. What is
> interesting is that users would do this grouping themselves ... they would do it as a
> matter of convenience when creating the <g><e/></g> blocks.
>
> The ultimate improvement of your example is an identity transform copying everything
> verbatim except this expansion of the <g><e/></g>. That is the stylesheet that would
> substantially implement what I am proposing for files preprocessed against the
> stylesheet. How easy is that? :)
>
Both of those (which would each only require a line or two of xslt) are
day to day faq questions on xsl-list Perhaps you should move this there,
or see the usual reference for grouping on Jeni's site
http://www.jenitennison.com/xslt/grouping/
Grouping and flattening of hierarchical data is just what XML is all
about, so I'm not sure I understand this thread really. I think you are
proposing that the element names be hard coded into applications but
that would be going against the whole point of XML which is a meta
language for defining vocabularies. Specfic vocabularies such as xhtml
have fixed element names but XML has (almost) no fixed names at all.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
|
