<?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: Dave&#8217;s OPML Validator Beta</title>
	<atom:link href="http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta/feed" rel="self" type="application/rss+xml" />
	<link>http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta</link>
	<description>"a foolish consistency is the hobgoblin of little minds" ~Emerson</description>
	<pubDate>Sun, 23 Nov 2008 15:32:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Firmly Wedged &#187; Another view</title>
		<link>http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta#comment-1203</link>
		<dc:creator>Firmly Wedged &#187; Another view</dc:creator>
		<pubDate>Sun, 13 Nov 2005 09:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta/#comment-1203</guid>
		<description>[...] It looks like Carl is all over the type issue already, and that I may have lead him astray with my use of within-spec but non-Dave types. [...]</description>
		<content:encoded><![CDATA[<div class='microid-http+http:sha1:c57db89502b41e786e431f0368bfa4ef6fdaec0e'>[...] It looks like Carl is all over the type issue already, and that I may have lead him astray with my use of within-spec but non-Dave types. [...]</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: cori</title>
		<link>http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta#comment-1160</link>
		<dc:creator>cori</dc:creator>
		<pubDate>Sun, 30 Oct 2005 12:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta/#comment-1160</guid>
		<description>Thanks Kosso!

I saw your comments in the thread on the opml-support group, specifically &lt;a href="http://groups.yahoo.com/group/opmlsupport/message/1009" title="Yahoo! Groups : opmlsupport Messages : Message 1009 of 1035" rel="nofollow"&gt;here&lt;/a&gt;, and agree with Bela's &lt;a href="http://groups.yahoo.com/group/opmlsupport/message/1012" title="Yahoo! Groups : opmlsupport Messages : Message 1012 of 1035" rel="nofollow"&gt;response&lt;/a&gt; but by the time I had energy and time it seemed the moment had passed for timely response.

Dave &lt;a href="http://www.opml.org/comments?u=opml&#38;p=85&#38;link=http%3A%2F%2Fwww.opml.org%2F2005%2F10%2F28%23a85" rel="nofollow"&gt;mentions&lt;/a&gt; in the comments to the validator post that he's thinking about a type for opml inclusion, and I think that's important.   As Bela says, more people are going to start generating OPML, and like RSS it will need to become automated to a certain degree before there's widespread adoption, so I think that accepting opml that doesn't end in "opml" is crucial.

That said, thanks for the hack to get mine working in your browser (which I love BTW) and thanks for the inclusion!</description>
		<content:encoded><![CDATA[<div class='microid-mailto+http:sha1:a0f4d42dfe22b27f1e918cdaa8dcbdc3d8145d25'>Thanks Kosso!</p>
<p>I saw your comments in the thread on the opml-support group, specifically <a href="http://groups.yahoo.com/group/opmlsupport/message/1009" title="Yahoo! Groups : opmlsupport Messages : Message 1009 of 1035" rel="nofollow">here</a>, and agree with Bela&#8217;s <a href="http://groups.yahoo.com/group/opmlsupport/message/1012" title="Yahoo! Groups : opmlsupport Messages : Message 1012 of 1035" rel="nofollow">response</a> but by the time I had energy and time it seemed the moment had passed for timely response.</p>
<p>Dave <a href="http://www.opml.org/comments?u=opml&amp;p=85&amp;link=http%3A%2F%2Fwww.opml.org%2F2005%2F10%2F28%23a85" rel="nofollow">mentions</a> in the comments to the validator post that he&#8217;s thinking about a type for opml inclusion, and I think that&#8217;s important.   As Bela says, more people are going to start generating OPML, and like RSS it will need to become automated to a certain degree before there&#8217;s widespread adoption, so I think that accepting opml that doesn&#8217;t end in &#8220;opml&#8221; is crucial.</p>
<p>That said, thanks for the hack to get mine working in your browser (which I love BTW) and thanks for the inclusion!</p></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: kosso</title>
		<link>http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta#comment-1154</link>
		<dc:creator>kosso</dc:creator>
		<pubDate>Sat, 29 Oct 2005 14:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://kinrowan.net/blog/wp/archives/2005/10/28/daves-opml-validator-beta/#comment-1154</guid>
		<description>Cori,
this is cool. 

my one comment is the lack of an opml extension.

But a quick tip I uaed was : in order to have your OPML feed show up in my OPML browser (which treats a 'link' type with a url ending in opml as OPML. (i used 'opml' not '.opml') I added you link like this:

http://kinrowan.net/blog/wp/wp-opml.php?opml

now it works in my OPML browser (in development) :) cool!
http://readerss.com/opml/kopml2.html


</description>
		<content:encoded><![CDATA[<div class='microid-mailto+http:sha1:c3a6573847fc2913508c0eb365ef20cbe46c3528'>Cori,<br />
this is cool. </p>
<p>my one comment is the lack of an opml extension.</p>
<p>But a quick tip I uaed was : in order to have your OPML feed show up in my OPML browser (which treats a &#8216;link&#8217; type with a url ending in opml as OPML. (i used &#8216;opml&#8217; not &#8216;.opml&#8217;) I added you link like this:</p>
<p><a href="http://kinrowan.net/blog/wp/wp-opml.php?opml" rel="nofollow">http://kinrowan.net/blog/wp/wp-opml.php?opml</a></p>
<p>now it works in my OPML browser (in development) <img src='http://kinrowan.net/blog/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> cool!<br />
<a href="http://readerss.com/opml/kopml2.html" rel="nofollow">http://readerss.com/opml/kopml2.html</a></div>
]]></content:encoded>
	</item>
</channel>
</rss>
