I came across The Harry Potter Automatic News Aggregator, which made me think if topic-based aggregators are the way of the future. It is a point also made briefly by Ted Leung, who says: "There's a role here for topics and categories. People have been talking about topical weblogs but I'm not sure I'm ready to go that far. I am more than happy to have topical aggregators like JavaBlogs or SeaBlogs, etc. where I can go to trawl for new bits."

Adam Bosworth writes: "Web services holds the potential to change all this and the rapid rise of mobile computing and occasionally connected laptops is going to help drive the changes. The world is now holding its breath for a zero-install cross platform browser that talks web services to the net, not HTML."

This is where the microcontent client comes in. A related point echoed by Steve Gillmor: "We need something very much like an RSS information router, one with authenticated searchable persistence, shared cacheable peered feed notification servers, and automated RSS registration."

Vikas Kamat writes on the requirements of a knowledge management solution, based around blogs:

A K-Log system must have categorization -- this can be human specified (like in Movable-Type), or automated via a content classification engine (CCE).

Full-text search is also essential to dissimilate the knowledge.

Chronological organization of posts is quite useless in a K-Log. Rather, organization by importance (most important), relevancy (post popular), author, and whether peer-reviewed or not, are more important.

At all the installations, the customers asked a search by Last-Updated feature. This tells many things (more below)

Knowledge is not equal -- some posts must be available only to some eyes.

As absurd as it might sound, nicely printing the blog post is very important. I have seen executives go to meetings with thick stack of blog printouts!