[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Doubt in using <A> within XSL
/ "eduardo.gutentag" <Eduardo.Gutentag@xxxxxxxxxxx> was heard to say: [...] | > server, maybe I'll have to maintain my source as dozens of | > separate XML documents. Linked together with XLinks? | | Hm, I don't know if that's the right question, Norm. Seems to | me that it boils down to whether XSL is a server-side | style-sheet language (a la Jade, or rather, like Jade can be | used), or a client-side one. If the latter, which I believe is | how the current submission approaches it, I agree with you that the current work on XSL is focused on the client side attachement of style (and that's where I think it should be focused). | the chunking should be done at the server-side, This is another possible approach to the problem. I had suggested that the chunks would be maintained on the server, but I think you're suggesting that the document be maintained on the server as one (or several) large units and that the server should send only the appropriate chunk. | but that brings up the issue of how the style sheet is then | supposed to traverse the tree when all it has is a bit of a | chunk to work on. It would seem to me that in this case the server is going to have to send additional information. Perhaps a <chapter> on the server becomes a <chapter-chunk> when sent by the server, with additional metadata stuck at the top to indicate the titles and URIs of preceding and next chunks, pointers to the TOC, etc.? Since we can represent this data as well-formed XML, we can still use XSL to style it. --norm XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|