[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

using xsl:result-document in a non-list situation

Subject: using xsl:result-document in a non-list situation
From: "Mark Wilson" <mark@xxxxxxxxxxxx>
Date: Tue, 19 Aug 2008 11:28:49 -0700
 using xsl:result-document in a non-list situation
All of the examples for using <xsl:result-document> to produce multiple files (at least those that I've seen) write to a new file each time they encounter a new instance of a controlling element structure in a 'list' and use "position()" to help name the file. What technique do I apply to a document containing a <List> of <Items> such as the one shown below? Here the controlling element is not simply another <Year> element, but <Year> elements with differing content: 1998, 1999 and so on, with each year repeated within the source document many times. Ideally, the output would be a series of files, one for each different <Year> content (1998.xml, 1999.xml) and each sorted internally by <IssueNumber> and <Page>.

I have not been able to see how the stylesheet should be constructed. Any hints would be appreciated.
Thanks,
Mark


Source example:
<List>
   <Item>
       <Data>
           ...
       </Data>
       <Article>
           <Year>1999</Year>
           <IssueNumber>1</IssueNumber>
           <Page>6</Page>
       </Article>
   </Item>
   <Item>
       .......
   </Item>
</List>

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.