Folksonomies and What’s At Stake

by Joshua Porter  |   8 Comments

Clay Shirky over at Many-to-Many recently linked to a Matt Locke post about folksonomies that I found interesting.

Locke seems skeptical about the revolutionary merits of folksonomies, ultimately seeing them as nothing more than “playing”. He comes to this conclusion by way of his assertion that folksonomies are only useful when “nothing is at stake”.

I disagree.

First off, I don’t like the term “at stake”, because it is too subjective. What Locke sees as high stakes I may see as low stakes, and vice-versa.

His initial example of nursing helps shed light on this. The Nursing Interventions Classification, Locke says (example taken from the book Sorting Things Out), was needed “in order (for the nurses) to be adequately recognised and compensated by hospital authorities”. This reason, it would seem, is the high stakes for which the formal NIC classification is necessary.

To me, the high stakes isn’t what nurses get paid, it’s how healthy their patients are. And Locke points out that several nurse professionals resisted the NIC because their informal taxonomy based on “natural” language was how they were used to doing their jobs. So, they seem to be practicing this “invisible work” while the very patients’ lives are at stake!

Secondly, Locke questions the implications of folksonomies without questioning the merits of what they might replace or improve upon. Certainly, we should be asking questions about who is benefitting (and becoming marginalized) from collective action classification. But what about formal classifications? Are there not benefits and marginalizations there as well?

Of course there are. One marginalization of a controlled vocabulary is that it cannot possibly elucidate all the ideas it contains. By definition, controlling a vocabulary is controlling the words with which people use within it, thereby reducing the number of possible interpretations. This is a shame. I, for one, believe that the more people express an idea in their own words, the better everyone else’s interpretations become.

Another marginalization is the disadvantage of people who don’t know the vocabulary, but who have to work within it nonetheless. When my wife and I bought our condo, for example, we knew very little about what was actually going on, despite our best efforts to learn the terminology. In fact, I know that if I knew then what I know now that we could have gotten a better deal than we did.

So my question is: When are formal classifications not the bee’s knees?

Thirdly, this really seems to be about standardization and precision. I certainly won’t argue the benefits of standardization, because it is how many things get done. In domains where precision is necessary: (Locke suggests the legal, financial, and political domains), we certainly need standards so that “transactions” are agreed upon.

But in other domains where we do not need precision, it is wrong to say that nothing is at stake. Indeed, everything is at stake because these are the domains in which we are learning. It could be that we are figuring out how to make them into precise domains. We might call these the learning domains. Sure, we play there too, but aren’t these domains as important to leading happy lives as any that rely on financial or legal precision? I don’t think we should discount them by saying nothing is at stake.

Finally, though I’m arguing against some of Locke’s terminology, I’m not really disagreeing with his overall gist. I think that folksonomies are as much a revolution in scale as a revolution in anything else, save one thing. That one thing depends on the visibility that Locke talks about.

Because we are here now, able to look into the minds of others using their very own words, we have the ability to learn more, and learn faster, than we ever could before. We learn not just from those lucky enough to be published, but we learn all the way down the long tail.

Comments ( 8 Responses so far )

1.  CM Harrington on March 4th, 2005 (Comment) #

The problem with “folksonomy” 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 “folksonomy” 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.

2.  Bud Gibson on March 4th, 2005 (Comment) #

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’s likely to be disagreement. There are all sorts of ways to handle that.

I’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’ll see what we get of value.

Personally, I am watching with interest what Ben Hammersley is doing at The Observer Blog.

3.  bill h-d on March 7th, 2005 (Comment) #

The “folk” in folksonomy doesn’t connote “personal” so much as it does “vernacular.” 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.

4.  Matt Locke on March 14th, 2005 (Comment) #

Thanks for these comments - they really add to the ongoing debate. I particularly value your idea of the ‘learning domain’ within taxonomies - you’re right that Folksonomies, by their fluidity and collaborative nature, keep this learning domain open for as long as possible.

For the record, i’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 ‘hard’ 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 ‘nothing is at stake’. 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 ‘Sorting Things Out’.

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.

5.  Josh on March 17th, 2005 (Comment) #

Matt,

I agree that we shouldn’t be the ones who decide what is at stake. We wouldn’t agree, and even then our opinions don’t matter. Well put.

I’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’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 “transactions”, in which we allow little interpretation as possible.

I’m still convinced, however, that in most communication systems we need a high level of interpretation, because we really don’t understand things in the same way.

6.  facebook news blog on April 19th, 2007 (Comment) #

Amazing tutorial! Really apreciate that – thanks!

7.  Lion on May 14th, 2007 (Comment) #

Ecellent article, thank you.

8.  pickuplines on October 23rd, 2007 (Comment) #

Great job! Rock on dude!

Add Your Comment

Accepted tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> .

Preview...

If your comment contains links, or if it is your destiny, your comment may not show up immediately. I'll approve it as soon as I can. (I delete dozens of comment spams per day)

Get updated when someone posts a comment: Comment Feed


ABOUT

Bokardo is the blog of Joshua Porter, a web designer/developer, researcher, and writer. I live in Newburyport, MA, USA.

WHAT IS SOCIAL DESIGN?

Social design is design that focuses on the social lives of users. It deals with the activities, behaviors, and motivations of people who work and play together through software interfaces. It is built on the observation that many of the decisions we make are greatly affected by those we surround ourselves with in our social lives: our family, friends, and colleagues. Exploring our motivations and how to design interfaces to support them is what the Bokardo blog is all about.

Designing for the Social Web

Building a social web site or application? I wrote a book just for you!

designing for the social web

Find out more or order from Peachpit or Amazon

Upcoming Speaking Events