Re: EDI over http?

[lincoln@xxxxxxxxxxxxx (Lincoln Yarbrough)]

Dear Ma Fei Chun:

Please allow me to describe my viewpoint that there are two ways to
perform "EDI" using HTTP.

One is through forms where a human being actually fills out or views a
form. Maybe the other trading partner is sending and receiving an EDI
document, and something in the middle is translating between a form and
EDI. This is what GE's Tradeweb (http://www.getradeweb.com) and other
types of web form services are doing. This should replace the use of fax
machines and the receive-and-print "EDI" going on today.

Second, and maybe even more important, the Auto (http://www.aiag.org),
Natural Gas (http://www.neosoft.com/~gisb/), and Telco
(http://www.atis.org/atis/tcif/) industries, and others, are moving
towards using HTTP as an EDI file transfer protocol. The intent among
all of these industries, I believe, is to one day have one generic
standard (the next task of the IETF EDIINT EDI Work Group), but they are
focused on their immediate business drivers for now. This protocol would
be primarily used by two trading partners to exchange data in a
real-time, point-to-point fashion. Advantages are obvious.

Regards,

Lincoln Yarbrough


Ma Fei Chun wrote:
> 
> Hello!
> 
>         Can you tell me what are the strengthness and weakness of EDI over
> HTTP?
> 
>                                                 Best Regards,
>                                                 Ma Fei Chun, Patrick

-- 
Lincoln Yarbrough               Email: lincoln@xxxxxxxxxxxxx
Actra Business Systems          Tel#: 1.408.542.3261
610 Caribbean Drive             Fax#: 1.408.542.3210
Sunnyvale, CA 94089             Visit: http://home.actracorp.com