While I won't comment on the many other issues presented on XML (I've posted
a few times before at length on my views and don't see the point in doing it
again), I will comment on the following...
<<SNIP>>
> > I would argue these points. Never before have vendors pledged and
> > started to
> > deliver on having there applications produce and accept XML. I have
> > seen press release and
> > demos from folks like SAP, Peoplesoft, JD Edwards, Great Plains,
> > Microsoft and Oracle that all are
> > working on having XML as the input or output.
> >
<<SNIP>>
I've seen (and written only a few) implementations of using XML as an input
for my programming components and apps. XML can be very powerful and
flexible as a communications data structure given the right circumstances.
Microsofts' upcoming .NET strategy makes extensive and almost exclusive use
of XML as it's communications data structure at every level. This extends,
as well, to their Visual Studio .NET application development environment.
The many many developers writing to the Microsoft platform are going to be
sucked right along into the "XML everything & everywhere" toolset... not to
say it's good or bad ... just that it's the direction I see on the
development front. I'm sure the other language/app.dev. vendors will follow
suit shortly. So, XML will be built-in at the start.
Therefore, I agree with the quoted statement above from Scott. It's
cooommminnngggg. <g>
- AHilton
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
