Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Why XML for Messaging?

From: Joe English <jenglish@---------.--->
To: xml-dev@-----.---.---
Date: 6/1/2005 8:20:00 PM
Bullard, Claude L (Len) wrote:

> Still, no one has answered why I need
> pointy brackets for that given comma-delimited ascii worked
> just as well and is smaller.

But comma-delimited ASCII doesn't work just as well.

First: comma-delimited.  What if the fields contain commas?
Or newlines?  They need to be quoted (and the developers
need to know that they need to be quoted), which means you've
already got an interop problem, namely, which of the half-dozen
flavors of CSV are you going to use?

Second: ASCII.  'Nuf said.

Third, and most important, is the shape of the data.
Not everything fits in a list of homogeneous records,
which is CSV's the natural shape.  Of course you can
wedge data that isn't shaped like an N by M table into
a CSV file, but then you have to devise your own encoding 
scheme.

XML's basic building blocks of elements, attributes,
and text are flexible enough to accomodate a much
broader range of data.  Only a few things fit in a
regular table, but a lot of things can fit in a tree.


--Joe English

  jenglish@f...


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent