On Monday, March 04, 2002 8:57 PM, David RR Webber wrote: > > Correct me if I am wrong - you are talking about using XSLT in > combination with custom Java code - the purpose of the Java code > being to pre-parse the EDI into XML so that the XSLT can then > process the EDI? > This is correct - EDI must be transformed into an XML syntax prior to using XSLT (although this transformation need not be developed using Java - any programming language will do).
> The one obvious issue with this is the need to process codelists > within the EDI itself - so its not necessarily a simple <tagging > exercise (in X12). Actually it is. Take a look at http://www.vcml.net. VCML supports all codelists for all versions of both X12 and EDIFACT. VCML can transform any EDI transaction into XML syntax. Stylesheets can then be applied for presentation or additional transformations. > My experience is that XSLT is not designed to handle non-XML source > data, and so struggles in this area. XSLT totally fails in this area. XSLT can only be used with XML inputs (although the transformation outputs are not so restricted). Depending on your performance requirements, XSLT might not provide the ideal solution. PS: I agree with David regarding your book - highly recommended. JohnE www.Vitria.com ------ XML/edi Group Discussion List ------ Homepage = http://www.XMLedi-Group.org Unsubscribe = send email to: [EMAIL PROTECTED] Leave the subject and body of the message blank Questions/requests: [EMAIL PROTECTED] To receive only one message per day (digest format) send the following message to [EMAIL PROTECTED], (leave the subject line blank) digest xmledi-group your-email-address To join the XML/edi Group complete the form located at: http://www.xmledi-group.org/xmledigroup/mail1.htm
