Discussion Locked

Why XML is the language of Web services

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about XML as the natural language of Web services, featured in this week's Web services e-newsletter. Do you think XML and Web services work well together? What are some of the advantages and disadvantages of using XML within Web services? How do XML's security features rate? Is XML better or worse than EDI?

5 replies

by Stephen Fraser

EDI has been around a lot longer. This providing a maturity level that XML has yet to attain. EDI has a well establish trading partner community, while XML?s is still in its infancy. EDI has agreed upon standards (maybe too many), while XML is stilltrying to get the top players to play nice.

People point out that XML due to its nature has more flexibility. But it might be argued that how flexible do you need to be to send an invoice, purchase order or a money transfer?

If you look at the internal differences between EDI and XML you find that EDI and XML are very similar. The big difference is EDI transactions are less verbose using coded headers and single character delimiters while XML uses readable (usually) tags and attributes.

Right now I don?t see any real benefit from moving from EDI to XML. Maybe with some more maturity but not yet.

by pjmidnight

For the transfer of complex data structures from back tier to a thin client xml is definitley the way to go. Transformation possiblities are endless depending on different delivery methods. We us XML in almost all of our Flash, browser, and WAP application development. No other data structure delivers as concise and effective content to a variety of sources from a single data source.

Justin Beals
Roundbox Media

by balaraman

XML has become evolutionary and is accepted as World Wide Standard. Easy for backend data transfer and operations. Highly pushed by all blues including MS and IBM.
Has become ubiquitous and all-forms.

by balaraman

XML has become evolutionary and is accepted as World Wide Standard. Easy for backend data transfer and operations. Highly pushed by all blues including MS and IBM.
Has become ubiquitous and all-forms ...

by john wilker

One of the strengths and weaknesses of XML is that anyone can define what they need; to get and to send. While there is a good chance of "too many cooks in the kitchen" syndrome, overall I think it makes good sense to use XML for web Services. XML is easy to understand and is small. XML is plain text and can be sent over existing protocols.

I have never used EDI so I can't speak to it's plusses or minusses but a recent app I developed to get XML data over the web, parse it and display it tothe user was very easy to implement. From their DTD I was able to know exactly what to expect and how.

While I'm a little concerned about the lack of standards and seemingly boondoggle nature of the decision, I think once the smoke and dust clear that XML will be very well defined and suitable for everything we think it is.

J.
Web App Developer/writer

This discussion is closed to new replies.