RE: How to mark every 5th output record.
At 11:30 AM 3/11/2008, you wrote:
In retrospect it would have been a lot easier to do it in C++, especially since we have access to the source code of the application that exports the XML. The choice to use XSLT was chosen as a stress test to validate the XML schema and to prove to third parties that they could use XSLT to implement their own file converters. In other words: "If we can export to *that* format using XSLT, then our customers can export to any file format".
That's interesting. In view of the fact that other considerations were put ahead of technical ones, one shouldn't be surprised to see a price being paid on the technical side.
Regarding your defense of XSLT, I'm not trying to force xslt to do something it wasn't designed to do. I'm simply trying to find the path of least resistance to accomplish that last 0.05% to meet spec compliance.
Well, maybe, but even without knowing any of the details, the running consensus is "this sounds like a job for XSLT 2.0". Nor do I doubt that a clean implementation would be possible even in XSLT 1.0 -- if you're willing to run the optimum number of passes (which might be more than two but probably isn't more than three). Part of the reason pipelining is an approved methodology is that it simplifies so much, even while it looks cumbersome up front (as someone suggested: Andrew?).
Then too, it seems like the industry must have been gasping for an openly-specified general-purpose transformation technology back in the early 2000s, given how much weight XSLT 1.0 has been asked to pull over the years.
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