Re: Running XSLT transformation

[Adam Glauser <adamglauser@xxxxxxxxxxxx>]

Aaron Bartell wrote:
> I am not necessarily trying to steer you away from XSLT, but note that
> you just introduced a potentially unnecessary failure point and
> potentially CPU intensive processing that could be eliminated by just
> just buckling down and doing it all in RPG.

I'm probably going to do it in RPG eventually, without the extra XSLT 
step.  The problem is that the vendor we're getting the data from seems 
to have changed their web application, from which we are retrieving this 
data.  The XML is _really_ ugly, in that it's designed to be displayed 
as a report as opposed to being designed for data transfer.  For 
example, it had silly attribute names like "textbox49" for the account 
title.  Not only that, but the account numbers are embedded in text 
strings like "Account: ERB..... Montreal (QC)" instead of being an 
account tag or attribute.

> Another thing to watch out for is if you "flatten" the XML out, make
> sure you are still adhering to the XSD (i.e. be mindful of repeating
> sections).

Can you expand on that?  I'm not using a validating parser.  FWIW, the 
schema to which the existing document links is an invalid URL, so I'm 
not sure I can make it much worse :)


> Just some thoughts that don't really answer your question (sorry) :-)

Appreciated nontheless.