|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: Re: <TECH> Tool for pruning XML Schemas?
> Yes, Gentran is over-kill for your scenario, however, there are EDI
> products
> that
> would certainly fit your scenario. We can set up a complete in-house
> Walmart
> solution
> that includes all communication and translation capabilities for all
> required Walmart
> documents, including 810 turnaround documents, for a couple of thousand
> dollars.
>
That's not my point though. My point is that for the "little" guy EDI can be
more confining than liberating. A good XML solution for the same price
(roughly a few thousand dollars) will go a *lot* farther than an EDI
solution, because it can be used in a lot more scenarios than an EDI one and
typically it's easier to customize. Not only B2B with non-EDI partners, but
also standard EDI and XML ones, and even some A2A within the many in-house
applications small shops usually have.
My example is a prime candidate. If the small shop has an EDI Translator
setup for a large vendor, his other two dropshippers that are small and
don't want to have anything to do with EDI, he'll need some serious
customization (or a second solution) to handle his non-EDI vendors. A good
XML middle tier would be able to handle both scenarios (and arguably better,
cheaper, and easier than an X12 Translator).
But ultimately I fall back on my main point, every tool and technology has
its strengths. Examine your situation before prejudging a particular
technology away. What may be a fit for some will not be for others.
Bryce K. Nielsen
SysOnyx, Inc. (www.sysonyx.com)
Makers of xmlHack, the Simple XML Editor
http://www.sysonyx.com/products/xmlhack
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
