<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Benefits of Using XML Technologies for Web Applications</title>
	<link>http://www.orbeon.com/blog/2005/03/02/benefits-of-using-xml-technologies-for-web-applications/</link>
	<description>XForms Everywhere</description>
	<pubDate>Thu, 21 Aug 2008 14:19:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.3</generator>

	<item>
		<title>by: Alessandro Vernet</title>
		<link>http://www.orbeon.com/blog/2005/03/02/benefits-of-using-xml-technologies-for-web-applications/#comment-165</link>
		<pubDate>Tue, 05 Apr 2005 18:04:02 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/02/benefits-of-using-xml-technologies-for-web-applications/#comment-165</guid>
					<description>Jay,

I agree with your comment. Somehow I make a distinction between the reasons to use XML &lt;i&gt;in general&lt;/i&gt; (and the fact that it is human readable, easier to migrate and restructure than other formats is a definitive plus), and the reasons to use XML &lt;i&gt;for web applications in particular&lt;/i&gt;. You mention a good reason why people are using XML to exchange and sometime store information. To deal with this data, stored and exchanged in XML format, web applications want to use XML tools (implementations of standards like XSLT, W3C/RNG schema, XForms, ...), and an XML platform that integrates and provides an easy access to those tools (like &lt;a href=&quot;http://www.orbeon.com/software/&quot;&gt;PresentationServer&lt;/a&gt;). Am I making an artificial distinction here, or does this make sense?

Alex</description>
		<content:encoded><![CDATA[	<p>Jay,</p>
	<p>I agree with your comment. Somehow I make a distinction between the reasons to use XML <i>in general</i> (and the fact that it is human readable, easier to migrate and restructure than other formats is a definitive plus), and the reasons to use XML <i>for web applications in particular</i>. You mention a good reason why people are using XML to exchange and sometime store information. To deal with this data, stored and exchanged in XML format, web applications want to use XML tools (implementations of standards like XSLT, W3C/RNG schema, XForms, &#8230;), and an XML platform that integrates and provides an easy access to those tools (like <a href="http://www.orbeon.com/software/">PresentationServer</a>). Am I making an artificial distinction here, or does this make sense?</p>
	<p>Alex
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jay</title>
		<link>http://www.orbeon.com/blog/2005/03/02/benefits-of-using-xml-technologies-for-web-applications/#comment-164</link>
		<pubDate>Tue, 05 Apr 2005 11:24:52 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/02/benefits-of-using-xml-technologies-for-web-applications/#comment-164</guid>
					<description>You forget one the main advantages of using XML within a large corporation: future-proof-ness ! Being &quot;human-readable&quot;, XML data can be migrated (if necessary) to other new formats or re-structured, using XSLT, for example. But the initial problem, migrating old HTML-formated documents, embedded in layers of gooey DHTML, into meta-information rich XML remains. This step should never be underestimated and could cost far more than simply setting up the new system in the first place ...</description>
		<content:encoded><![CDATA[	<p>You forget one the main advantages of using XML within a large corporation: future-proof-ness ! Being &#8220;human-readable&#8221;, XML data can be migrated (if necessary) to other new formats or re-structured, using XSLT, for example. But the initial problem, migrating old HTML-formated documents, embedded in layers of gooey DHTML, into meta-information rich XML remains. This step should never be underestimated and could cost far more than simply setting up the new system in the first place &#8230;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
