Reverse XSL! site syndication http://www.reversexsl.com/j 2010-09-05T18:43:26+01:00 text/html 2009-05-18T09:14:14+01:00 http://www.reversexsl.com/j http://www.reversexsl.com/j/index.php?option=com_content&task=view&id=21&Itemid=63 ReverseXSL software sprouted in 2007 from the failed attempt to find a straight and flexible structured-messages parser that would be affordable, can be learned quickly, and would not come with dozens of interface screens, gigabyte workstation and server software, plus hundreds of parameters to configure, because communication platforms existed already. Moreover, it had to digest structured airline messages (IATA IMP, AHM, SSIM...) which, if you know them, bear one of the most screwy syntax of the EDI arena. text/html 2009-08-13T06:14:24+01:00 http://www.reversexsl.com/j http://www.reversexsl.com/j/index.php?option=com_content&task=view&id=41 Just like all of us, you once thought to use XSLT for a flat-file to XML transformation with the idea that it would be almost as magical as the XML-to-anything developments you formerly achieved. You expect me to reveal the secretly hidden <xsl:input>(?) method and XSL functions that you haven't used before and that will hopefully provide the solution but... we have to acknowledge that beside framing your entire file with <tag>..myFile..</tag> and using substring() extensively... oups! text/html 2009-05-27T08:40:14+01:00 http://www.reversexsl.com/j http://www.reversexsl.com/j/index.php?option=com_content&task=view&id=30 You have a screwy flat file to import into your application and you are reluctant to endorse one of the solutions presented so far to you... actually, you fear that there could be more parameters to set-up than data elements in your file! text/html 2009-05-28T06:25:00+01:00 http://www.reversexsl.com/j http://www.reversexsl.com/j/index.php?option=com_content&task=view&id=31 Most likely, you had to coordinate three activities:understand the details of the message syntax at stake and formalize a representation in codedeal with the programming language in itself: edit code, build, unit test, debug, add code to handle exceptionsdesign and code the logic to deal with optional pieces, repeated blocks, nested structures, conditions, ...We propose that you drop the last two, and boost your productivity for an even better result! text/html 2009-05-28T09:23:00+01:00 http://www.reversexsl.com/j http://www.reversexsl.com/j/index.php?option=com_content&task=view&id=32&Itemid=63 An XML document is, by construction, neatly divided into pieces organized as a tree of nodes: element nodes, text nodes, attribute nodes, namespace nodes. When you get a new XML document, the unknowns are names and contents of nodes, but you can trust the cuts, i.e. the tree. In other words, you see first the structure, and then the contents. These features have forged XSLT which is based on XPath expressions (to select nodes) and a hierarchical application of node processing templates.An arbitrary text document is just the reverse: you see first a melted content, and then you have...