Flipping through the 2nd edition of the Polar Bear book, I found an interesting section that portends the use of bottoms-up, user generated, emergent navigation systems, my latest muse. I did not expect to find such a passage, given Peter Morville’s recent talk on folksonomies at the IASummit, but nonetheless both he and Rosenfeld we able to portend the coming change in navigation systems even a couple years ago.

The passage begins on page 355. Here it is:

The practice of information architecture has come a long way since the early 1990s. We began with highly centralized, top-down approaches, attempting to leverage careful planning into stable solutions. We did some good work, but learned the hard way that change is a constant and surprises should be expected. More recently, we’ve been exploring bottom-up approaches that tap the distributed intelligence within our organizations to nuture emergent, adaptive solutions. The following table compares classic or “top-down” IA to modern or “bottom-up” IA:

Classic IA	Modern IA
Prescriptive	Descriptive
Top-Down	Bottom-Up
Planned	Emergent
Stable	Adaptive
Centralized	Distributed

As we struggle with these ideas, an interesting question arises. Do we create information architectures or reveal them?

So, given that the 2nd edition of the Polar Bear book was published almost 3 years ago, the authors have certainly had time to get used to things like folksonomies coming along and stirring things up. After all, the table displayed above is no less than a great overview of the differences between taxonomies of the classic IA and folksonomies of the modern IA. So, my dear reader, why is Morville still bearish on folksonomies…? Even the wonderful folksonomy video post by Peter Van Dijck doesn’t shed light on this.

Dan Bricklin (co-creator of Visicalc, the first spreadsheet) on the February 4th edition of the Gillmor Gang, quickly talks about how information architecture has changed. He mentions that Google was the big surprise, cutting through the riff-raff in a time when much research was being done on automated taxonomies and hierarchical systems.

Bricklin makes a distinction that I think is hugely important: automation. Automation means “automatically controlled”: to be automated means to have controlling decisions made without conscious or voluntary intervention.

But what about Google, you ask? Isn’t that automated? Surely, people aren’t sitting there deciding which links to give a higher pagerank to, right?

Actually, that’s exactly what’s going on here, but the people in question don’t work for Google. The people in question are the ones making the decisions about what is valuable to them by publicly linking to another URI. (In other words, the people actually making the web sites.) This is the important part of Google, and it is NOT automated. What is automated is the aggregation and display of this behavior. It’s a subtle, but vital, difference.

Also, at the E-Tech summit del.icio.us’ creator Joshua Schacter brings up another important point related to this topic (folksonomies in particular). As quoted in Cory Doctorow’s impressionistic transcript:

“We have different axes of why you’re tagging, what you’re tagging and how it happens. Flickr you mostly tag your stuff for your own purposes, in Technorati, it’s your stuff for others’ purposes, and in Delicious, it’s others’ stuff for your purposes. They’re different things, they don’t necessarily flow together.”

One of the things that this tidbit shows is how different folksonomies can be, even though they’ve been lumped together by those talking about them (including me). Given that, and the growing interest in these things, it seems as though we’re only just beginning to scratch the surface in terms of bottoms-up architectures.

Part two of the series “Deciding What Features to Implement”. In this edition I observe a powerful new class of features that emerge from the aggregated behavior of a web site’s users: emergent features.

Continue Reading: Deciding What Features to Implement: Let Features Emerge From User Behavior

Hey Information Architects, I’ve got a question for you…

Continue Reading: An Open Question for Information Architects

Via Dave Winer: Robert Scoble brings up some interesting points in a post about the new Opera/WASP campaign called the Acid2 test. The test is being proposed as a way to get all browser makers supporting the same standards by having them test their browser against a full-featured web page that contains elements and styling that aren’t supported consistently at the present time.

Scoble, a Microsoft employee, is somewhat upset with WASP for not letting him in on the party beforehand. And given his status as the Microsoft liason of late and his influence around the blogosphere, it does seem odd that nobody talked to him first. He seems to really want to help, and he’s got the ear of the right people in Redmond. That said, the WASP seems like a rather mysterious group.

Another thing: this issue is one of those tough ones where a relatively large company has little incentive to do something other than “it’s the RIGHT thing to do” (it has not been shown what Microsoft would gain from this). I’ve long been frustrated by these sorts of things, and I wonder if publicly challenging them might not be the best thing to do. This reminds me of a recent spat between Joe Clark and Anil Dash about the accessibility of the Movable Type interface. Joe was calling “bullshit” on Six Apart because he had been after them for 6 months to comply with certain accessibility standards, and they hadn’t done what he asked.

I know that sometimes it does help to get the crowd involved, the “media” if you will, but I usually find that there is a disconnect between what the company sees as valuable and what the requesting party sees as valuable. It will be interesting to see if Microsoft is “encouraged” by the ACID2 test.

So I wonder: what is the incentive for Microsoft to change their CSS 2 support? Is the only incentive because WASP wants them to? Or because they don’t want to look bad to developers? Or because WASP wants the media to get involved (as is already happening on Cnet) and then Microsoft would look bad to a lot more people? Also, where is the user in all this? Are they going to see any benefits?

Another tactic might be to directly link what Microsoft really wants (to keep/increase their marketshare) with what goals WASP is selling (standards compliancy). The question is, though, does standards compliancy lead to marketshare? Well, what does the success of Firefox tell us? Was Firefox’s marketshare gain only a security issue, a developer tools issue, or a standards-compliancy issue?

Jon Udell has provided what is perhaps the best example of both the usage and the issues within the del.icio.us bookmarking service. I highly recommend you check this out! Especially if you’re a folksonomy skeptic…

The more I use del.icio.us and observe other folksonomies, the more I realize that we don’t use them to find “stuff”. We use them to discover “personally-related stuff”, which is really hard to do with a search engine. As I mentioned yesterday, Peter Morville’s slides from the IASummit seemed to try to compare two representative services, Google and Flickr, with the implication that folksonomies can’t Search as well as, well, Search can. (Morville compares the services on the axes of “quantity”, “quality”, and “findability”) Anyway, I think he’s absolutely right about that. Search is the best Search…

However, I think that comparing them this way is like comparing a Humvee and a Corvette on gas mileage and speed. It doesn’t really tell us everything. I think he gets the usefulness of folksonomies wrong: we don’t use them to help us Search like we do with Google.

In Search, we have no idea who the results belong to before we get to them. They are simply the most relevant results to whatever words we type in. Highly useful, of course. But not Personal. In folksonomies, on the other hand, we get to discover content based on who is tagging it. This is powerful because now we can judge content in terms of who is tagging it, and not just how relevant it might be to some algorithm that doesn’t take into account who-knows-who. Just like the movies, we tend to value the judgments of people we know (or are familiar with online) more than people we don’t know.

Speaking of Google, their new customized news pages are going to change the way people get news. The idea isn’t new, just ask Yahoo. But what is different here? It’s the news, of course. Just news. All news. Your news. And they don’t even have RSS feeds yet!

Take a look at a personalized news page that I whipped up in about 3 minutes (easy as cake). I’ve got two customized sections, one for “blog” and one for “folksonomies”.

The Web is becoming the Aggregation Nation.

Gene Smith has a quick writeup of the IASummit Folksonomies Panel with the slides from each of the speakers. The slides, even without the context of voice, give a quick overview of some of the issues that were talked about.

If you’re familiar with any of my past posts on folksonomies:

• A Self-Referential Demonstration of the Power of the Del.icio.us Folksonomy
• Folksonomy Notes: Considering the Downsides, Behavioral Trends, and Adaptation
• Controlled Vocabularies and Folksonomies: Why Change is Good.
• Folksonomies and What’s At Stake

…then you’ll know that I’m very optimistic about them. From what I can tell from the slides (which isn’t much), Morville doesn’t think you can find anything in folksonomies, Merholz is hesitant, and Smith and Vander Wal optimistic. I really hope these folks write up their talks so that those of us who didn’t attend can get a clearer picture of what they’re saying.

Smith also mentions the feeling that folks don’t know where to use folksonomies…which is a question I discussed here: I’ve Heard of Folksonomies. Now How do I Apply them to My Site? (short answer: you don’t need tagging to create features that leverage actual user behavior, you just need something explicit and aggregable)

Moving down the conference trail brings us to SXSW (South by Southwest). There, a similar discussion panel “Leveraging Solipsism” went on and Liz Lawley tracked it on Many-to-Many. She found Don Turnbull’s part the most interesting, and she provided us with a few of his interesting questions about tagging:

• Who controls the sharing? And who controls those controls??
• anonymity vs community (and privacy issues related to this)
• free riders—people who never tag, just browse
• what constitutes a community? are personal relationships necessary? do they grow out of the information sharing, or define with whom you share information?

All interesting questions.

Also, over at Shelley Power’s burningbird, I found one of the comments to her in-depth overview of tagging called Accidental Smarts (which has an excerpt from bokardo), quite interesting. Hans Gerwitz makes a distiction between “bookmark aggregation”, “link aggregation”, and “tag aggregation”, using del.icio.us for the first and last terms and technorati for the middle one. Interesting… (note: scroll all the way to the bottom of that amazingly long page to read the comment in question)

Editor’s note: this is a new format for topics in which I want to aggregate and pass along information, but don’t have the time to do a full writeup. I’m calling the format “notes”. These posts will be about a single topic or two and will contain several links to resources that I find interesting along with a bit of contextual commentary. I hope you find them interesting, too. (most Notes won’t be this long)

I’ve been talking a lot lately about the theory behind controlled vocabularies. Most of my talk has been around the idea that they are not inclusive, don’t allow for change, and aren’t as user-centric as folksonomies, the new kid in town.

However, as two commentors politely pointed out, I’m not really giving controlled vocabularies their due. What I’m really doing is pointing out that controlled vocabularies are really hard to implement, which doesn’t exactly mean that they’re bad, but only that most don’t live up to their potential. I’m now convinced that if they were implemented successfully, with a dedicated team, that some of the issues I’ve brought up aren’t as big a detriment as I’ve painted them. (I’m really glad that the folks who comment on bokardo are really bright people)

One of those commentors, Bud Gibson, pointed out an interesting session he attended at IASummit 2005. (My boss Jared suggested that I go next year: he really enjoyed it). Anyway, the session Bud pointed out was given by a group of folks from IBM and was called: Traversing the Corporate Web: IA and Taxonomy at IBM. (here are the notes in .ppt format that didn’t work on my Mac). After combing through the copious notes (presentations are so much better than notes), I came away thinking “Wow, IBM’s intranet is huge!”. Also, I found the team’s problem statement very enlightening:

1. Confusion about how taxonomies work to solve information problems
2. No best practices for using and applying taxonomies
3. Disparate groups developing taxonomies
4. Process-heavy change management around taxonomy
5. No clear engagement path for users & stakeholders to affect change
6. Decentralized taxonomy tools and inconsistent taxonomy formats
7. Strict rules for terminology management that often don’t meet user’s needs

When considering these problems, remember that this taxonomy has over 3,700 categories! Pretty impressive, huh? Also, Bud’s own post about this session included the claim that IBM will be trying out folksonomies to help with these issues, but I didn’t notice that word in the notes…again, presentations are so much better than notes. Folksonomies or not, this team is dealing with issues that are pertinent to all designers.

Continuing on this theme, David Weinberger has written a report for Esther Dyson’s Release 1.0 called Taxonomies to Tags: From Trees to Piles of Leaves, in which he talks about tree-like knowledge structures vs. other options. The report costs a robust $80.00. For those of you without the momentum to pay for that, David has luckily provided the first chapter as a teaser. He’s got a bunch of good insights here, but I’ll only post his interesting conclusions, comparing trees (hierarchies), faceted systems, and tagging systems (folksonomies):

1. Because they are unambiguous, trees work well where information can be sharply delineated and is centrally controlled. Users are accustomed to browsing trees, so little or no end-user training is required. But trees are expensive to build and maintain and require the user to understand the subject area well: How do you find the recipe for bread soup if you don’t know to look in the “Tuscan Cooking” category?
2. Faceted systems work splendidly where an application is being used by such a wide range of users that no one tree going to match everyone’s way thinking. They are also easier maintain than trees because adding new item requires only filling in the information about facets, rather having make decision exactly which category it should go into.
3. Tagging systems are possible only if people are motivated to do more of the work themselves, for individual and/or social reasons. They are necessarily sloppy systems, so if it’s crucial to find each and every object that has to do with, say, apples, tagging won’t work. But for an inexpensive, easy way of using the wisdom of the crowd to make resources visible and sortable, there’s nothing like tags.

So, I hope these prove interesting. Thanks to Bud and David, this has been the inaugural set of Bokardo Notes…

Controlled vocabularies are, by their very definition, exclusive. The Long Tail paradigm, however, relies on inclusion. So, doesn’t that leave us with an easy choice?

Continue Reading: Controlled Vocabularies Cut Off the Long Tail

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”. […]

Continue Reading: Folksonomies and What’s At Stake

Deciding what features to implement on a site is not easy. It’s not that designers lack ideas, we often have many of them: too many to implement. Somehow we have to sift through these ideas and figure out which ones are the best ones to implement in the scope of the project and which ones aren’t worth the time and effort. Here’s one way how.

Continue Reading: Deciding what Features to Implement: Go for the Win-Win.