<?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: Relative links in RSS and Atom</title>
	<atom:link href="http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/</link>
	<description>Musings on just about everything.</description>
	<pubDate>Fri, 05 Dec 2008 10:09:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Sam Ruby</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-706</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Tue, 29 Jul 2003 10:58:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-706</guid>
		<description>Guessing may turn out to be the right thing to do for RSS feeds, but my problem is that different tools will implement different heuristics impeeding interoperability.&lt;br&gt;&lt;br&gt;In any case, my experience is that relative links are fairly rare in RSS feeds.  The RSS validator flags such usages in html with a warning.&lt;br&gt;&lt;br&gt;As for Atom feeds, I'll try to make sure that there are conformance tests for aggregators that include various combinations of relative urls, with and without xml:base.
</description>
		<content:encoded><![CDATA[<p>Guessing may turn out to be the right thing to do for RSS feeds, but my problem is that different tools will implement different heuristics impeeding interoperability.</p>
<p>In any case, my experience is that relative links are fairly rare in RSS feeds.  The RSS validator flags such usages in html with a warning.</p>
<p>As for Atom feeds, I&#8217;ll try to make sure that there are conformance tests for aggregators that include various combinations of relative urls, with and without xml:base.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-705</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Mon, 28 Jul 2003 19:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-705</guid>
		<description>I'm using the .NET DOM parser (XmlDocument).  Unfortunately, the BaseURI property for a node doesn't do what you'd hope...so the xml:base stuff is custom code.
</description>
		<content:encoded><![CDATA[<p>I&#8217;m using the .NET DOM parser (XmlDocument).  Unfortunately, the BaseURI property for a node doesn&#8217;t do what you&#8217;d hope&#8230;so the xml:base stuff is custom code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dare Obasanjo</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-704</link>
		<dc:creator>Dare Obasanjo</dc:creator>
		<pubDate>Mon, 28 Jul 2003 19:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-704</guid>
		<description>What XML parser are you using? Specifically how are you getting xml:base to work?
</description>
		<content:encoded><![CDATA[<p>What XML parser are you using? Specifically how are you getting xml:base to work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-703</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Mon, 28 Jul 2003 15:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-703</guid>
		<description>Well, I could do something like that, except 1) it's a resource drain, and 2) I still wouldn't be guaranteed of getting the correct link.  Just because there's something at the URL doesn't mean it's the right thing...&lt;br&gt;&lt;br&gt;Honestly, I think this will shake out over the next few months as relative URL's are more widely accepted, and guidelines for their use are more widely published.&lt;br&gt;&lt;br&gt;And you're right about the "feature" - haven't got around to fixing that yet!
</description>
		<content:encoded><![CDATA[<p>Well, I could do something like that, except 1) it&#8217;s a resource drain, and 2) I still wouldn&#8217;t be guaranteed of getting the correct link.  Just because there&#8217;s something at the URL doesn&#8217;t mean it&#8217;s the right thing&#8230;</p>
<p>Honestly, I think this will shake out over the next few months as relative URL&#8217;s are more widely accepted, and guidelines for their use are more widely published.</p>
<p>And you&#8217;re right about the &#8220;feature&#8221; - haven&#8217;t got around to fixing that yet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-702</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Mon, 28 Jul 2003 15:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-702</guid>
		<description>Here is a "neat feature"... if after you "post" a comment, you hit the refresh button in IE, the post will get posted again.&lt;br&gt;&lt;br&gt;Eric
</description>
		<content:encoded><![CDATA[<p>Here is a &#8220;neat feature&#8221;&#8230; if after you &#8220;post&#8221; a comment, you hit the refresh button in IE, the post will get posted again.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-701</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Mon, 28 Jul 2003 15:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-701</guid>
		<description>Greg,&lt;br&gt;  Maybe I am missing something since I have not played with RSS yet, but could you not do a quick check, and see if the relative path is "from" the URI (maybe check for the existence of a specified image), and then if that doesn't yield the desired results, default to the current method?&lt;br&gt;&lt;br&gt;Eric
</description>
		<content:encoded><![CDATA[<p>Greg,<br />
<br />  Maybe I am missing something since I have not played with RSS yet, but could you not do a quick check, and see if the relative path is &#8220;from&#8221; the URI (maybe check for the existence of a specified image), and then if that doesn&#8217;t yield the desired results, default to the current method?</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-700</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Mon, 28 Jul 2003 14:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-700</guid>
		<description>Sam, that's true...however, for the majority of feeds out there that are (arguably incorrectly) using relative links without a xml:base, basing URI's off of the post link gives us typically better results.  This is due to the way most tools generate their posts and feeds, and where relatively-linked stuff actually gets placed...&lt;br&gt;&lt;br&gt;So it's a tough call.  Technically correct per the spec, or more likely to function with actual data in the wild.  I tend toward the latter...
</description>
		<content:encoded><![CDATA[<p>Sam, that&#8217;s true&#8230;however, for the majority of feeds out there that are (arguably incorrectly) using relative links without a xml:base, basing URI&#8217;s off of the post link gives us typically better results.  This is due to the way most tools generate their posts and feeds, and where relatively-linked stuff actually gets placed&#8230;</p>
<p>So it&#8217;s a tough call.  Technically correct per the spec, or more likely to function with actual data in the wild.  I tend toward the latter&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Ruby</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-699</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Mon, 28 Jul 2003 10:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/07/27/relative-links-in-rss-and-atom/#comment-699</guid>
		<description>If xml:base is not specified, the uri of the feed itself should be used as the base (see http://www.w3.org/TR/xmlbase/#syntax).&lt;br&gt;&lt;br&gt;In case you are wondering, external entity is defined at http://www.w3.org/TR/REC-xml#sec-external-ent
</description>
		<content:encoded><![CDATA[<p>If xml:base is not specified, the uri of the feed itself should be used as the base (see <a href="http://www.w3.org/TR/xmlbase/#syntax" rel="nofollow">http://www.w3.org/TR/xmlbase/#syntax</a>).</p>
<p>In case you are wondering, external entity is defined at <a href="http://www.w3.org/TR/REC-xml#sec-external-ent" rel="nofollow">http://www.w3.org/TR/REC-xml#sec-external-ent</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
