Hi Group,
Nice that this issue of Transportation has been raised.These days I'm
working on Design Architecture for "Internet EDI".If we look at it closely
the only difference between EDI and Internet EDI is the term "Internet".
This addition of the word "Internet" doesn't change the meaning of EDI. In
essence ,what we are trying to achieve is to make EDI ,internet enabled.
As Leo Mendelson has pointed out clearly that we have three options SMTP,FTP
and HTTP.All these protocols are Internet based (TCP/IP)protocols. X.400 for
sure doesn't fall in this model because it is based on a client/server kind
of an architecture,though it is highly reliable as it maintains a copy at
last hop. SMTP is server to server communication at Port 25 based on DNS
resolutions.
All these three protocols are in the Application Layer of the TCP/IP
Reference Model and all of these were developed keeping in mind the specific
purpose they were supposed to serve. What is e-mail in crude terms? It is an
FTP only with added features that makes it e-mail. FTP is meant to simply
send/receive files ,while e-mail is again send/receive files but with added
features like recipient , sender , subject ,date ,etc are explicitly
mentioned in the file itself. What makes it more different from FTP is that
the receiver can simply press the "REPLY" button some of the relevant fields
like recipient and Subject etc. get automatically filled and the person only
has to type the reply to the mail, rather than getting involved in giving
references to the mail he is replying to.Do you all see that "Re:" or "Fw:"
which gets automatically attached with your "Subject field" when you are
replying/forwarding a particular mail.This is what makes it e-mail and not
FPT.
With this kind of a framework EDI will be another protocol which will fall
in the Application Layer of the TCP/IP Reference Model. As on date this
protocol is not there, but definitely people are working towards it. So in
essence Internet EDI will be e-mail with added features that will make it
"Internet EDI". These added features will be Trading Partner Relationships,
Data Tracking and the various standards (like ANSI X.12,UNEDIFACT,ODETTE and
of course XML which is just evolving)
regards
Ashwani
>From: Leo Mendelson <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Antwort: Transportation Standards
>Date: Tue, 11 Jul 2000 16:35:39 +0200
>
>Hi!
>
>What about X.400!? Did someone know about how to transfer files which
>using of the X.400 protocol? Is there any special software needed or can
>you use "normal" e-mail protocol (SMTP) for this?
>
> > you can use the INTERNET in several ways. The IP protocol is the
>foundation of the
> > INTERNET. On top of that TCP is used most of the time, but UDP may be
>used as well.
>
> > On top of that there are many choices for 'application layer' protocols.
> > Popular choices for transferring XML text entities or streams (files,
>transactions) are:
> > SMTP (simple mail transport protocol) (MIME could go with that - there
>is a MIME
> > FTP (file transfer protocol),
> > HTTP (hyper text transfer protocol).
>
>Leo Mendelson
>
>--
>mendelson-e-commerce GmbH
>phone: +49 30 89 09 10 22 fax: +49 30 89 09 10 19
>http://www.mendelson.de/
>Home of m-e-c eagle - Opensource B2B integration tool based on XML/XSL
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
