Xqueeze Project Summary
Motive - The whys behind Xqueeze
The Problem: XML has grown wildly in its popularity as a medium for exchange of structured data and is now increasingly being used in large scale distributed applications and dedicated messaging protocols. However, XML is quite verbose and sub-optimal for such applications, mostly for the sake of human readability.
Compression? Compression of XML documents is widely used to lower bandwidth usage and storage capacity for large documents. This is fine as long as you don't have to deal with XML streams and you don't use it for devices with low computation power. Then again, you might be paying for something you don't need (readability).
Binarization? There is no dearth of proposals for binary representation of XML. Where these fail is in offering the flexibility afforded by XML. How much of a difference would adoption of binary formats make to the style of application development and middleware usage? Can the chosen encoding fit into your scheme of document generation?
Solution - the whats and hows
What Xqueeze is not
What Xqueeze is
You may now like to briefly read about how Xqueeze is different and how it works in principle. Please refer to the Concept page for this. Feature Details page elaborates on the entire project. Technical Specifications and other documentation can be found on the Documentation page.
Nitesh Ambastha, Tahir Hashmi