<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Our own 100 years War</title>
	<atom:link href="http://blog.broadbandmechanics.com/2004/10/our_own_100_yea/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.broadbandmechanics.com/2004/10/our_own_100_yea</link>
	<description>Digital Lifestyle Aggregation - helping to establish open source infrastructure</description>
	<pubDate>Fri, 05 Dec 2008 12:54:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Danny</title>
		<link>http://blog.broadbandmechanics.com/2004/10/our_own_100_yea#comment-1905</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://marc_blogs_it.myelin.co.nz/?p=1712#comment-1905</guid>
		<description>Heh, I was going to comment saying pretty much the same as Joshua. 

Regarding the holy war, there's still the occasional skirmish, but from what I've seen on some of the lists in recent months (particularly Atom's) there's a lot more effort going into finding positions in which everyone's reasonably comfortable. 

In general more people are recognising the benefits of the RDF model (and the app list is growing), and it's impossible to ignore the widespread deployment of domain-specific XML like RSS 2.0. So I'm optimistic that less energy is going into futile arguments and more into making the Web an interesting place.

On the point of argument in the mail, I do reckon the layering thing is still an open question - where should the lines be drawn between transport, metadata and content. All three are really just data, after all. I'm just uneasy at the idea of turning something full of structure and external linkage into an opaque blob.  

Oh yeah, an don't forget Joshua's a nice guy!
 
</description>
		<content:encoded><![CDATA[<p>Heh, I was going to comment saying pretty much the same as Joshua. </p>
<p>Regarding the holy war, there&#8217;s still the occasional skirmish, but from what I&#8217;ve seen on some of the lists in recent months (particularly Atom&#8217;s) there&#8217;s a lot more effort going into finding positions in which everyone&#8217;s reasonably comfortable. </p>
<p>In general more people are recognising the benefits of the RDF model (and the app list is growing), and it&#8217;s impossible to ignore the widespread deployment of domain-specific XML like RSS 2.0. So I&#8217;m optimistic that less energy is going into futile arguments and more into making the Web an interesting place.</p>
<p>On the point of argument in the mail, I do reckon the layering thing is still an open question - where should the lines be drawn between transport, metadata and content. All three are really just data, after all. I&#8217;m just uneasy at the idea of turning something full of structure and external linkage into an opaque blob.  </p>
<p>Oh yeah, an don&#8217;t forget Joshua&#8217;s a nice guy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Allen</title>
		<link>http://blog.broadbandmechanics.com/2004/10/our_own_100_yea#comment-1904</link>
		<dc:creator>Joshua Allen</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://marc_blogs_it.myelin.co.nz/?p=1712#comment-1904</guid>
		<description>Hi Marc,

I appreciate your eagerness to identify and dissipate holy wars or "pointless" conversations (I feel the same way), but I believe you might have been too obstreperous to draw conclusions about the e-mail thread you posted above.

It's a bit funny to see myself being characterized as anti-RDF.  I have been criticized for being too *pro* RDF, for being too idealistic in my evangelism of the triples data model, and I am the first to argue that XML and RDF are naturally at peace (and for example, I wrote the FOAF importer for WinFS to show that WinFS is not all that incompatible with RDF).  And none of this is really very secret about me.

Now, I agree that there have been holy wars between XML and RDF, but think we are mostly past those as a community.  The two can and do complement one another.

The real difference in perspective (if there is one) between Danny and me highlighted in the quoted e-mail thread regards the appropriate amount of "layering" in a protocol like Atom/RSS which is intended to be a transport.  For example, FOAF/RDF files are transported very effectively over HTTP, but HTTP does not need to have any knowledge of RDF.  I don't think it would be effective at all to try baking RDF concepts into HTTP.  Same with RSS, SMTP, NNTP, or any other transport mechanism.</description>
		<content:encoded><![CDATA[<p>Hi Marc,</p>
<p>I appreciate your eagerness to identify and dissipate holy wars or &#8220;pointless&#8221; conversations (I feel the same way), but I believe you might have been too obstreperous to draw conclusions about the e-mail thread you posted above.</p>
<p>It&#8217;s a bit funny to see myself being characterized as anti-RDF.  I have been criticized for being too *pro* RDF, for being too idealistic in my evangelism of the triples data model, and I am the first to argue that XML and RDF are naturally at peace (and for example, I wrote the FOAF importer for WinFS to show that WinFS is not all that incompatible with RDF).  And none of this is really very secret about me.</p>
<p>Now, I agree that there have been holy wars between XML and RDF, but think we are mostly past those as a community.  The two can and do complement one another.</p>
<p>The real difference in perspective (if there is one) between Danny and me highlighted in the quoted e-mail thread regards the appropriate amount of &#8220;layering&#8221; in a protocol like Atom/RSS which is intended to be a transport.  For example, FOAF/RDF files are transported very effectively over HTTP, but HTTP does not need to have any knowledge of RDF.  I don&#8217;t think it would be effective at all to try baking RDF concepts into HTTP.  Same with RSS, SMTP, NNTP, or any other transport mechanism.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
