Alan .. your words are well taken .. along with the other contributors to
this thread. We must all stay open minded, as well as factual in these
discussions. We see too many instances where XML/EDI is over simplified by
vendors and the real facts often remain in a diminished state.
Gene Hockemeyer
Sunbeam Corporation
Manager EDI and EC Business Development
561 912-4877
[EMAIL PROTECTED]
-----Original Message-----
From: Alan Kotok [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 9:52 AM
To: Steve L. Bollinger; [EMAIL PROTECTED]
Subject: Re: The XML/EDI has no Clothes!
Steve:
First, many thanks for raising this issue, which is important to our work
on business data exchange. You provided a valuable service.
My point in bringing up the reporting errors stems from my own work as a
free-lance writer (BA -Journalism -Univ of Iowa, National Assn of Science
Writers, yada yada yada). When I wrote for Ecom World for eight years, I
did not send in one word unless I was sure of the content. Much of my
writing was about bar codes and other automatic identification
technologies, and I wanted to actually see evidence of the systems working
before I wrote about them. I also tried to understand how they worked and
how they benefited their users.
Mr. Lucas seems to come from a different school of thought. His story does
not mention one XML vocabulary by name -- none, zero, nada -- nor does he
cite problems with specific vocabularies. He also missed the extensive
work being down on framework specifications such as ebXML that try to
address the serious interoperability problems. Add in the factual errors
and you have work I would not accept in my publication.
Please understand that we need the debate you have brought to us
here. These are legitimate and serious issues. But we need better
discussions from the trade press than what Ecom World brought us. Best
regards.
Alan Kotok
Director, Education and Information Resources
Data Interchange Standards Association
[EMAIL PROTECTED]
+1 703-518-4174
** DISA's E-Business and Internet Conference, 7-9 March 2001, in San
Francisco.
http://www.disa.org/conference/annual_conf/index.htm **
At 05:50 PM 1/31/01 -0800, Steve L. Bollinger wrote:
>At 10:38 AM 1/31/2001 -0500, Alan Kotok wrote:
>>My good friend William Kammerer of Foresight Corporation pointed out two
>>glaring factual errors in the story ...
>
>I agree that there are a few errors here. My point in showing this was
>that this article is the first time (that I am aware) someone has tried to
>point out the real world difficulties in XML/EDI implementation in a trade
>magazine. Before this is was rosy hype leading companies astray.
>
>At 11:18 AM 1/31/2001 -0500, David RR Webber wrote:
>>Please do NOT confuse XML-EDI with XML/edi !!!!!!
>>Quite simply all that you have been describing is XML-EDI.
>>We said THREE YEARS AGO that would not work - but who are we?
>
>Most of us were not here three years ago. Please state again the
>difference between XML-EDI and XML/edi. The web page does not clearly
>state that nor does your email.
>
>David I don't think that distinction will matter at all to the major point
>I raise because regardless of this you still need to integrate the
>received document into the back-end data base of the receiving
>partner. It is this point of semantic translation that is the problem in
>XML-EDI or XML/edi (or X12, etc.).
>
>At 11:18 AM 1/31/2001 -0500, David RR Webber wrote:
>>I'm sorry that CISCO has poured millions into the hole
>>finding this out - but I am not in the least bit surprised.
>
>I expect by this you would also have to apply this same comment to
>RosettaNet who continues to form these standards? Is this not also
>XML-EDI and bound to fail?
>
>
>
>
>------ 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
>---------------------------------------------------------------------
>Plan on attending the upcoming meeting during DISA's conference:
>http://www.disa.org/conference/annual_conf/index.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 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
---------------------------------------------------------------------
Plan on attending the upcoming meeting during DISA's conference:
http://www.disa.org/conference/annual_conf/index.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 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
---------------------------------------------------------------------
Plan on attending the upcoming meeting during DISA's conference:
http://www.disa.org/conference/annual_conf/index.htm
