donzog

7 ms·

1.
Free, bidirectional conversion between EDI X12 and JSON(edination.edifabric.com)
1 points by donzog 6mo ago|0 comments
2.
EdiNation is the new EDI Notepad(edination.edifabric.com)
1 points by donzog 9mo ago|0 comments
3.
by donzog 1y ago
We do have a Registered Trademark. Thank you for the reply.
4.
What to do if another company is using our brand name without permission?
2 points by donzog 1y ago|5 comments
5.
Web API for translating EDI files – host it in-house to avoid compliance hassle(edination.com)
1 points by donzog 4y ago|0 comments
6.
by donzog 4y ago
Ah, no worries mate, it's a software toolkit and not a pizza - can't make everyone happy. We are in the business of simplifying things for devs, and I'm sorry that you had a bad experience with our product, but if you found a
7.
by donzog 4y ago
The different EDI standards are pretty explicit about the sequence of messages (276/277, etc.), acknowledgments (technical, functional, etc.), and conversation items (interchange IDs, duplicates, sender/receiver IDs, etc.). And ye
8.
by donzog 4y ago
Are they still in business? I heard they fired lots of developers, bless them.
9.
by donzog 4y ago
Go with Stedi.com.au instead, it's lighter. Longtime EdiFabric developer. Always had a plan.
10.
by donzog 4y ago
+1 haha, indeed.
11.
by donzog 4y ago
Yep, that's becoming mainstream. UNECE is currently working on a JSON schema for EDIFACT, due next year, as far as I'm aware. The EDI standard was made independent from the transport (AS2, SFTP, etc.), so files can be transferred
12.
by donzog 4y ago
The article outlines that API IS NOT JSON over HTTP, albeit it's the most popular case. You can send a text file/binary (that contains X12, EDIFACT) to an API as easily as JSON. In fact, that's what EdiNation does; it allows
13.
by donzog 4y ago
+1 I like your syllogism. API isn't EDI if you apply any logic to determine this. The article's goal was to dispel the typical pitting of EDI vs. API by showing that EDI can be API.
14.
by donzog 4y ago
"An EDIs standardized format is implementated with methods that are accessed through an API." - so true. Then everyone starts calling this either EDI or API for short :)
15.
by donzog 4y ago
Agreed always bugged me too. We have both a .NET library and a web API product, and I still can't tell when customers refer to our API, whether they mean the library or the web API. It's another case where everybody has their own
16.
by donzog 4y ago
+1 At least that's what we built OpenEDI on top of - https://github.com/EdiNation/OpenEDI-Specification
17.
by donzog 4y ago
But this is not EDI's fault, it's the power-crazed companies and their management that bastardize EDI. Because they can.
18.
by donzog 4y ago
There is always the first time. Much like we created the first EDI API https://edination.com/
19.
by donzog 4y ago
Ha, ha, can't believe DC/Marvel haven't invented the ZZ-man/woman already
20.
by donzog 4y ago
So true. The purpose of EDI/X12 was to be the single source of truth. It was okay while the military used it, as they would have stricter control over the standard, but once it was unleashed into the world of business... There is not m
21.
by donzog 4y ago
There isn't a JSON transport protocol either. And EDI is not a format; it's a general reference for multiple data standards and the rules for exchanging data instances of them. One of the issues is that people have different opini
22.
by donzog 4y ago
I second that; it is the core of all EDI issues. Outdated software and ancient complex maps that no one dares touch. That's why so many adapter/data cleansing projects spring up to isolate the COBOL-style software from the rest.
23.
by donzog 4y ago
EDI is standardized; however, the standard is not enforceable. So it's not like you can't send crappy data or some custom flavor of the format. The problem is that the receiver of this "standardized" data has to work wit
24.
by donzog 4y ago
I still work in the EDI-parser software but retiring to the mountain has never been more appealing.
25.
by donzog 4y ago
How is the experience any better? EdiFabric is a library that you install locally, not a web API. As far as I'm aware, tsedi can't generate acknowledgments, can't import SEF, can't parse healthcare X12, can't parse
26.
EDI vs. API(support.edifabric.com)
104 points by donzog 4y ago|97 comments
27.
Why EDI and API are different sides of the same coin
1 points by donzog 4y ago|3 comments
28.
Master B2B and Healthcare EDI files for free(edination.com)
1 points by donzog 5y ago|0 comments
29.
EdiNation makes EDI so easy(support.edifabric.com)
1 points by donzog 5y ago|1 comments