Re: [xml-dev] Transmission of XML Data

[basudeb gupta <basudeb0001@yahoo.com>]

Thanks for your comments. I did go to this URL 
http://www.w3.org/TR/xbc-use-cases/
and found this to be a very good analysis of the real
world. 

There is surely a case of XML compression. And to make
it general, it should be a gzip/deflate kind of
standard compression. 

My point was that we could try out the concepts of 
SIGCOMP, whereby a small UDVM is implemented at both
ends and the decryption algorithm itself is sent along
with the encrypted data, thus making the exchange
totally immune to non-standard compressions.

We have seen with DEFLATE algorithm, the decryption
code is very small ( they are made for Mobile devices
normally) and very fast. 

I was exploring if this could be implemented as a
standard in XML data exchange too. 

Basudeb
 

--- Michael Champion <michaelc.champion@gmail.com>
wrote:

> On 10/17/05, basudeb gupta <basudeb0001@yahoo.com>
> wrote:
> 
> >
> > How is the XML Data actually exchanged? Is it in
> its
> > full glorious expanded form? If so, is it not a
> great
> > loss of bandwidth?
> >
> > If not, I assume there are compression mechanisms
> > available in the send and receive functions used
> by
> > such programs which exchange XML data? Can someone
> > please guide me on the current state of the art?
> 
> This is not an ignorant question, it's an xml-dev
> permathread.  There
> is a widespread complaint that XML is "bloated and
> slow" and that this
> is a problem that needs to be remedied.  There is an
> equally
> widespread belief (enshrined in the XML spec) that
> terseness is not a
> design criterion, that human readability and
> exploitable redundancy
> trumps machine efficiency, and that the "binary XML"
> cure is worse
> than the inefficiency disease.
> 
> The "efficient interchange" camp seems to be winning
> this year, at
> least at W3C.  There will probably be a working
> group formed soon to
> develop an Efficient XML Interchange Recommendation
> that is
> (supposedly) going to achieve a wide range of use
> cases.  There is a
> lot of debate about this within member-only W3C
> mailing lists (and I'm
> on record as opposing it). Still, the proponents and
> the W3C have gone
> to some lengths to ensure that the evidence of
> whatever improvements
> in efficiency are achieved and whatever threats to
> interoperability
> are uncovered are made public before the working
> group's spec achieves
> unstoppable momentum.
> 
> Shameless plug: We've organized a panel discussion
> at the XML 2005
> Conference (http://2005.xmlconference.org/ ) on
> Efficient XML in which
> people on all sides of this question have been
> invited.   Come to the
> XML 2005 conference, listen to what these people
> have to say, and
> you'll have a chance to speak your piece during the
> Q&A period and
> lobby people for your point of view at the dinner
> afterwards.
> 
>
-----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at
> http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the
> subscription
> manager:
> <http://www.oasis-open.org/mlmanage/index.php>
> 
>