EDI is a process and, as defined, that process requires a standardized
format. EDI is not that format. But here is where the language in the
definition is somewhat sloppy. By "Standardized Format" I believe the
definition assumes the format includes semantics. One could more
specifically refer to the data format and the semantic definitions & context
of the "Standardized Format".
The data format of ANSI X12 & EDIFACT is labeled records containing
delimited fields arranged in nested loops. ANSI X12 & EDIFACT use that data
format in providing semantic meaning for use in the electronic communication
of standard business doucuments.
XML is an example of a tagged data language, a technology used in the '70s
to control printer output rather than screen output. One of XML's major
values lies in the ability of applications to read it and create formatted
screen displays. The data format is also labels(tags), delimited fields and
nested loops. Without someone providing a semantic context for the use of
XML it has little value in any business process.
Clear, right? Jim
----- Original Message -----
From: "Mohan Wanchoo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 2:02 PM
Subject: Fw: Re: Internet, EDI and XML
> A Hilton,
>
> I would like to differ on your description of EDI being a *process* and
not
> a data format structure. Everywhere you look EDI is defined as the
> "Computer to Computer exchange of data in a Standardized Format".
>
> You need the data formats supported within a particular EDI standard to
> carry out the *process* of EDI that you are referring to. The data
formats
> are the pillars of EDI.
>
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
