Lets remeber that EDI started when size did count. The state
of the art in communications was 2400 baud.
Mark Malatak wrote:
Now this attitude,
I can subscribe to. One things for sure: 90% of the fortune 1000 still
employ EDI for most of their EC. There are several valid secure methods
for moving EDI data over the internet. Even some, like our own, that allow
you to continue to use your existing translators without any new software
or changes to your envelopes. Plus they provide all of the niceties
traditional EC networks provide at one eighth the cost. XML is a workable
solution, but all our clients tell us when they translate the same document
into XML versus EDI, it increases in size ten fold. Well, of course it
does, because you're, for all intent and purposes, sending database definitions
along with your data. In EDI, it is only a character that separates fields. So,
while time has proven XML a workable solution, it will take more time to
make it efficient, cross industry compatible, and stream lined, and thus
a valid solution. Hell, we've been working on EDI since the late
60's!
-----Original
Message-----
From: Scott Shulman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, June 01, 2000
4:35 PM
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
HTML>
------ 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
|
