<?xml version='1.0' encoding='iso-8859-1'?><?xml-stylesheet type='text/xsl' href='http://w3future.com/w3f/w3f.xsl' ?>
<html xmlns="http://www.w3.org/2002/06/xhtml2" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xf="http://www.w3.org/2002/xforms/cr" xml:lang="en" xml:base="http://w3future.com/weblog/2003/06/29.xml">
<head>
<title>Sunday, June 29, 2003 - Sjoerd Visscher's weblog</title>
<link rel="meta" type="application/rdf+xml" title="FOAF" href="http://w3future.com/people/sjoerd_visscher/foaf.rdf" />
</head>
<body>
<section id="content">
	<h>Sjoerd Visscher's weblog</h>
	<p>Pondering those web technologies that may change the future of the world wide web.</p>
	<section id="note">
		<h>Last Update</h>
		<p>10/16/2005; 1:28:05 AM</p>
		<p id="alternates" class="buttons">
			<l href="http://w3future.com/weblog/2003/06/29.xml?notransform" rel="alternate" type="application/xml" title="See this web page with XHTML 2.0 technology."><span>Try</span> XHTML 2.0</l>
			<l href="view-source:http://w3future.com/weblog/2003/06/29.xml?notransform" title="View the XHTML 2.0 source of this page."><span>Src</span> XHTML 2.0</l>
			<l href="http://w3future.com/tools/xr.pl?xr=http://w3future.com/xr/w3f.xml&amp;xml=http://w3future.com/weblog/2003/06/29.xml%3Fnotransform" rel="meta" type="application/rdf+xml" title="RDF metadata"><span>RDF</span> Metadata</l>
		</p>
		<xi:include href="http://w3future.com/w3f/buttons.xml" />
	</section><section>
  <h><a rel='prev' href='http://w3future.com/weblog/2003/06/25.xml#a210' title='Wednesday, June 25, 2003'>&lt;&#160;</a><a href="http://w3future.com/weblog/2003/06/29.xml">Sunday, June 29, 2003</a><a rel='next' href='http://w3future.com/weblog/2003/06/30.txt#a212' title='Monday, June 30, 2003'>&#160;&gt;</a></h>
<a name="a240"></a>
<section id="a240">
<h id='theDifferenceBetweenRssAndEcho'><a href="http://w3future.com/weblog/2003/06/29.xml#a240" class="weblogItemTitle">The difference between RSS and Echo</a></h>
<p>In the recent heated debates about Echo (<a href="http://intertwingly.net/wiki/pie/NameItEchoConflict">I'll call it that for now</a>) the prevailing comment is that Echo is a replacement of RSS because of political issues. While this is not entirely untrue, there are actually big differences between Echo and RSS. I'm going to address the main difference for each version of RSS.</p>
<ol><li><em>Why Echo is different from RSS 1.0</em> Echo is XML. RSS 1.0 is RDF.</li>
<li><em>Why Echo is different from RSS 0.91</em> RSS 0.91 is designed as a site summary. There is an item for each page on your site with a link and a title and maybe a description. This is the way the BBC and Microsoft use RSS. Echo is for distributing/transmitting content. Each entry contains things like author, an id, a permalink (if it is already published online), the relevant dates, and the actual content. This can be a weblog entry, or a comment or what else.</li>
<li><em>Why Echo is different from RSS 2.0</em> RSS 2.0 is XML, but Echo is really about XML technology. The only thing that is asked more than once on the RSS2-Support list, I think, is: Where can I find the XML Schema or DTD for RSS 2.0? There is no schema because it cannot be done. That's the backwards compatability burdon RSS is carrying. Echo will probably have a W3C XML Schema and a RelaxNG schema. The dates will be in <code>xs:dateTime</code> format, so languages with schema support (f.e. .net languages, XQuery, XSLT 2.0) can perform date/time calculations directly. Also the preferred format of the content seems going to be XML, where RSS 2.0 uses escaped HTML.</li></ol>
<p>These differences are IMHO big enough to warrant a new format, and Echo deserves a fair chance.</p>
</section>
</section>
<xi:include href='http://w3future.com/tools/rdf.php?about=http://w3future.com/weblog/2003/06/29.xml' /></section>
<section id="navigation"><xi:include href="http://w3future.com/w3f/sections.xml" /></section>
<section id="sidebar"><xi:include href="http://w3future.com/weblog/sidebars/weblog.opml" /></section>
</body>
</html>

