canabrook
commented
3 years ago Hi Karl,
Thanks for diligence in making contact. The email setup changed, and apparently the json @ forwarding got dropped.
The JSON-based integration is certainly more common these days, replacing the earlier XML-based approaches. Fortunately, the underlying EDI parser and framework is not tightly coupled with either, so both JSON and XML are equally supported, in either direction, and for EDIFACT as well as X12.
Please contact me at @. @.> for pricing other other information.
Scott
On Jun 23, 2021, at 3:11 AM, Karl @.***> wrote:
Hi,
I'm reaching out here, because I don't think I've had any response from the json@ address in the README (apologies if I have, but I've not found it in spam/quarantine).
The company I work for (@GlodoUK https://github.com/GlodoUK) is interested in getting read/write capabilities from X12 (and later down the line likely EDIFACT), and I think edi-json is probably one of the easier solutions to get into our existing workflows.
We're basically after pricing at this point to be able to compare
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BerryWorksSoftware/edi-json/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQDKPDDLZQVQ4VQEGAF5PTTUGJMXANCNFSM47FIPUPA.
Hi,
I'm reaching out here, because I don't think I've had any response from the json@ address in the README (apologies if I have, but I've not found it in spam/quarantine).
The company I work for (@GlodoUK) is interested in getting read/write capabilities from X12 (and later down the line likely EDIFACT), and I think edi-json is probably one of the easier solutions to get into our existing workflows.
We're basically after pricing/support model at this point to be able to get an understanding of where it fits in the ecosystem.