They played separate roles.  Ralph provided the technical input and design.
Buddy provided the "words".  They worked for Joe, who was my predecessor at
TDCC.

I  quote from Ralph:

"I was the system engineering consultant for the 1975 effort and tasked to
make all of the definitive work "hang together like a system." Another
consultant to the project at that time was Buddy Bass who was tasked to
design and produce a structured comprehensive complete standards manual. We
worked for Ed Guilbert and Joe Carley at TDCC who coordinated the
cross-industry endeavor, supplying leadership, concept, strategy, direction,
and a work plan."

-----Original Message-----
From: William J. Kammerer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 3:54 PM
To: [EMAIL PROTECTED]
Subject: Re: XML/EDI - Why does it have to be so hard? ...Or at least
that's how monkeys do it


Paul Lemme, of Commerce One, told Dan Tharp and Rich Rostrom a few weeks
ago that the "creator of the EDI standards is still with us, so I would
suggest any question about the genesis of EDI structures be directed to
Ralph Notto."

Dear Paul:

I must correct you.  Actually, there were three "fathers" of EDI: Joseph
G. Carley, Jr. and Earl J. "Buddy" Bass, in addition to Ralph Notto.
They were all honored as 1995 Co-recipients of the DISA Edward A.
Guilbert EDI Professional Award.  The questionable paternity of EDI
enabled its survival, since more males cared for the infant hoping that
it was theirs.

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"accelerating time-to-trade"

=======================================================================
To contact the list owner:  mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/

=======================================================================
To contact the list owner:  mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/

Reply via email to