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

Re: Data streams


Re:  Data streams
Hey

> (a) the longer the tags or the shorter the data elements, the
> less sense it makes to transport the data via XML and (b) the shorter the
> tags or the longer the data elements, the more sense it makes to  
> transport
> the data via XML. Anyone disagree?

Another design philosophy I've heard is something along the lines of:  
"Design to preserve as much information as possible.  When performance  
issues are encountered evaluate specific solutions to optimizing."  These  
solutions may involve shortening markup or other approaches, depending on  
what best suites the specific optimization.

I first heard this in relation to normalizing relational DBs but I think  
it applies to XML markup as well?

---->N


>
> Steve
>
> -----Original Message-----
> From: Peter Hunsberger [mailto:peter.hunsberger@g...]
> Sent: Monday, December 06, 2004 5:24 PM
> To: Stephen E. Beller
> Cc: xml-dev@l...
> Subject: Re:  Data streams
>
> On Mon, 06 Dec 2004 16:35:48 -0500, Stephen E. Beller <sbeller@n...>
> wrote:
>> In consideration of Elliotte's reply, I went back and looked at the XML
> file
>> Excel generated. Here's what I found ...
>>
>> Every one of the XML data elements had this tagging structure:
>> <Row>
>>    <Cell><Data ss:Type="Number">1</Data></Cell>
>> </Row>
>>
>> In contrast, the CSV had this structure: 1,
>>
>> That's a 50 characters to 1 difference for each data element.
>>
>> I doubt that all those XML tags are necessary if you're rendering the  
>> data
>> in something other than a spreadsheet. But if you are planning to use a
>> spreadsheet, then the 50 to 1 ratio is valid, it seems to me.
>
> Use the number 10, now the difference is 51 to 2 or a ratio of ~26 to
> 1.  Use the number 100 and the ratio is 52 to 3 or ~17 to 1.  Six
> digits? 56 to 6 or ~10 to 1. Now add multiple columns of data (as any
> realistic example would do) and the ratio falls even farther.
>
> <snip/>
>>
>> So, this benchmark test still points to a huge difference in file size  
>> and
>> in unzipping and parsing time when you compare a large data array in CSV
>> compared to XML.
>
> Maybe, maybe not, the bench mark needs to be more realistic before you
> draw any conclusions about "huge".
>



-- 


.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:.

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.