I object to folksonomy because it's another example of inventing new words when perfectly good English words already exist. Using the term "folksonomy" might be great for web developers to talk about, but when you are trying to make a tool useful to everyday people, you use plain langage. No, plain language isn't as precise as jargon, but it doesn't need to be when you are talking to end users. On 9/29/05, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi!
Despite what Shakespeare says about the name of the rose (What's in a name? That which we call a rose / By any other name would smell as sweet), it's still more convinient to call it a rose, simply because (lot) more people would know what are you talking of.
"free tagging" has 13,300 results while folksonomy has 1,220,000 results according to googlefight. It's not that "free tagging" is bad, it's just that we are creating another barrier. Look at taxonomy vs. categories... it's still more accessible to call it "categories" while the savvy developer know that "Drupal categories" is another name for a rose called "taxonomy". I am ready to admit that "free tagging" is not folksonomy, but again, taxonomy vs. categories. You can say that taxonomy vs. categories is the camel nose in the tent. I will disagree.
Regards
NK
-- Dondley Communications http://www.dondleycommunications.com Communicate or Die: American Labor Unions and the Internet http://www.communicateordie.com