<?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: Folksonomies and What&#8217;s At Stake</title>
	<atom:link href="http://bokardo.com/archives/folksonomies_at_stake/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/folksonomies_at_stake/</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Wed, 28 Sep 2011 20:28:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: pickuplines</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-148462</link>
		<dc:creator>pickuplines</dc:creator>
		<pubDate>Tue, 23 Oct 2007 09:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-148462</guid>
		<description>Great job! Rock on dude!</description>
		<content:encoded><![CDATA[<p>Great job! Rock on dude!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lion</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-142112</link>
		<dc:creator>Lion</dc:creator>
		<pubDate>Mon, 14 May 2007 15:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-142112</guid>
		<description>Ecellent article, thank you.</description>
		<content:encoded><![CDATA[<p>Ecellent article, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: facebook news blog</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-120322</link>
		<dc:creator>facebook news blog</dc:creator>
		<pubDate>Thu, 19 Apr 2007 08:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-120322</guid>
		<description>Amazing tutorial! Really apreciate that â€“ thanks!</description>
		<content:encoded><![CDATA[<p>Amazing tutorial! Really apreciate that â€“ thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-316</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 17 Mar 2005 14:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-316</guid>
		<description>Matt,

I agree that we shouldn&#039;t be the ones who decide what is at stake. We wouldn&#039;t agree, and even then our opinions don&#039;t matter. Well put.

I&#039;m interested in how folksonomies translate into other contexts, too. Right now, I see them as a great way to express ideas in a relatively new domain, and I&#039;m wondering if there is a point at which we would move to a more structured way of doing things, like automation. It would seem in those domains that you mentioned (legal,financial,political) that we need structure, but as I mentioned that might only be necessary for &quot;transactions&quot;, in which we allow little interpretation as possible. 

I&#039;m still convinced, however, that in most communication systems we need a high level of interpretation, because we really don&#039;t understand things in the same &lt;em&gt;way&lt;/em&gt;.</description>
		<content:encoded><![CDATA[<p>Matt,</p>
<p>I agree that we shouldn&#8217;t be the ones who decide what is at stake. We wouldn&#8217;t agree, and even then our opinions don&#8217;t matter. Well put.</p>
<p>I&#8217;m interested in how folksonomies translate into other contexts, too. Right now, I see them as a great way to express ideas in a relatively new domain, and I&#8217;m wondering if there is a point at which we would move to a more structured way of doing things, like automation. It would seem in those domains that you mentioned (legal,financial,political) that we need structure, but as I mentioned that might only be necessary for &#8220;transactions&#8221;, in which we allow little interpretation as possible. </p>
<p>I&#8217;m still convinced, however, that in most communication systems we need a high level of interpretation, because we really don&#8217;t understand things in the same <em>way</em>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Locke</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-305</link>
		<dc:creator>Matt Locke</dc:creator>
		<pubDate>Mon, 14 Mar 2005 17:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-305</guid>
		<description>Thanks for these comments - they really add to the ongoing debate. I particularly value your idea of the &#039;learning domain&#039; within taxonomies - you&#039;re right that Folksonomies, by their fluidity and collaborative nature, keep this learning domain open for as long as possible.

For the record, i&#039;m not sceptical of the power of folksonomies at all, but want to understand how they will translate into other contexts, particularly ones where they will interact with &#039;hard&#039; taxonomies. An ongoing exchange with Clay on our blogs has usefully prompted me to try and explain this a bit more.

One thing - I would disagree with your interpretation of my use of the phrase &#039;nothing is at stake&#039;. For the nursing community, it was precisely their place within the bureaucracy of the healthcare industry that was at stake - that was what they were trying to solve with the creation of the NIC. I did not suggest that this was their aim - I was reporting from the analysis provided from the community themselves in &#039;Sorting Things Out&#039;.

I would suggest that its not up to me or you to decide. For all taxonomies - folk or otherwise - only the community engaged in the process can define what is at stake. This is what the commons-based folksonomies add that is so radical - they make it easy for people to participate and articulate their needs. My comments were aimed at asking whether these models would be productive outside of the relatively benign contexts that we have seen so far.</description>
		<content:encoded><![CDATA[<p>Thanks for these comments &#8211; they really add to the ongoing debate. I particularly value your idea of the &#8216;learning domain&#8217; within taxonomies &#8211; you&#8217;re right that Folksonomies, by their fluidity and collaborative nature, keep this learning domain open for as long as possible.</p>
<p>For the record, i&#8217;m not sceptical of the power of folksonomies at all, but want to understand how they will translate into other contexts, particularly ones where they will interact with &#8216;hard&#8217; taxonomies. An ongoing exchange with Clay on our blogs has usefully prompted me to try and explain this a bit more.</p>
<p>One thing &#8211; I would disagree with your interpretation of my use of the phrase &#8216;nothing is at stake&#8217;. For the nursing community, it was precisely their place within the bureaucracy of the healthcare industry that was at stake &#8211; that was what they were trying to solve with the creation of the NIC. I did not suggest that this was their aim &#8211; I was reporting from the analysis provided from the community themselves in &#8216;Sorting Things Out&#8217;.</p>
<p>I would suggest that its not up to me or you to decide. For all taxonomies &#8211; folk or otherwise &#8211; only the community engaged in the process can define what is at stake. This is what the commons-based folksonomies add that is so radical &#8211; they make it easy for people to participate and articulate their needs. My comments were aimed at asking whether these models would be productive outside of the relatively benign contexts that we have seen so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bill h-d</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-298</link>
		<dc:creator>bill h-d</dc:creator>
		<pubDate>Mon, 07 Mar 2005 18:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-298</guid>
		<description>The &quot;folk&quot; in folksonomy doesn&#039;t connote &quot;personal&quot; so much as it does &quot;vernacular.&quot; That is, of the people rather than imposed upon us/them.

Vernaculonomy is cumbersome though.

So is Vernacularchy. So I guess we stay with folksonomy for the time being.</description>
		<content:encoded><![CDATA[<p>The &#8220;folk&#8221; in folksonomy doesn&#8217;t connote &#8220;personal&#8221; so much as it does &#8220;vernacular.&#8221; That is, of the people rather than imposed upon us/them.</p>
<p>Vernaculonomy is cumbersome though.</p>
<p>So is Vernacularchy. So I guess we stay with folksonomy for the time being.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud Gibson</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-297</link>
		<dc:creator>Bud Gibson</dc:creator>
		<pubDate>Fri, 04 Mar 2005 23:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-297</guid>
		<description>In response to Harrington, just because something is personal does not mean it is not shared.  We tend to use similar words to describe things when those things are well understood by a particular group or culture.  

When we are embarking on new concepts or going between cultural subgroups, there&#039;s likely to be disagreement.  There are all sorts of ways to handle that.

I&#039;m not sure it is so worth to debate the merits of going forward.  Folksonomy folks should just go forward and try to work out the problems that will inevitably arise.  Then, we&#039;ll see what we get of value.

Personally, I am watching with interest what Ben Hammersley is doing at The Observer Blog.</description>
		<content:encoded><![CDATA[<p>In response to Harrington, just because something is personal does not mean it is not shared.  We tend to use similar words to describe things when those things are well understood by a particular group or culture.  </p>
<p>When we are embarking on new concepts or going between cultural subgroups, there&#8217;s likely to be disagreement.  There are all sorts of ways to handle that.</p>
<p>I&#8217;m not sure it is so worth to debate the merits of going forward.  Folksonomy folks should just go forward and try to work out the problems that will inevitably arise.  Then, we&#8217;ll see what we get of value.</p>
<p>Personally, I am watching with interest what Ben Hammersley is doing at The Observer Blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CM Harrington</title>
		<link>http://bokardo.com/archives/folksonomies_at_stake/#comment-296</link>
		<dc:creator>CM Harrington</dc:creator>
		<pubDate>Fri, 04 Mar 2005 20:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/49/index.php#comment-296</guid>
		<description>The problem with &quot;folksonomy&quot; is that it only exists on the personal level. What *I* think is an adequate way to describe something, is *not* what someone else will.

The portion about the nurses, I would even say supports the idea that it ceased to be a &quot;folksonomy&quot; as soon as it was adopted by more than one person. It then became a taxonomy by committee. Everyone agreed (controlled) the language after that point. The only difference being the terms used were possibly less scientific or exact than a formal taxonomy.</description>
		<content:encoded><![CDATA[<p>The problem with &#8220;folksonomy&#8221; is that it only exists on the personal level. What *I* think is an adequate way to describe something, is *not* what someone else will.</p>
<p>The portion about the nurses, I would even say supports the idea that it ceased to be a &#8220;folksonomy&#8221; as soon as it was adopted by more than one person. It then became a taxonomy by committee. Everyone agreed (controlled) the language after that point. The only difference being the terms used were possibly less scientific or exact than a formal taxonomy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

