OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: standard compressed XML format?

[ Lists Home | Date Index | Thread Index ]
  • From: Greg Messner <gmessner@vsi.com>
  • To: XML-Dev Mailing list <xml-dev@xml.org>
  • Date: Thu, 16 Mar 2000 13:43:38 -0800

You might want to take a look at:
http://www.research.att.com/sw/tools/xmill/

I have also looked at least one other approach but cannot seem to locate the
URLs for them. I'll post them if I can locate them.


-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]
Sent: Thursday, March 16, 2000 9:34 AM
To: XML-Dev Mailing list
Subject: standard compressed XML format?


Is anyone doing any work on a standard compression format for XML documents?

I'm starting to get concerned about the volume of complaints I'm getting
from readers and folks in Web development forums who are starting to argue
that XML's verbosity is a problem, especially for things like transmitting
vector graphics information.  There are a lot of wasted bits in XML
documents - and of course in HTML and other text documents as well.

I'm not happy about the prospect of sending documents to browsers as .zip
or some other compressed format and making users go through multiple steps
to decompress and view the content.  I'd like to think that we could come
up with a compression/decompression algorithm for markup (maybe just XML,
maybe all text) that we can use transparently.  Ideally, it would be an
algorithm explicitly placed in the public domain, avoiding licensing and
legal battles.

Some folks have argued that this belongs in transfer protocols, while
others have argued that it should be a 3rd party function, like .zip and
.sit are today.  I'm not convinced by the first because so many competing
formats (gif, jpeg, flash, etc.) already include compression, and I'm not
convinced by the second because I don't think users are willing to
micromanage such a process.

It also has an impact on some of the discussions on the IETF-XML-MIME
discussion (see http://www.imc.org/ietf-xml-mime/ for archives and
information) because we're already discussing how best to mark information
as XML for possible generic processing.  If a compression standard emerged,
it might well have an impact on MIME types - and I'd like to see that
discussion start before we settle the MIME types for XML debate.

Any thoughts?  I like the fact that XML is verbose when I'm editing and
processing, but it's not so good in transmission.  I'd like to think that
there's a good _general_ solution that will let us have the best of both
worlds.

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
Building XML Applications
Inside XML DTDs: Scientific and Technical
Cookies / Sharing Bandwidth
http://www.simonstl.com

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS