[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Use of XML ?
- From: Caroline Clewlow <email@example.com>
- To: firstname.lastname@example.org
- Date: Thu, 02 Aug 2001 11:54:33 +0100
I just wanted to thank everyone for their replies to my query. It appears to have sparked off some interesting
discussion - but most of you comfirmed my original thoughts
Would it be fair to summarise that........
XML is ideal as a method of exchanging data between systems where the implementation on one of more sides is unknown,
but between co-operating systems there are other possibly more efficient methods where data can be structured
programmatically. ..... ?
Of course one of the other advantages being XML's machine and human readbility feature.
Thanks again all
Ajay K sanghi wrote:
> The effort has to do with "programming vs mapping" even if "all" sides have
> JVM and XML Parser.
> Also, if you see my response, nowhere I use the word "XML". I use the term
> "file-based" approach. The file may be in XML, EDI or proprietary format.
> Note: we are an XML/EDI vendor, so "may" be i am biased.
> -----Original Message-----
> From: Al Snell [mailto:email@example.com]
> Sent: Wednesday, August 01, 2001 10:17 PM
> To: Ajay K sanghi
> Cc: firstname.lastname@example.org
> Subject: RE: Use of XML ?
> On Wed, 1 Aug 2001, Ajay K sanghi wrote:
> > Also, consider efforts required in synchronising a change in the class.
> 1) s/class/DTD/
> 2) Requiring both sides to have an XML parser isn't *that* much less
> restrictive then requiring both sides to have a JVM either :-)
> > Ajay
> Alaric B. Snell
> http://www.alaric-snell.com/ http://RFC.net/ http://www.warhead.org.uk/
> Any sufficiently advanced technology can be emulated in software
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: email@example.com