Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XML naming conventions and good practice

From: Joe Kesselman <keshlam.cat.nospam@-------.--->
To: NULL
Date: 5/15/2009 8:18:00 PM
> My main gripe against XML is that it's so verbose. In this particular
> application, tags and antitags take up more than ten times as much space as
> the actual data being sent. CSV was *so* much more compact.

XML's verbosity is part of what's made it rapidly accepted -- it's easy 
to debug.

On the other hand, XML has never claimed to be the right answer for all 
tasks. If CSV is right for your needs, by all means use CSV. Or use 
whatever representation you like internally, with an export/import tool 
that converts between your representation an XML for interchange with 
others.

On the other other hand, XML typically compresses magnificently, and a 
compressed XML file may take no more space than the compressed CSV file 
would have.


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