<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Rel for practical use: XPN</title>
	<atom:link href="http://kilianvalkhof.com/2006/web/rel-for-practical-use/feed/" rel="self" type="application/rss+xml" />
	<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/</link>
	<description></description>
	<lastBuildDate>Wed, 10 Mar 2010 12:59:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Guy Fraser</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-206</link>
		<dc:creator>Guy Fraser</dc:creator>
		<pubDate>Fri, 20 Apr 2007 00:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-206</guid>
		<description>Does XPN really need to be separate? It would make sense to define all the relationships in one place and then various services could choose which &quot;categories&quot; to enable to the end-users. I&#039;m very keen to extend XFN / XPN ideas as I have real-world clients in 50 countries who want this stuff and have loads of ideas to contribute.</description>
		<content:encoded><![CDATA[<p>Does XPN really need to be separate? It would make sense to define all the relationships in one place and then various services could choose which &#8220;categories&#8221; to enable to the end-users. I&#8217;m very keen to extend XFN / XPN ideas as I have real-world clients in 50 countries who want this stuff and have loads of ideas to contribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KilianValkhof.com &#187; Blog Archive &#187; Getting my feet wet with microformats</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-43</link>
		<dc:creator>KilianValkhof.com &#187; Blog Archive &#187; Getting my feet wet with microformats</dc:creator>
		<pubDate>Sun, 28 Jan 2007 18:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-43</guid>
		<description>[...] Friday I finally signed up for the microformats mailinglist, and it appears that my idea of an XPN has fallen quite good. Unknown to me, there were already some small discussions about a similar [...]</description>
		<content:encoded><![CDATA[<p>[...] Friday I finally signed up for the microformats mailinglist, and it appears that my idea of an XPN has fallen quite good. Unknown to me, there were already some small discussions about a similar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Redonkulosity</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-19</link>
		<dc:creator>Redonkulosity</dc:creator>
		<pubDate>Fri, 29 Dec 2006 18:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-19</guid>
		<description>&lt;strong&gt;Reapplying the &#039;rel&#039; attribute...&lt;/strong&gt;

 Note: a demo of what this post may look like with my new design. Sorry for making things so cluttered! This is a post in response to Kilian&#039;s recent post about the possible creation of an XPN. Hopefully, this......</description>
		<content:encoded><![CDATA[<p><strong>Reapplying the &#8216;rel&#8217; attribute&#8230;</strong></p>
<p> Note: a demo of what this post may look like with my new design. Sorry for making things so cluttered! This is a post in response to Kilian&#8217;s recent post about the possible creation of an XPN. Hopefully, this&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biscuitrat (Ranjani)</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-18</link>
		<dc:creator>Biscuitrat (Ranjani)</dc:creator>
		<pubDate>Sat, 23 Dec 2006 16:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-18</guid>
		<description>Well, yeah, that would be nice. Lemme know if you want any more help with it!</description>
		<content:encoded><![CDATA[<p>Well, yeah, that would be nice. Lemme know if you want any more help with it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kilian Valkhof</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-17</link>
		<dc:creator>Kilian Valkhof</dc:creator>
		<pubDate>Sat, 23 Dec 2006 10:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-17</guid>
		<description>Thank you for your comment, Johnathan. (sorry it got moderated, it had more then two links, and I&#039;m all new with this wordpress stuff) 

The only gripe I see here is that, in my opinion, the &quot;professional&quot; and the &quot;friends&quot; do/should not match. I wouldn&#039;t want to define my relationships to clients using a friends network. (Not all of them, at least)

Perhaps a general list of rel attributes would be a nice idea. I&#039;m sure going to take on your tip about e-mailing those three people.

I&#039;ve also been thinking about a couple of more additions concerning freelancers, and some way to see what type of developer made a website (&lt;code&gt;rel=&quot;developer freelancer&quot;&lt;/code&gt; or &lt;code&gt;rel=&quot;developer company&quot;&lt;/code&gt;).</description>
		<content:encoded><![CDATA[<p>Thank you for your comment, Johnathan. (sorry it got moderated, it had more then two links, and I&#8217;m all new with this wordpress stuff) </p>
<p>The only gripe I see here is that, in my opinion, the &#8220;professional&#8221; and the &#8220;friends&#8221; do/should not match. I wouldn&#8217;t want to define my relationships to clients using a friends network. (Not all of them, at least)</p>
<p>Perhaps a general list of rel attributes would be a nice idea. I&#8217;m sure going to take on your tip about e-mailing those three people.</p>
<p>I&#8217;ve also been thinking about a couple of more additions concerning freelancers, and some way to see what type of developer made a website (<code>rel="developer freelancer"</code> or <code>rel="developer company"</code>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Snook</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-16</link>
		<dc:creator>Jonathan Snook</dc:creator>
		<pubDate>Sat, 23 Dec 2006 02:52:30 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-16</guid>
		<description>My thought would be to extend XFN with these new relationship options, specifically under the Professional sub-head. I&#039;d email any or all of the authors of the XFN spec (&lt;a href=&quot;http://meyerweb.com/&quot; rel=&quot;nofollow&quot;&gt;Eric&lt;/a&gt;, &lt;a href=&quot;http://tantek.com/&quot; rel=&quot;nofollow&quot;&gt;Tantek&lt;/a&gt; or &lt;a href=&quot;http://photomatt.net/&quot; rel=&quot;nofollow&quot;&gt;Matt&lt;/a&gt;) to get their opinion or direction.</description>
		<content:encoded><![CDATA[<p>My thought would be to extend XFN with these new relationship options, specifically under the Professional sub-head. I&#8217;d email any or all of the authors of the XFN spec (<a href="http://meyerweb.com/" rel="nofollow">Eric</a>, <a href="http://tantek.com/" rel="nofollow">Tantek</a> or <a href="http://photomatt.net/" rel="nofollow">Matt</a>) to get their opinion or direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kilian Valkhof</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-15</link>
		<dc:creator>Kilian Valkhof</dc:creator>
		<pubDate>Fri, 22 Dec 2006 19:04:35 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-15</guid>
		<description>&lt;p&gt;Meta tags have been practically abandoned because of mis-use, and they do not give any semantical meaning to links (which is the whole point).&lt;/p&gt;
&lt;p&gt;You can already get away with that rel, but that was not the point. The rel attribute is open for any sort of relationship. &lt;code&gt;Rel=&quot;guy-that-sold-me-something-on-ebay&quot;&lt;/code&gt; is a valid rel, too.&lt;/p&gt;
&lt;p&gt;The point is that, with a microformat such as XFN, or like I am proposing, XPN, you standardise the way people use the rel attribute. And by standardising you can depend on it, making things like &quot;sitemadeby:&quot; search queries possible.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Meta tags have been practically abandoned because of mis-use, and they do not give any semantical meaning to links (which is the whole point).</p>
<p>You can already get away with that rel, but that was not the point. The rel attribute is open for any sort of relationship. <code>Rel="guy-that-sold-me-something-on-ebay"</code> is a valid rel, too.</p>
<p>The point is that, with a microformat such as XFN, or like I am proposing, XPN, you standardise the way people use the rel attribute. And by standardising you can depend on it, making things like &#8220;sitemadeby:&#8221; search queries possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biscuitrat (Ranjani)</title>
		<link>http://kilianvalkhof.com/2006/web/rel-for-practical-use/comment-page-1/#comment-14</link>
		<dc:creator>Biscuitrat (Ranjani)</dc:creator>
		<pubDate>Fri, 22 Dec 2006 18:56:25 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/2006/web/rel-for-practical-use/#comment-14</guid>
		<description>&lt;p&gt;We could do...&lt;/p&gt;
&lt;p&gt;Partner, client, designer/developer...design team?&lt;/p&gt;
&lt;p&gt;There&#039;s already a meta thingy for author, and there&#039;s a rel=&quot;self&quot; i think.&lt;/p&gt;
&lt;p&gt;I dunno, we&#039;re still limited if we add an XPN (unless we branch into saying &lt;i&gt;branding client&lt;/i&gt; or &lt;i&gt;website client&lt;/i&gt; - which sounds cheesy) because there are fewer professional relationships than social relationships. But what if we made the rel=&quot;&quot; attribute &lt;b&gt;open&lt;/b&gt;? I could say something like  &lt;a href=&quot;Kilian&quot; rel=&quot;MINTPAGES BUDDY&quot;&gt; and totally get away with it!
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We could do&#8230;</p>
<p>Partner, client, designer/developer&#8230;design team?</p>
<p>There&#8217;s already a meta thingy for author, and there&#8217;s a rel=&#8221;self&#8221; i think.</p>
<p>I dunno, we&#8217;re still limited if we add an XPN (unless we branch into saying <i>branding client</i> or <i>website client</i> &#8211; which sounds cheesy) because there are fewer professional relationships than social relationships. But what if we made the rel=&#8221;" attribute <b>open</b>? I could say something like  &lt;a href=&#8221;Kilian&#8221; rel=&#8221;MINTPAGES BUDDY&#8221;&gt; and totally get away with it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
