I see Zbigniew beat me to blogging about wiki-wednesday. That’s one of the perils of laying around in bed all morning.

He’s dead right about Alan Wood’s presentation being very exciting. I’m probably even more impressed by Wood’s “Rel3” than Zby is.

What most impressed me was Alan’s apparent good taste that seems to be formed by real experience. Rel3 isn’t an attempt to take a particular genre of social software as it exists and force it into the enterprise, but a crafted, pragmatic response to particular needs.

Yes, it looks very like a non-threaded discussion forum. In fact it’s also a bit like a page of “River of News” for a single issue being handled within a group. There are echoes of TopicExchange and explicit inspiration from Twitter.

Behind the scenes things seem just as interesting. Written originally in Java, then ported to Rails and now to Erlang. It’s designed to use Amazon’s S3 and EC2. (The fact that it keeps data in files on S3 prompted leaving Rails.) Each page (or conversation) allows files to be attached so you can manage Word, Excel, PDF docs, etc. When asked if he’s thinking of creating some kind of Ajaxy online editor for collaborative documents, Alan sensibly says he won’t re-invent the wheel but will provide hooks to other providers of this kind of stuff.

In other words, this is a very nice, minimal “glue” to tie together the people and resources that temporarily need to be brought together to solve a particular problem. After which the page doesn’t hang around cluttering up your ontology when you have lost interest in it. (I mean, it probably *does* hang around. But Alan Wood, interestingly, contrasted Rel3 with wikis which allow a small group to work producing a more permanent document that must stake its claim to some part of the name-space.)

In this, it has some of the best features of other social software, in particular, I think it has potential to rival email’s special power of spontaneous group forming and dissolving. Let’s see if actually creating, subscribing and unsubscribing to pages can be quick enough.

Also, Alan has a very smart blog at Folknology

There’s a new crop of business wikis. And some interesting discussion.

But what’s wrong with this picture?

SystemOne, an enterprise-knowledge-management system masquerading as an ordinary business wiki. What’s cool about this product is that it automatically creates, at the bottom of each page, a list of relevant other wiki pages, feeds, and Web search results. The autocreation of the links removes some of the need to manually create links to connect wiki pages together. This is a key feature if the wiki is to be used by a lot of people who aren’t hypertext-savvy.

Answer : Everything is wrong here.

Firstly, what’s the point of automatically making hyperlinks for people who aren’t web-savvy? Or rather, why are you trying to get people who don’t understand hypertext to use wiki? (In fact, in 2007, why are you even employing people who aren’t hypertext savvy? But that’s another story.) At the very least you should ask how exactly they are going to use wiki if they can’t understand what hypertext is, or have some intuition about how to use it?

Remember, this is wiki we’re talking about : all the hard graft of making links (like the trivially fiddly writing of “anglebracket a href”, and the genuinely tricky part about finding the right URL to point to) has been eliminated by the simple WikiWord or [[double square bracket]] conventions. What’s left is the only other difficult question : deciding what links to make.

SystemOne “solves” that part for you. But remember, the links are part of the valuable decision-making and information that goes into your wiki. Wiki links are not meant to mean that “this page is vaguely similar to that web-page”. If I want to know what pages are vaguely similar I can use Google. Wiki links mean “I, the author, want the reader to notice this kind of similarity between this page or this paragraph or this word, and that page because I think it’s significant.” Which is far more precise and subtle piece of information.

A wiki which automatically creates links is as useless as a word-processor which claims to write your letters for you.

The purpose of creating documents is not to kill trees or fill up as much disk space as possible. The purpose of creating documents is to capture the value added by human intelligence. Attempting to automate away that, in order to help consume more wood-pulp or fill the screen with more blue-underlines is counterproductive. Bad links devalue the good links. The reader of a page is overwhelmed and confused.