[xsl] many to one OR one to many?

[Jason White <jewhite@xxxxxxx>]

I'm looking at converting some training materials we have (in Word 
currently) to XML/XSLT.  The target is Web/Web-printer-friendly/print 
output.  Server resources are a sensitive issue and updates aren't 
going to be daily or even weekly, so the web version will be batched to 
static files with some dynamic functionality (search, 
most-accessed-topics etc.) wrapped around it via keywords and some PHP. 
So...the output for the web is multiple files, while the print is 
[ideally] one document (PDF). The material will mainly be organized as 
'reference'.

I'm wrestling with:
whether I would go with multiple small xml files that I could compile 
into one output for the print, but would match the html files 
essentially
OR
one xml source file that matches the print, but can be output into 
multiple files (via some element in the structure that separates) for 
the web.

I would prefer the multiple xml to one for editing management and 
because IMO, the web output is more important...especially since there 
will be a web printer-friendly version.

Anybody experienced one or both of these scenarios and have some 
pointers?  I have seen some references to doing this, but not much more 
than that.

Also, I am investigating user-friendly XML/XSL tools for the rest of 
the group. XMetaL by Corel is the lead candidate at the moment. Any 
other suggestions?

TIA!

Jason


XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list