> I'm trying to find a non expensive tool that could be used instead of > Mercator (now Ascential DataStage) for our mapping needs. We deal > with the EDIFACT standard and the tool should work on Windows > environment. We are looking for a product, not a third party service. >
Depending on the details of your circumstances, you may want to consider xmlLinguist, the EDI-to-XML Translator. It's affordable (mapeditor retails for $79.95 USD and the runtime engine is free) and very simple to use. The tool only does one small step, translating the format of the document from text into XML, but after that you can apply many standard XML technologies (such as XML Schemas, XML Stylesheets, etc.) to get the document to where you want to go. The engine is bi-directional as well, so it can go from EDI to XML, as well as XML back into EDI. Read our tutorial http://www.sysonyx.com/xml-to-edi-850 for a quick sample on how it's done (and how to piece things in a basic way using VBScript). > Also, along the lines of this research I have found the > terms "Translation tools" & "Mapping tools" used indistinctly in some > places whether not in others, which could be the main difference > between these terms? > Ah, terminology is always confusing in IT (for example, .NET, how many different ways can that be interpreted?). It seems (and I'm sure that members on this group will quickly jump in to correct me) that when talking about EDI, a "translator" often refers the the 'glue' pieces, the ones that pick the documents up from VANs, FTP, files, etc. and shuffle them to other applications for processing. "mapping tools" are one these other applications, the ones that transform the document from EDI 850 to your proprietary Order import file, etc. I've probably further confused the issue by calling xmlLinguist an EDI-to-XML Translator. In the realms of XML, "translation" doesn't exist, you "transform" documents from one XML into another with stylesheets. To help bridge the gap between XML and EDI, the term "Translator" is used for xmlLinguist to emphasize the fact that xmlLinguist doesn't _tranform_ the document, only translate from one file format to another (i.e. text to XML and visa versa). HTH, Bryce K. Nielsen SysOnyx, Inc. (www.sysonyx.com) Makers of xmlDraft, the Smart XSD Editor http://www.sysonyx.com/products/xmldraft . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> 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/
