[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Xml file sizes

  • To: <xml-dev@l...>
  • Subject: RE: Xml file sizes
  • From: "Byarlay, Wayne A." <wab@p...>
  • Date: Mon, 21 Nov 2005 16:14:49 -0500
  • Thread-index: AcXu3Rprgrp6KGdMQduY8RNo0W/FTwAAj5qQ
  • Thread-topic: Xml file sizes

computers file sizes
Well, I've certainly received a well-voiced response. It would seem that
XML's readability is its strongest point. Both by people, and computers.
If its original design was more for ease-of-use, than straight-out
efficiency, that would make sense.

Thanks for your input! Though, right now, I cannot think of any
applications for XML in any of my current projects, I will keep it in
mind.

wab

-----Original Message-----
From: Michael Champion [mailto:michael.champion@h...] 
Sent: Monday, November 21, 2005 3:50 PM
To: Byarlay, Wayne A.; xml-dev@l...
Subject: RE:  Xml file sizes




>From: "Byarlay, Wayne A." <wab@p...>
>To: <xml-dev@l...>
>Subject:  Xml file sizes
>Date: Mon, 21 Nov 2005 14:31:13 -0500
>

>If XML uses tags such as <blablabla>This is my data</blablabla>, is 
>that not a lot of extra bytes to simply declare the end of a field?

The XML spec explicitly says something like "terseness is not a design 
objective."   In this case, I think there were a number of recovering
LISP 
victims :-) who wanted a way for *humans* to figure out what level of
the hierarchy was being closed.

>
>And to take it a step further: if I have several records, but the 
>fields are always sequential, such as:
><my record>
>     <field1>Bubba Smith</field1>
>     <field2>123 Elm Street</field2>
></my record>
><my 2nd record>
>     <field1>Sally Ryder</field1>
>     <field2>123 Elm Street</field2>
></my 2nd record>
>
>...Wow, to me, that just seems like many redundant bits of data. So, 
>how is XML better than, say, a file where the field headers (and 
>footers) are smaller?

If the data is always that regular and sequential, there is little
advantage to XML.  But what if there are multiple versions of a format
floating around (some with extra information columns), and you need to
figure out which is which?  What if you need to merge them?  What if
some "cells" are the top of a tree of subordinate information?  That
gets dicey with CSV.

The basic reason why XML is practical is that it is a good enough format
for a lot of things, even if it is not particularly good at anything.
Humans can deal with it (albeit by squinting a lot), and software can
deal with it (albeit inefficiently).  It's particularly suited for the
messy middle ground where both computers and humans must work with
information that is somewhat document-like and somewhat data-like, and
there is enough structure and semantics built into the format to be
useful but not enough structure to be easily mapped into RDBMS, CSV,
ASN.1, etc.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.