Joshua Porter at Column Two comments about folksonomies in the context of CMS:
Many of the design teams we talk to face the same major issue: how to organize the information on their sites. From creating navigation schemes to developing site hierarchies to refining checkout sequences, it’s highly important for design teams to organize information effectively for their users.
Information architects frequently must deal with the problem of managing more and more information. Rarely can they remove information from a site; in most cases, it’s add, add, add. Design teams must make room for this new content in some way, either by incorporating it into the current organizational scheme or by altering the information architecture to allow for it.
At this point, folksonomies are more of an interesting technology than a tried-and-true design tool. However, with their ability to let users do most of the organizational work of the information on a web site, they may yet prove to be a valuable, time-saving way for information architects to keep a handle on the addition of information into an already-burdened architecture. We’re anxious to see where they go.
(Via Column Two.)