medici

Mentioned elsewhere in the thread, but it's possible to parse the (mostly) machine readable specs for EDIFACT messages to create schemas for reading massages. A library that I wrote decades ago has some Perl which can do that to produce XML definitions from the UN/EDIFACT published directories. I hope that it can be useful to others: https://github.com/davidcoles/medici

This takes me back 20+ years to when I had to create/parse EDI messages for various retailers when I worked at an independent record distributor. I wrote a C library to parse the messages with callbacks in the style of Expat. There's binding for Perl to make it a bit easier to use. EDIFACT, X12 and Tradacoms are supported. Anyways, unlikely anyone might need it these days, but there are some Perl scripts which can interpret the EDIFACT "directories" (basically message schemas), so you don't have to build your own message syntax definitions. It should be possible to convert the XML output that it generates into the Python needed to define message syntax, element definitions, etc. Best of luck with it - there's a whole world of crazy industry standards to explore. Oh, and consulting is a possibility if anyone needs it ;-) -- https://github.

I haven’t done any work on EDI for many years so it might be a bit out of date, but in case it’s of any use to anyone I wrote an EDI parsing library and processor for many of the EDIFACT message specs: https://github.com/davidcoles/medici