[PEPr] Comment on Payment::Payment_EDIFACT
| From: | David Jean Louis | Date: | Tue, 26 Oct 2010 11:54:50 +0000 |
| Subject: | [PEPr] Comment on Payment::Payment_EDIFACT | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53873@lists.php.net to get a copy of this message | ||
Hi Reinhard,
Back in 2006, at work and on my paid time, I implemented a full featured
EDI php library, it currently supports UN/EDIFACT only, but the goal was
also to support X12 and EANCOM standards.
*All* UN/EDIFACT messages and revisions are supported, from 1994 (D94B) to
2007 (D07A).
What I did was implementing a generic parser that parsed edifact message
structure stored in xml files generated by a php script (it is not included
in the source, I think I've lost it :().
It's a huge project, pear packing is not terminated, there's still many
things to do (for example, the name should be File_EDI and not EDI as
Christian noted).
If you're interested on what needs to be done, I'll try to write a todo
list, but as far as I remember, the goal was to provide a core package (the
Parser and Element classes), and subpackages for each revision of the
standard xml data files (I think this part needs a custom role for PEAR
packaging).
I've never had time to finish it and I do not plan to work on it again
either, to be honest it was not a very fun experience to write a parser for
this prehistoric and cryptic format :/
It's ok to open-source it, so you may want to have a look at the
sources...:
http://code.google.com/p/izi-sandbox/source/browse/#svn/trunk/php/php_edi/
Regards,
--
David
--
http://pear.php.net/pepr/pepr-proposal-show.php?id=648