Altova Mailing List Archives

Re: Request: Techniques for reducing the size of XML instances

From: "Al B. Snell" <alaric@------------.--->
To: Daniel Barclay <Daniel.Barclay@------------.--->
Date: 8/2/2001 2:22:00 AM
On Wed, 1 Aug 2001, Daniel Barclay wrote:

> Isn't there a significant difference between between parsing for delimiters
> (and requiring escape mechanisms for delimiter characters in data) and
> reading, say, length codes and following fields of the given lengths (not
> that that's the only form of "binary" formats, of course)?

True textual formats never use length codes, but indeed, many binary
formats use scanning for delimiters (ASN.1 does this in some cases; a
large object with lots of little ones can be sent with a length prefix,
but if buffering it all isn't an option, it can be sent as a seqeuence of
blocks with a special null block terminating it).

There are myriads of ways of encoding things; categorising them depending
on what subset of the values 0..255 they use strikes me as odd :-)

What is perhaps really meant by textual is "layered on top of the local
character set", which is a lot less of a fundamental distinction than
might be imagined.

> Daniel


                               Alaric B. Snell
   Any sufficiently advanced technology can be emulated in software


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 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.