It happens over and over again since the beginning of civilization.
Cheaper isn't always cheaper. Just like you have to spend money to make
money, sometimes you have to spend money to save money.
-Steve
"William J. Kammerer" To:
"EDI-L Mailing List"
<[EMAIL PROTECTED]> cc:
Subject: Re:
[EDI-L] <sales>looking for mapping tools
02/14/2005 04:52 PM
Brian, are we talking past one another? Richard Hug *is* using a
translator - and it presumably takes care of "all the rest of the good
stuff you need, such as compliance checking and trading partner
maintenance." I just assumed he was saying he relies on Perl to do the
heavy lifting of mapping. I love that idea.
And I really wasn't dissing Mercator. But walk into a book store
sometime: you'll see Perl this and Perl that. Perl is ubiquitous -
maybe even more so than XSD and XSLT. But not one book about Mercator
and type trees. I'm supposing that with all other things being equal,
I'd rather have Perl code dumped on my desk than some random vendor's
map.
Now, speaking of roses: you forgot me this time. Did I say something
wrong? I loved the arrangement you sent me last year.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
----- Original Message -----
From: "Brian Lehrhoff" <[EMAIL PROTECTED]>
To: "William J. Kammerer" <[EMAIL PROTECTED]>; "EDI-L Mailing List"
<[email protected]>
Sent: Monday, 14 February, 2005 12:25 PM
Subject: Re: [EDI-L] <sales>looking for mapping tools
Yea, sure, great. Now all you need to do is find a partner that can take
the XML instead of X12. Call Wal-Mart, tell them that you're changing.
See how far you get, and report back to us.
If you want to ditch that expensive translator for a free (or lower
cost) one ... fine. You can do all of your translation in c# or perl.
Are you going to build all the rest of the good stuff you need, such as
compliance checking and trading partner maintenance? It is still
infinitely cheaper to buy than build. Unless you decided to grow the
roses yourself :)
=====
Brian Lehrhoff
EDI Consultant
201-913-4506
----- Original Message -----
From: "William J. Kammerer" <[EMAIL PROTECTED]>
To: "EDI-L Mailing List" <[email protected]>
Sent: Monday, 14 February, 2005 11:08 AM
Subject: Re: [EDI-L] <sales>looking for mapping tools
Hush!! If folks get an inexpensive EDI translator and learn Perl to do
their mapping, then that puts the kibosh on at least one of many good
reasons to move to XML. They'll find out that they don't have to put up
with the agony of "point-'n'-click" mapping, Mercator "type" trees,
Gumtran macros or bad or non-existent technical support to get useful
things done.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
----- Original Message -----
From: "Richard Hug" <[EMAIL PROTECTED]>
To: "Kevin Galioto" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[email protected]>
Sent: Sunday, 13 February, 2005 09:30 PM
Subject: Re: [EDI-L] <sales>looking for mapping tools
Dave,
About a year ago I switched to the scripting language PERL. It was
easy to learn and seems to handle all my client's mapping needs. I
use Trading Partner PC from Emanio, as the translator, a low priced
translator with plenty of installs. (www.emanio.com).
Oh yes, the price of Perl is free, it is part of the open source
movement. (www.perl.org). EDI syntex is controled by Trading Partner
PC, and Perl writes just about any file that exists.
Regards,
Richard Hug
New Tampa Consulting
.
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
.
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
