<?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: Not the LibraryThing I signed up for</title>
	<atom:link href="http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/feed/" rel="self" type="application/rss+xml" />
	<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/</link>
	<description>Figure it out ... with me!</description>
	<lastBuildDate>Thu, 26 Aug 2010 17:42:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: configures</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-71392</link>
		<dc:creator>configures</dc:creator>
		<pubDate>Sat, 30 Jan 2010 15:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-71392</guid>
		<description>&quot;Genders and Drop-down Menus&quot; is a more recent take on the sort of issue that sparked this post (which LibraryThing fixed, I&#039;m happy to say).  In it, &lt;a href=&quot;http://www.sarahdopp.com/blog/?p=514&quot; rel=&quot;nofollow&quot;&gt;Sarah Dopp explains the influence issue of binary gender categorization&lt;/a&gt;.  As I&#039;ve said in letters to the ACM before they fixed their member survey (thanks!), my college Honors Department, and others, a poll (or drop-down menu) which only allows &quot;male&quot; and &quot;female&quot; defines people who don&#039;t fit into binary gender categories out of existence, and reinforces rigid binary gender thinking which harms real human beings.  An &quot;Other&quot;, &quot;Complicated&quot;, or &quot;Prefer not to say&quot; option (or some mix of these, or all on one line) would encourage participation from people who just don&#039;t fit so neatly, and would help remind people that it&#039;s a big world with lots of kind of people in it.</description>
		<content:encoded><![CDATA[<p>&#8220;Genders and Drop-down Menus&#8221; is a more recent take on the sort of issue that sparked this post (which LibraryThing fixed, I&#8217;m happy to say).  In it, <a href="http://www.sarahdopp.com/blog/?p=514" rel="nofollow">Sarah Dopp explains the influence issue of binary gender categorization</a>.  As I&#8217;ve said in letters to the ACM before they fixed their member survey (thanks!), my college Honors Department, and others, a poll (or drop-down menu) which only allows &#8220;male&#8221; and &#8220;female&#8221; defines people who don&#8217;t fit into binary gender categories out of existence, and reinforces rigid binary gender thinking which harms real human beings.  An &#8220;Other&#8221;, &#8220;Complicated&#8221;, or &#8220;Prefer not to say&#8221; option (or some mix of these, or all on one line) would encourage participation from people who just don&#8217;t fit so neatly, and would help remind people that it&#8217;s a big world with lots of kind of people in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ConFigures &#187; Blog Archive &#187; Fielded wikis and LibraryThing, a year and a half later</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-64977</link>
		<dc:creator>ConFigures &#187; Blog Archive &#187; Fielded wikis and LibraryThing, a year and a half later</dc:creator>
		<pubDate>Sat, 04 Jul 2009 23:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-64977</guid>
		<description>[...] had some experience working with fielded wikis since I wrote disgruntledly about LibraryThing&#8217;s implementation of them in October 2007.  I knew at the time of their potential for being able to extract info for other purposes, but I [...]</description>
		<content:encoded><![CDATA[<p>[...] had some experience working with fielded wikis since I wrote disgruntledly about LibraryThing&#8217;s implementation of them in October 2007.  I knew at the time of their potential for being able to extract info for other purposes, but I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ConFigures &#187; Blog Archive &#187; Visibility, Visualization, and Knowledge Gardening</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-12344</link>
		<dc:creator>ConFigures &#187; Blog Archive &#187; Visibility, Visualization, and Knowledge Gardening</dc:creator>
		<pubDate>Thu, 07 Feb 2008 17:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-12344</guid>
		<description>[...] Culture influence is hard without a critical mass of enthusiasts. Incentives may be difficult to distribute appropriately if tracking information/access is poorly set up, and incentives may get people into a mindset where one has to *keep* giving incentives to keep the contributions coming. Emailed reminders are all too easy to ignore (or filter straight to trash). Reminders inserted into the system&#8217;s interface may take up valuable real estate onscreen, which can make users unhappy (see previous comments exchange with Tim Spalding following my entry about LibraryThing&#8217;s fielded wiki &#8220;Common Knowledge&#8221; insertion onto each main page for books). LiveJournal&#8217;s &#8220;nudge&#8221; feature has annoyed users who don&#8217;t want to be guilted into blogging (it might be more appropriate for task-oriented communities). Games such as CMU&#8217;s The Name Game (picked up by Google for their Image Labeler game) may have a high start-up cost. [...]</description>
		<content:encoded><![CDATA[<p>[...] Culture influence is hard without a critical mass of enthusiasts. Incentives may be difficult to distribute appropriately if tracking information/access is poorly set up, and incentives may get people into a mindset where one has to *keep* giving incentives to keep the contributions coming. Emailed reminders are all too easy to ignore (or filter straight to trash). Reminders inserted into the system&#8217;s interface may take up valuable real estate onscreen, which can make users unhappy (see previous comments exchange with Tim Spalding following my entry about LibraryThing&#8217;s fielded wiki &#8220;Common Knowledge&#8221; insertion onto each main page for books). LiveJournal&#8217;s &#8220;nudge&#8221; feature has annoyed users who don&#8217;t want to be guilted into blogging (it might be more appropriate for task-oriented communities). Games such as CMU&#8217;s The Name Game (picked up by Google for their Image Labeler game) may have a high start-up cost. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ConFigures &#187; Blog Archive &#187; Visibility, Visualization, and Knowledge Gardening</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-12343</link>
		<dc:creator>ConFigures &#187; Blog Archive &#187; Visibility, Visualization, and Knowledge Gardening</dc:creator>
		<pubDate>Thu, 07 Feb 2008 17:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-12343</guid>
		<description>[...] Culture influence is hard without a critical mass of enthusiasts. Incentives may be difficult to distribute appropriately if tracking information/access is poorly set up, and incentives may get people into a mindset where one has to *keep* giving incentives to keep the contributions coming. Emailed reminders are all too easy to ignore (or filter straight to trash). Reminders inserted into the system&#8217;s interface may take up valuable real estate onscreen, which can make users unhappy (see previous comments exchange with Tim Spalding following my entry about LibraryThing&#8217;s fielded wiki &#8220;Common Knowledge&#8221; insertion onto each main page for books). LiveJournal&#8217;s &#8220;nudge&#8221; feature has annoyed users who don&#8217;t want to be guilted into blogging (it might be more appropriate for task-oriented communities). Games such as CMU&#8217;s The Name Game (picked up by Google for their Image Labeler game) may have a high start-up cost. [...]</description>
		<content:encoded><![CDATA[<p>[...] Culture influence is hard without a critical mass of enthusiasts. Incentives may be difficult to distribute appropriately if tracking information/access is poorly set up, and incentives may get people into a mindset where one has to *keep* giving incentives to keep the contributions coming. Emailed reminders are all too easy to ignore (or filter straight to trash). Reminders inserted into the system&#8217;s interface may take up valuable real estate onscreen, which can make users unhappy (see previous comments exchange with Tim Spalding following my entry about LibraryThing&#8217;s fielded wiki &#8220;Common Knowledge&#8221; insertion onto each main page for books). LiveJournal&#8217;s &#8220;nudge&#8221; feature has annoyed users who don&#8217;t want to be guilted into blogging (it might be more appropriate for task-oriented communities). Games such as CMU&#8217;s The Name Game (picked up by Google for their Image Labeler game) may have a high start-up cost. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ConFigures &#187; Blog Archive &#187; Tagging, ontology, and structured information</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-5941</link>
		<dc:creator>ConFigures &#187; Blog Archive &#187; Tagging, ontology, and structured information</dc:creator>
		<pubDate>Wed, 24 Oct 2007 22:09:52 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-5941</guid>
		<description>[...] Paper magazines seem to pile up unread at home.  I&#8217;m better at keeping up with online news/research.  I can tag and point others to online sources, after all.  I&#8217;ve been considering letting my ACM* membership lapse for a while, at least partly due to guilt over unread Communications of the ACM issues (though I keep up with the tech alerts they email me pretty well).  However, I did notice that their October issue has an article on Knowledge Management, specifically, &#8220;Knowledge Services of the Semantic Web&#8220;.  I actually went to the trouble of finding and linking to an online version of it (and tear out the paper version and hung it outside my cube for any interested colleagues).  From my reading, it&#8217;s an exploration of what sort of infrastructure might facilitate knowledge commerce (the trading of knowledge services, not just within an enterprise), with some specific proposals (mostly, what ontologies, but also a bit about registration entities and payment schemes).  It&#8217;s interesting to think about how knowledge commerce may develop.  Some of their search examples suggested a tagging solution to me.  However, there&#8217;s no saying that random taggers will be interested in adding the sort of metadata that leads to commerce or facilitates the kind of use an organization may wish to make of its data.  I can see why an organization might wish to encourage certain kinds of contributions through structured fields and other input mechanisms.  This approach comes with its own risks, of course.  Whatever they set up may become outdated quickly if their system/mechanism is not very flexible.  What&#8217;s more, the more that inputting seems like &#8220;work&#8221;, the less enthused people will be about adding metadata.  This may be just fine if what&#8217;s wanted is really just the experts/authorities adding metadata (not the hoi polloi), and there are enough of them, and they&#8217;re motivated, of course.  I think mashups between social software and structured information resources have a lot of potential, depending on the implementation and the critical mass.  Where things get tricky is when folks have different expectations about the interactions, as in my recent post about LibraryThing.  Tim, the founder of LT, wrote a very thoughtful comment, and I&#8217;ve been meaning to reply to it at length; this ACM article has helped me sort out my thoughts a bit. * By the way, I was cheered to notice that someone at ACM appears to have seen/taken seriously the feedback about their beta site.  Not just my feedback, I imagine, but anyway, I&#8217;m glad their post-beta implementation went in the direction I&#8217;d hoped. [...]</description>
		<content:encoded><![CDATA[<p>[...] Paper magazines seem to pile up unread at home.  I&#8217;m better at keeping up with online news/research.  I can tag and point others to online sources, after all.  I&#8217;ve been considering letting my ACM* membership lapse for a while, at least partly due to guilt over unread Communications of the ACM issues (though I keep up with the tech alerts they email me pretty well).  However, I did notice that their October issue has an article on Knowledge Management, specifically, &#8220;Knowledge Services of the Semantic Web&#8220;.  I actually went to the trouble of finding and linking to an online version of it (and tear out the paper version and hung it outside my cube for any interested colleagues).  From my reading, it&#8217;s an exploration of what sort of infrastructure might facilitate knowledge commerce (the trading of knowledge services, not just within an enterprise), with some specific proposals (mostly, what ontologies, but also a bit about registration entities and payment schemes).  It&#8217;s interesting to think about how knowledge commerce may develop.  Some of their search examples suggested a tagging solution to me.  However, there&#8217;s no saying that random taggers will be interested in adding the sort of metadata that leads to commerce or facilitates the kind of use an organization may wish to make of its data.  I can see why an organization might wish to encourage certain kinds of contributions through structured fields and other input mechanisms.  This approach comes with its own risks, of course.  Whatever they set up may become outdated quickly if their system/mechanism is not very flexible.  What&#8217;s more, the more that inputting seems like &#8220;work&#8221;, the less enthused people will be about adding metadata.  This may be just fine if what&#8217;s wanted is really just the experts/authorities adding metadata (not the hoi polloi), and there are enough of them, and they&#8217;re motivated, of course.  I think mashups between social software and structured information resources have a lot of potential, depending on the implementation and the critical mass.  Where things get tricky is when folks have different expectations about the interactions, as in my recent post about LibraryThing.  Tim, the founder of LT, wrote a very thoughtful comment, and I&#8217;ve been meaning to reply to it at length; this ACM article has helped me sort out my thoughts a bit. * By the way, I was cheered to notice that someone at ACM appears to have seen/taken seriously the feedback about their beta site.  Not just my feedback, I imagine, but anyway, I&#8217;m glad their post-beta implementation went in the direction I&#8217;d hoped. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: configures</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-5573</link>
		<dc:creator>configures</dc:creator>
		<pubDate>Thu, 18 Oct 2007 21:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-5573</guid>
		<description>Oh, no, it was a fair cop.  I&#039;d rather be called on something like that so I can correct it.

&quot;Categories are weapons&quot; -- sounds like a good title!

I&#039;m glad if my picture is useful for your talk.  Even if it turns out to be about Users Who Don&#039;t Get It, or something like that.  :-)  Really, there&#039;s a lot I like about LT; I wouldn&#039;t have taken time to blog about it or create that image if not.</description>
		<content:encoded><![CDATA[<p>Oh, no, it was a fair cop.  I&#8217;d rather be called on something like that so I can correct it.</p>
<p>&#8220;Categories are weapons&#8221; &#8212; sounds like a good title!</p>
<p>I&#8217;m glad if my picture is useful for your talk.  Even if it turns out to be about Users Who Don&#8217;t Get It, or something like that.  :-)  Really, there&#8217;s a lot I like about LT; I wouldn&#8217;t have taken time to blog about it or create that image if not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-5572</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 18 Oct 2007 20:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-5572</guid>
		<description>Sorry. That was snarky of me to notice, but I felt it tied into the point: categories are weapons.

Thanks for the picture. I&#039;m going to show it at a talk I&#039;m giving at a conference in Manhattan on Monday :)</description>
		<content:encoded><![CDATA[<p>Sorry. That was snarky of me to notice, but I felt it tied into the point: categories are weapons.</p>
<p>Thanks for the picture. I&#8217;m going to show it at a talk I&#8217;m giving at a conference in Manhattan on Monday :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: configures</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-5568</link>
		<dc:creator>configures</dc:creator>
		<pubDate>Thu, 18 Oct 2007 18:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-5568</guid>
		<description>Tim, thank you for your thoughtful reply to my bit of spleen.  I hope to post a longer reply, or another blog entry, tomorrow.

&quot;I mention this because it’s a nice demonstration of how categorization can be used in the place of argument. If I call you a “writer” (in quotes) I’ve simultaneously attacked and avoided having to justify myself.&quot;

You are right.  It&#039;s not a feature I wanted, but that doesn&#039;t invalidate its feature-ness; obviously some people (beyond LT staff) are excited by it.  I apologize, and I have edited my post to change &quot;feature&quot; to feature.

You&#039;re welcome to the image.</description>
		<content:encoded><![CDATA[<p>Tim, thank you for your thoughtful reply to my bit of spleen.  I hope to post a longer reply, or another blog entry, tomorrow.</p>
<p>&#8220;I mention this because it’s a nice demonstration of how categorization can be used in the place of argument. If I call you a “writer” (in quotes) I’ve simultaneously attacked and avoided having to justify myself.&#8221;</p>
<p>You are right.  It&#8217;s not a feature I wanted, but that doesn&#8217;t invalidate its feature-ness; obviously some people (beyond LT staff) are excited by it.  I apologize, and I have edited my post to change &#8220;feature&#8221; to feature.</p>
<p>You&#8217;re welcome to the image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://configures.sarahelkins.org/2007/10/16/not-the-librarything-i-signed-up-for/comment-page-1/#comment-5567</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 18 Oct 2007 16:57:40 +0000</pubDate>
		<guid isPermaLink="false">http://configures.sarahelkins.org/?p=55#comment-5567</guid>
		<description>Hey. I saw this on Google blog search and thought I&#039;d reply. If you consider it inappropriate, please delete it. I&#039;d ask you through LT, but I don&#039;t know your user name.

It is a feature, not a quote-unquote-feature. I have no problem calling this a blog, not a blog. 

I mention this because it&#039;s a nice demonstration of how categorization can be used in the place of argument. If I call you a &quot;writer&quot; (in quotes) I&#039;ve simultaneously attacked and avoided having to justify myself. 

The ability for categories and classifications to be &quot;used&quot; is a serious one. Clay Shiry calls this &quot;voodoo ontology,&quot; when your system forces your ideas on someone. Sometimes this is overt and intentional (eg., arguments in Congress of what race boxes to allow on the census form), sometimes the voodoo only takes hold later. It&#039;s hard to tell which came first with the Dewey Decimal System, but it&#039;s certainly the greatest example. Christianity gets 890 times as much space as Buddhism. Islam gets lumped in with a number of religions most Muslims regard with great suspicion. Portuguese is a special case of Spanish, women&#039;s education a special case of education.

As you say, tagging gets beyond this. Where LCSH is binary and professes an objectivity we can only question, tagging can express nuance and embraces something like multi-subjectivity. I go on at some length in my Library of Congress talk about this very issue, mentioning the subtle but important differences between &quot;gay,&quot; &quot;queer,&quot; &quot;LGBT&quot; and &quot;GLBT.&quot; In a weird sort of irony, the &quot;homosexual&quot; tag--which in the LCSH world is the simple unmarked expression--is, on LibraryThing, strongly identified with ANTI-homosexual literature. 

I think this problem is basic to classification. You can try to reach compromises, but, in the end, someone has to win. 

In the case of gender, you should note that I raised the issue in the initial blog post, and we have been in a deep discussion about it ever since. That we haven&#039;t resolved it says more about our deep love to discussion. (I might add that discussion has been pretty weak so far, with much more effort going into place names and such. Whether or not gender should be expanded or free-form, most users just don&#039;t care. I would encourage you to post there, even the link to this blog.)

So, in a sense, I think it&#039;s a step back too. It&#039;s a step forward insofar as a more rigid system does have some advantages. By enforcing one field (or a field which can become more than one) we force users to work together. 

Sometimes that&#039;s a bad thing, but it can also be good. Wikipedia--which you mention--is an example of how it can work. Wikipedia is user-contributed, but it does not simultaneously reflect all of its users opinions. It could fork, but it mostly doesn&#039;t. Things move toward consensus. 

Sometimes the advantages of classification and standards are won at minimal expense. The community is now working out rules for places. Without a unified system, people would use any old expression they wanted. By forcing users to come to agreement, we can ensure that Texas isn&#039;t split between &quot;Texas,&quot; &quot;Tex.&quot; and &quot;TX.&quot;

Incidentally, your point about discussion is well taken. In part, I think the community is small enough and engaged enough that the Common Knowledge group can do the job. But you have to be checking it. One possibility--which just came to me, so thank you for prompting this--would be to allow people to &quot;touchstone&quot; a work or an author in a way that specifically indicates CK is being discussed. That way we could put in the CK area a message like &quot;The Common Knowledge relating to this author are under discussion; click here to read this discussion.&quot;

Oddly enough, we actually DO have a comments feature, which would be an ideal place for footnotes. (Note however that Wikipedia&#039;s interest in citation is relatiely recent.) Every edit can get a comment. We haven&#039;t exposed this because, having built it in, we didn&#039;t see an elegant and unobtrusive way to expose this in the user interface. 

Unfortunately, all the options for exposing comments, discussion and etc. would require more space, which you&#039;ve already come out against. Physical space--or virtual physical space--like traditional classification, is something someone has to win on.

Thanks for the post. Do you mind if I snag the image from your blog for mine?</description>
		<content:encoded><![CDATA[<p>Hey. I saw this on Google blog search and thought I&#8217;d reply. If you consider it inappropriate, please delete it. I&#8217;d ask you through LT, but I don&#8217;t know your user name.</p>
<p>It is a feature, not a quote-unquote-feature. I have no problem calling this a blog, not a blog. </p>
<p>I mention this because it&#8217;s a nice demonstration of how categorization can be used in the place of argument. If I call you a &#8220;writer&#8221; (in quotes) I&#8217;ve simultaneously attacked and avoided having to justify myself. </p>
<p>The ability for categories and classifications to be &#8220;used&#8221; is a serious one. Clay Shiry calls this &#8220;voodoo ontology,&#8221; when your system forces your ideas on someone. Sometimes this is overt and intentional (eg., arguments in Congress of what race boxes to allow on the census form), sometimes the voodoo only takes hold later. It&#8217;s hard to tell which came first with the Dewey Decimal System, but it&#8217;s certainly the greatest example. Christianity gets 890 times as much space as Buddhism. Islam gets lumped in with a number of religions most Muslims regard with great suspicion. Portuguese is a special case of Spanish, women&#8217;s education a special case of education.</p>
<p>As you say, tagging gets beyond this. Where LCSH is binary and professes an objectivity we can only question, tagging can express nuance and embraces something like multi-subjectivity. I go on at some length in my Library of Congress talk about this very issue, mentioning the subtle but important differences between &#8220;gay,&#8221; &#8220;queer,&#8221; &#8220;LGBT&#8221; and &#8220;GLBT.&#8221; In a weird sort of irony, the &#8220;homosexual&#8221; tag&#8211;which in the LCSH world is the simple unmarked expression&#8211;is, on LibraryThing, strongly identified with ANTI-homosexual literature. </p>
<p>I think this problem is basic to classification. You can try to reach compromises, but, in the end, someone has to win. </p>
<p>In the case of gender, you should note that I raised the issue in the initial blog post, and we have been in a deep discussion about it ever since. That we haven&#8217;t resolved it says more about our deep love to discussion. (I might add that discussion has been pretty weak so far, with much more effort going into place names and such. Whether or not gender should be expanded or free-form, most users just don&#8217;t care. I would encourage you to post there, even the link to this blog.)</p>
<p>So, in a sense, I think it&#8217;s a step back too. It&#8217;s a step forward insofar as a more rigid system does have some advantages. By enforcing one field (or a field which can become more than one) we force users to work together. </p>
<p>Sometimes that&#8217;s a bad thing, but it can also be good. Wikipedia&#8211;which you mention&#8211;is an example of how it can work. Wikipedia is user-contributed, but it does not simultaneously reflect all of its users opinions. It could fork, but it mostly doesn&#8217;t. Things move toward consensus. </p>
<p>Sometimes the advantages of classification and standards are won at minimal expense. The community is now working out rules for places. Without a unified system, people would use any old expression they wanted. By forcing users to come to agreement, we can ensure that Texas isn&#8217;t split between &#8220;Texas,&#8221; &#8220;Tex.&#8221; and &#8220;TX.&#8221;</p>
<p>Incidentally, your point about discussion is well taken. In part, I think the community is small enough and engaged enough that the Common Knowledge group can do the job. But you have to be checking it. One possibility&#8211;which just came to me, so thank you for prompting this&#8211;would be to allow people to &#8220;touchstone&#8221; a work or an author in a way that specifically indicates CK is being discussed. That way we could put in the CK area a message like &#8220;The Common Knowledge relating to this author are under discussion; click here to read this discussion.&#8221;</p>
<p>Oddly enough, we actually DO have a comments feature, which would be an ideal place for footnotes. (Note however that Wikipedia&#8217;s interest in citation is relatiely recent.) Every edit can get a comment. We haven&#8217;t exposed this because, having built it in, we didn&#8217;t see an elegant and unobtrusive way to expose this in the user interface. </p>
<p>Unfortunately, all the options for exposing comments, discussion and etc. would require more space, which you&#8217;ve already come out against. Physical space&#8211;or virtual physical space&#8211;like traditional classification, is something someone has to win on.</p>
<p>Thanks for the post. Do you mind if I snag the image from your blog for mine?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
