This is correct. XML's initial purpose was to
put applications on line for key entry. EDI is simply the language we've all
agreed to speak. Unfortunately, us EDI folk tend to look at key entry as a
mortal sin. But you know, the data's got to come from somewhere. If it can't be
culled, it's got to be keyed.
Thanks Morris.
XML and EDI are not the same things.
XML is designed so that browsers can display documents written in
XML
without having to access their type definition for validation. XML is
based
on a concept that documents are composed of a series of entities.
Each
entity can contain one or more element. Each element has certain
attributes
or properties that describes how it should be processed. XML
provides a
formal syntax for describing the relationships between
entities, elements,
and attributes that make up an XML
document
EDI is defined as The exchange of standardized document
forms between
computer systems for business use. Each EDI translator has
its own language
for receiving files and translating them and forwarding
them to the trading
partner and receiving files translating them and
sending them to their ERP
or what ever system.
I guess what I am
trying to say is one is a language and the other is a way
to standardize
documents that are shared between applications.
There are a number of
standards people are using today associated with XML,
one being
EDI.
We have a standard that has been developed over the years. Why
waste all of
the time and effort spent on development and testing just to
come up with
something new? Why not just make a revision to the current
standard if it is
not acceptable in its current state.
Thank
you,
Duane Kevin Morris
Global Practices
Shell Services
International
Office: TSP-2043
email: [EMAIL PROTECTED]
Tel:
713-241-3872 Fax: 713-241-1924 Mobile:
713-702-1684
-----Original Message-----
From: Emad N. Georgy [mailto:[EMAIL PROTECTED]]
Sent:
Thursday, June 01, 2000 3:59 PM
To: Brad Berendt; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:
Re: Software - Objectivity
I don't know how this all started but
the original poster from Micron PC did
not mention anything about
replacing EDI with XML. In fact, I think the post
is quite relevant to
what many organizations are doing these days -- that
very evaluation of
B2B vendor tools. Ironically, Scott Shulman asks us
to,
"Relax!" and I return the favor, "Relax!" ...the
original poster never
mentioned replacing EDI.
-Emad
-----
Original Message -----
From: "Brad Berendt" <[EMAIL PROTECTED]>
To:
<[EMAIL PROTECTED]>
Cc:
<[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent:
Thursday, June 01, 2000 1:37 PM
Subject: RE: Software -
Objectivity
>
>
> I agree. Has anyone
heard the phrase, "if it ain't broke, don't fix
it"?
Many
> companies have spent plenty
> of money in
their current EDI inftrastructure. And guess what?
These
are the
> "guts" of many integrated
processing
> systems today. I believe XML has its strengths and
applications but don't
rule
> out good old EDI.
>
>
Brad Berendt
> Sterling Commerce
> District Consulting Mgr -
E-Commerce Solutions Microsoft
> Managed Services Division
>
Office: 614-791-5782 Fax:
614-793-7045
>
>
>
>
>
> Scott Shulman
<[EMAIL PROTECTED]> on
06/01/2000 04:26:31 PM
>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>
cc: (bcc: Brad Berendt/Dublin-ISG)
>
>
Subject: RE: Software - Objectivity
>
>
>
>
People, RELAX. Everyone thinks this XML thing is going to replace
this
thing
> called EDI, Just because this is the newest buzz word.
What happened to
> CPFR, That was last year's buzz word. What happened
to VMI, That was two
> years ago buzz word. We are still several years
out before this thing
called
> XML takes over the
world.
>
> Scott Shulman
> Director of E-Commerce
>
K-Swiss inc
> 818-706-5203
> [EMAIL PROTECTED]
>
>
>
> -----Original Message-----
> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
>
> Sent: Thursday, June 01, 2000 12:31 PM
> >
To: [EMAIL PROTECTED]
> >
Subject: Software - Objectivity
> >
>
> Having recently completed a 5 month evaluation process of XML -
B2B
> > Servers
> > and vendors, I have some relevant
experience in the process of selection
> > to
> >
share. We did the following:
> >
> > *
Evaluated vendors according to their industry participation and
> >
experience (Rosettanet in our case)
> > * Met with this
subset of vendors
> > * Participated in 3 vendors'
proof-of-concepts
> > * Scored each vendor according to a
formal weighted scorecard
> > * Considered development plans
and schedules
> > * Completed a subjective evaluation
>
>
> > The last item, "subjective evaluation" is very
important and I would
like
> > to
> > expand on
this. In the fast evolving software industry, products can
>
> change
> > on a daily basis. During our recent
evaluations we continually needed
to
> > see the
"latest" version of a vendor's product. Our
"objective"
scorecard
> > was likely obsolete even
before it was finished. This reality led me to
> > recognize
that the "relationship" with a vendor was even more
relevant
to
> > our needs than the "daily" feature
list.
> >
> > The ability to cooperate in product
development, future feature
> > development,
> > and
priorities are more important to our company's B2B
e-commerce
success
> > than a particular list of features in any
given day. A relationship,
and
> > channel of
communications with a vendor's decision makers is vital. The
>
> B2B
> > / XML vendor relationship should not be that of
buyer/seller, but that
of
> > "partner". The B2B
/ XML solution vendor is a virtual extension of our
> > internal IT
department. The vendor who recognizes this and
delivers
based
> > upon this relationship is worth serious
consideration.
> >
> >
0============================0
> > | Kevin Benedict
>
> | B2B E-Commerce Manager
> > |
micronpc.com
> > | 208-893-1738
> > | [EMAIL PROTECTED]
>
> | "The Process is the Product"
> >
>
> 0============================0
> >
> >
>
>
> >
> > ------ 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 join the XML/edi Group complete the form located
at:
> > http://www.xmledi-group.org/xmledigroup/mail1.htm
>
>
> >
>
>
> ------ 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 join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
>
>
>
>
>
>
>
>
>
------ 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 join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
>
>
>
------
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
join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------
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
join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ 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 join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
HTML>
|
