<?xml version='1.0' encoding='iso-8859-1'?><?xml-stylesheet type='text/xsl' href='https://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="https://w3future.com/weblog/2002/05/20.xml">
<head>
<title>Monday, May 20, 2002 - Sjoerd Visscher's weblog</title>
<link rel="meta" type="application/rdf+xml" title="FOAF" href="https://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:22:16 AM</p>
		<p id="alternates" class="buttons">
			<l href="https://w3future.com/weblog/2002/05/20.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:https://w3future.com/weblog/2002/05/20.xml?notransform" title="View the XHTML 2.0 source of this page."><span>Src</span> XHTML 2.0</l>
			<l href="https://w3future.com/tools/xr.pl?xr=https://w3future.com/xr/w3f.xml&amp;xml=https://w3future.com/weblog/2002/05/20.xml%3Fnotransform" rel="meta" type="application/rdf+xml" title="RDF metadata"><span>RDF</span> Metadata</l>
		</p>
		<xi:include href="https://w3future.com/w3f/buttons.xml" />
	</section><section>
  <h><a rel='prev' href='https://w3future.com/weblog/2002/05/15.xml#a100' title='Wednesday, May 15, 2002'>&lt;&#160;</a><a href="https://w3future.com/weblog/2002/05/20.xml">Monday, May 20, 2002</a><a rel='next' href='https://w3future.com/weblog/2002/05/28.txt#a104' title='Tuesday, May 28, 2002'>&#160;&gt;</a></h>
<a name="a103"></a>
<section id="a103">
<h id='andBackItIs'><a href="https://w3future.com/weblog/2002/05/20.xml#a103" class="weblogItemTitle">And back it is!</a></h>
<blockquote cite='http://scriptingnews.userland.com/backissues/2002/05/20#l49da5567a4d8aa519dde6f47413a16ee'><p>
<a href='http://backend.userland.com/ideasForEvolutionOfRss'>Ideas for RSS Evolution</a>: "Sjoerd Visscher and Rahul Dave both offered the same convincing argument for global IDs instead of local ones, so I flipped it back." [<a href='http://scriptingnews.userland.com/backissues/2002/05/20#l49da5567a4d8aa519dde6f47413a16ee'>Dave Winer</a>]</p></blockquote>
<p>Yes! Thanks Dave!</p>
</section><a name="a102"></a>
<section id="a102">
<h id='giveMeBackThatGuid'><a href="https://w3future.com/weblog/2002/05/20.xml#a102" class="weblogItemTitle">Give me back that GUID</a></h>
<blockquote cite='http://scriptingnews.userland.com/backissues/2002/05/20#lb7d637646b41482cf36ef20296e4edb5'><p>I updated my Ideas for Evolution of RSS page, posted yesterday. I realized that there was no need for global uniqueness of the id's, that uniqueness to the channel is good enough [<a href='http://scriptingnews.userland.com/backissues/2002/05/20#lb7d637646b41482cf36ef20296e4edb5'>Dave Winer</a>]</p></blockquote>
<p>I liked a GUID much more. Sometimes one item ends up in more than one channel. With a GUID you can tell it is the same item. Also, once you have a GUID, you can build from that. If a post is a reply to another post, the RSS file could point to that other post (using f.e. an &lt;inReplyTo&gt; element).</p>
</section><a name="a101"></a>
<section id="a101">
<h id='radioCanOutputXhtml'><a href="https://w3future.com/weblog/2002/05/20.xml#a101" class="weblogItemTitle">Radio can output XHTML</a></h>
<blockquote cite='http://diveintomark.org/archives/2002/05/19.html#ping_weblogscom_from_movabletype'><p>It's a safe bet that none of these are Radio weblogs, since Radio makes it virtually impossible to output XHTML. [<a href='http://diveintomark.org/archives/2002/05/19.html#ping_weblogscom_from_movabletype'>dive into mark/May 19, 2002</a>]</p></blockquote>
<p>That's not really correct. This is an XHTML Radio weblog. It's true that Radio doesn't help you to output XHTML, but it's far from impossible.</p>
</section>
</section>
<xi:include href='https://w3future.com/tools/rdf.php?about=https://w3future.com/weblog/2002/05/20.xml' /></section>
<section id="navigation"><xi:include href="https://w3future.com/w3f/sections.xml" /></section>
<section id="sidebar"><xi:include href="https://w3future.com/weblog/sidebars/weblog.opml" /></section>
</body>
</html>
