<?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: XFN 1.1</title>
	<atom:link href="http://dougal.gunters.org/blog/2004/08/17/xfn-11/feed" rel="self" type="application/rss+xml" />
	<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11</link>
	<description>Random musings of a Southern geek</description>
	<pubDate>Sat, 10 Jan 2009 00:33:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1-alpha-10188</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dougal Campbell</title>
		<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11/comment-page-1#comment-896</link>
		<dc:creator>Dougal Campbell</dc:creator>
		<pubDate>Wed, 18 Aug 2004 12:18:35 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-896</guid>
		<description>I only meant that there is no enforcement in *my* code that I added to WordPress. I added form fields to accomodate the new values, but I didn't have time to work on front-end or back-end error handling for the 'me' relations.

Anyhow, I think the new additions are good ones. In particular, I'll probably be using 'contact' a lot. I have a lot of 'acquaintance' relations that will probably drop down to 'contact'.</description>
		<content:encoded><![CDATA[<p>I only meant that there is no enforcement in *my* code that I added to WordPress. I added form fields to accomodate the new values, but I didn&#8217;t have time to work on front-end or back-end error handling for the &#8216;me&#8217; relations.</p>
<p>Anyhow, I think the new additions are good ones. In particular, I&#8217;ll probably be using &#8216;contact&#8217; a lot. I have a lot of &#8216;acquaintance&#8217; relations that will probably drop down to &#8216;contact&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tantek</title>
		<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11/comment-page-1#comment-894</link>
		<dc:creator>Tantek</dc:creator>
		<pubDate>Wed, 18 Aug 2004 05:19:14 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-894</guid>
		<description>Dougal, thanks for your kind note!

BTW, you said above: 
&lt;blockquote&gt;
... the “me” value is supposed to be exclusive of all other values. But there is nothing currently in the code to enforce that.
&lt;/blockquote&gt;

Not true!  Check out the updated &lt;a href="http://gmpg.org/xfn/creator"&gt;XFN 1.1 Creator&lt;/a&gt; which &lt;em&gt;does&lt;/em&gt; enforce the mutual exclusivity of the "me" value.</description>
		<content:encoded><![CDATA[<p>Dougal, thanks for your kind note!</p>
<p>BTW, you said above: </p>
<blockquote><p>
&#8230; the “me” value is supposed to be exclusive of all other values. But there is nothing currently in the code to enforce that.
</p></blockquote>
<p>Not true!  Check out the updated <a href="http://gmpg.org/xfn/creator">XFN 1.1 Creator</a> which <em>does</em> enforce the mutual exclusivity of the &#8220;me&#8221; value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dougal Campbell</title>
		<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11/comment-page-1#comment-893</link>
		<dc:creator>Dougal Campbell</dc:creator>
		<pubDate>Wed, 18 Aug 2004 01:38:45 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-893</guid>
		<description>BTW, technically, the "me" value is supposed to be exclusive of all other values. But there is nothing currently in the code to enforce that. I don't have time to dive into the javascript and do the error checking myself right now.

See &lt;a href="http://peterjanes.ca/blog/archives/2004/08/16/fun-with-xfn"&gt;Petroglyphs: Fun with XFN&lt;/a&gt; for amusing examples of what kinds of non-standard relations one could imply by toying with or ignoring the XFN specs.</description>
		<content:encoded><![CDATA[<p>BTW, technically, the &#8220;me&#8221; value is supposed to be exclusive of all other values. But there is nothing currently in the code to enforce that. I don&#8217;t have time to dive into the javascript and do the error checking myself right now.</p>
<p>See <a href="http://peterjanes.ca/blog/archives/2004/08/16/fun-with-xfn">Petroglyphs: Fun with XFN</a> for amusing examples of what kinds of non-standard relations one could imply by toying with or ignoring the XFN specs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geof</title>
		<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11/comment-page-1#comment-891</link>
		<dc:creator>Geof</dc:creator>
		<pubDate>Tue, 17 Aug 2004 15:10:16 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-891</guid>
		<description>Thanks for adding it in to WP.  I like WP's little form in the Links Manager for adding XFN values, but what frustrates the crap out of me is that you can't add values that aren't in the form!  I know that rel="blah" is largely being used by XFN, but there are other uses for it, and it frustrated me that I couldn't hand-enter "me" rel values.</description>
		<content:encoded><![CDATA[<p>Thanks for adding it in to WP.  I like WP&#8217;s little form in the Links Manager for adding XFN values, but what frustrates the crap out of me is that you can&#8217;t add values that aren&#8217;t in the form!  I know that rel=&#8221;blah&#8221; is largely being used by XFN, but there are other uses for it, and it frustrated me that I couldn&#8217;t hand-enter &#8220;me&#8221; rel values.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HREF - Anneâ€™s Weblog about Markup &#38;amp; Style</title>
		<link>http://dougal.gunters.org/blog/2004/08/17/xfn-11/comment-page-1#comment-25937</link>
		<dc:creator>HREF - Anneâ€™s Weblog about Markup &#38;amp; Style</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-25937</guid>
		<description>&lt;!--%kramer-pre%--&gt;... is a practical training course in web design for everyone interested in creating effective web pages."Â· First XFN 1.1 toolsAugust 21 &#124; WordPress 1.3 will also be conformant (mentioned in XFN 1.1)related: XFN 1.1 &lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-pre%-->&#8230; is a practical training course in web design for everyone interested in creating effective web pages.&#8221;Â· First XFN 1.1 toolsAugust 21 | WordPress 1.3 will also be conformant (mentioned in XFN 1.1)related: XFN 1.1 <!--%kramer-post%--></p>
]]></content:encoded>
	</item>
</channel>
</rss>
