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

XML and entropy, again

  • To: XML Developers List <xml-dev@l...>
  • Subject: XML and entropy, again
  • From: Michael Champion <michaelc.champion@g...>
  • Date: Tue, 21 Dec 2004 10:22:23 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=RFUV8XSuOFVaqzLld9N1UcYm7wYQQ3aUbaXhkuJ8HSdvF+uCIntl1h/XquFB4DVlDd74qE9pwMzXFV/LMspE4CNauN8hx2z9K5s/a7fRxwiQolRVUdk/CzVrGC5Fn1UTdGgAstaZdqE9JejjJGXr1noNW8Oy52sDm7UOzUfEaN8=
  • Reply-to: Michael Champion <michaelc.champion@g...>

entropy xml
We had a  classically xml-devish thread back in October about the
implications of Shannon's information theory for XML.  I must say I
didn't understand  much of that thread, but Kurt Cagle has an
intriguing entry in his weblog
http://metaphoricalweb.blogspot.com/2004/12/xml-and-entropy.html that
puts forth some ideas that seem both interesting and somewhat
practical.

"Entropy is important because it can better clarify the domain at
which it is best to work with a given document. XQuery I think
provides a good case in point here. XQuery supports XPath, and so it
has some of the advantages that XSLT has, but it's not really all that
useful for dealing with documents -- converting a DocBook document
into WordML or vice versa would be impossible in XQuery, but for many
business schemas with comparatively low entropies, XSLT is definitely
overkill."

 I for one like the idea of his interpretation of the entropy of an
XML document in terms of the number of discrete states that its
(implicit or explicit?) schema allows.  I also like the idea that
certain tools are more or less appropriate depending on the entropy of
the documents being processed -- perhaps it's something like SAX and
DOM for low entropy, XQuery for medium entropy, and XSLT for high
entropy (very document-ish) documents.   I wonder, however, about the
assertions made for the appropriateness of XQuery and XSLT, e.g.
"converting a DocBook document into WordML or vice versa would be
impossible in XQuery".  It gets back into our XSLT vs XQuery
permathread -- do the two have radically different capabilities with
respect to handling recursive structures and/or recursive alorithms,
or are they more or less different syntaxes for the same capabilities?

Thoughts, anyone?   Sorry to reopen the permathread, but I think
Kurt's approach might lead to a more focused and possibly conclusive
discussion,  Maybe wwe can all can trade ideas about this with our
relatives over the holidays :-)

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.