<?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: The Danger of Losing Context with XFN</title>
	<atom:link href="http://www.eakes.org/36/the-danger-of-losing-context-with-xfn/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eakes.org/36/the-danger-of-losing-context-with-xfn/</link>
	<description>Software Engineering, Social Technology, Product Design</description>
	<lastBuildDate>Fri, 16 Apr 2010 16:07:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Max Krueger</title>
		<link>http://www.eakes.org/36/the-danger-of-losing-context-with-xfn/comment-page-1/#comment-5</link>
		<dc:creator>Max Krueger</dc:creator>
		<pubDate>Fri, 22 Apr 2005 09:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.eakes.org/?p=36#comment-5</guid>
		<description>What if rather than putting the XFN entries directly into the html page, a seprate html file is kept as your blogroll file and either linked to using the link rel=, or using a meta-tag in the header? Only problem I see is compatability with existing XFN apps. I think a meta-tag is the way to go.
</description>
		<content:encoded><![CDATA[<p>What if rather than putting the XFN entries directly into the html page, a seprate html file is kept as your blogroll file and either linked to using the link rel=, or using a meta-tag in the header? Only problem I see is compatability with existing XFN apps. I think a meta-tag is the way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Sloan</title>
		<link>http://www.eakes.org/36/the-danger-of-losing-context-with-xfn/comment-page-1/#comment-4</link>
		<dc:creator>Steve Sloan</dc:creator>
		<pubDate>Fri, 07 Jan 2005 02:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.eakes.org/?p=36#comment-4</guid>
		<description>I think you are right, it is very possible that it might happen and did, I did it!
XFN is still a new concept to a lot of folks and is not even supported by a lot of HTML creation programs. It wasn&#039;t till I saw a post about the danger of doing what you say that I started doing research on XFN, went back and started using XFN on my own posts. Oh yes, I fixed my prior posts!
Anyway I started using Nvu for creating blog posts as it supports XFN.
~Steve
</description>
		<content:encoded><![CDATA[<p>I think you are right, it is very possible that it might happen and did, I did it!<br />
XFN is still a new concept to a lot of folks and is not even supported by a lot of HTML creation programs. It wasn&#8217;t till I saw a post about the danger of doing what you say that I started doing research on XFN, went back and started using XFN on my own posts. Oh yes, I fixed my prior posts!<br />
Anyway I started using Nvu for creating blog posts as it supports XFN.<br />
~Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: codestream</title>
		<link>http://www.eakes.org/36/the-danger-of-losing-context-with-xfn/comment-page-1/#comment-6</link>
		<dc:creator>codestream</dc:creator>
		<pubDate>Sat, 01 Jan 2005 04:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.eakes.org/?p=36#comment-6</guid>
		<description>&lt;strong&gt;The Semantic Context of XFN&lt;/strong&gt;

Michael Eakes raises the issue of XFN context. The problem he identifies is that someone might copy a set of XFN-enabled links from another blog and put them into their own, without realising that the links contained semantic information. It&#039;s...
</description>
		<content:encoded><![CDATA[<p><strong>The Semantic Context of XFN</strong></p>
<p>Michael Eakes raises the issue of XFN context. The problem he identifies is that someone might copy a set of XFN-enabled links from another blog and put them into their own, without realising that the links contained semantic information. It&#8217;s&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
