From a programmer's point of view, classical EDI data like e.g. UN/EDIFACT interchanges have been a constant source of frustration: They are too complex for makeshift tools, are basically ignored by leading programming languages - but play a major role as business enablers in virtually all large and many smaller companies. Proprietary converter products came to the rescue - introducing special purpose, proprietary mapping languages which frequently left a lot to be desired.
The edi4r toolkit takes a different approach to mapping: It takes Ruby, a state-of-the-art object-oriented programming language known for its high productivity, as the basic mapping language, and equips it with classes and methods that greatly simplify the processing of EDI data. As a result, programmers can combine the full power of a high-level, general-purpose programming language with the convenience of a special EDI class library.
The project is distributed as a series of Ruby Gems, each with its own RDoc pages. Their latest releases are also provided here. Select the documentation you want to see: