Oh, and while I am at it, I should probably mention that outsourcing this function can be a great option. You sure don't have to worry about what software, how much does it cost to buy and what is the yearly maintenance, does the software include old/new versions, can your software handle those trading partners which bend the standards, hiring experienced personnel to do the mapping etc.....
Doug -----Original Message----- From: Doug Anderson [mailto:[email protected]] Sent: Wednesday, November 24, 2010 8:22 AM To: 'Michael Mattias/LS'; [email protected] Subject: RE: [EDI-L] Re: Translator options Michael You clearly do not understand. XML solves all of the problems associated with EDI. :-) Doug Doug Anderson Chair, ANSI ASC X12 Transportation Subcommittee Vice President Sales Support Kleinschmidt 847-405-7457 (office) 847-826-3531 (cell) < http://www.kleinschmidt.com/ <http://www.kleinschmidt.com/> > http://www.kleinschmidt.com <http://www.kleinschmidt.com> -----Original Message----- From: Michael Mattias/LS [mailto: [email protected] <mailto:mcmlserve%40talsystems.com> ] Sent: Wednesday, November 24, 2010 8:16 AM To: [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: Re: [EDI-L] Re: Translator options > Hello Anne, > > Personally, I recommend to use the (W3C) standard XSLT language to perform > any translation, including the EDI - X12, EDIFACT, etc. - ones ;-) You > would then need a parser/serializer (to/from XML) , Well, that makes two (2) opinions... Why go ANSI X12 ==> XML ==> ERP format and back when you can cut out the middle man and just go ANSI X12==>ERP ? >but your mapping/translation will be expressed in a standard language that >can be processed by dozens of software ;-) ANSI X12 format data IS a standard language and CAN be processed by 'dozens of software!' Then again, to the man who knows only the hammer, all challenges look like a nail! Michael C. Mattias Tal Systems Inc. Racine WI [email protected] <mailto:mmattias%40talsystems.com> <mailto:mmattias%40talsystems.com> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
