[Home] [By Thread] [By Date] [Recent Entries]
If the structures are identical other than some of the element
and attribute names, you could write a rule-based XSLT sheet
that replaces the names. This would get very tedious if there are a lot of names to be changed. The XSD is not relevant to the process except to inform you in writing the transformation. It simply doesn't carry the information needed to bridge the gap. I suppose one could write an XSLT that would examine both the XSD and the sample file, make an attempt at guessing the transformation based on certain structural similarities, and output templates based on these guesses. But you would still have to work through the result to ensure that it was correct, and you would be more likely to overlook something. Lukacsy Gergely wrote: Hello! XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|

Cart



