Ok, I've read the "article." Doesn't EDI fix most of the problems that he
says are broken features in XML? I get challenged constantly with "This
methodology seems to work pretty good, but, if anyone can come up with a
better one that works i'll gladly take a look at it."
And I'd sure like a piece of that 12 month, $1,000,000 project to fix
something that isn't broken.
"William J. Kammerer" wrote:
> Thanks to Greg Olsen, of Contivo, Inc., for discovering this gem. See
> "Technologists Debate the Best Way to Implement XML," by Peter Lucas,
> published 01/22/01 on Ecomworld.com. Anytime you let a "journalist"
> loose with a word processor, misquotes, havoc and lies invariably
> abound. Even so, the trash to text ratio in this one is so excessive
> that a mere two snippets hardly do it justice. Read for yourself at
> http://www.ecomworld.com/online/columns/read.cfm?contentid=381.
>
> "In addition, structures defining XML documents are inherently
> simpler...The structure is so simple that e-mail can qualify as an XML
> document."
>
> "...Unicode, an 18-bit coding language created by Microsoft Corp,
> Redmond, Wash,...supports 64,000 definitions per character and can
> translate documents written in almost any language."
>
> William J. Kammerer
> FORESIGHT Corp.
> 4950 Blazer Memorial Pkwy.
> Dublin, OH USA 43017-3305
> +1 614 791-1600
>
> Visit FORESIGHT Corp. at http://www.foresightcorp.com/
> "Commerce for a New World"
>
> =======================================================================
> To contact the list owner: mailto:[EMAIL PROTECTED]
> Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
--
%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%
Brian Lehrhoff ([EMAIL PROTECTED])
EDI Consultant
eB2B Commerce
212-703-2121
%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
