| EDI to XML transformation - new 2019 approach ("approach A") |
|
|
(version 19.11.2019) The idea is to browse for some file on your own system. That file should contain the (valid) Edifact string to be transformed. The transformation gives you an xml file. You can also use the same but extended transformation, producing extended meta-info using xml-attributes. (added 14.06.2023 - originally this version delivered XML containing the Edifact-style codes, which are pure codes. At some point that had been adapted and this version now delivers XML containing "codes with meaning" - what we coined as our "alternaitve values". The subsequent effect is that the transition from that XML back to the original Edifact does now such reverse translation too...) |