generation neXt reports that three new blogging books (auf deutsche) are coming out.

• BLOGS! Die Weblogs – Literatur und Journalismus im Internet by a Who's Who of the blogosphere (Weblogwelt, actually).
• Das Blog-Buch by Dirk Olbertz
• Generation Blogger by Markus Christian Koch and Astrid Haarland 

Still room for a manager's guide to blogging. Must get back to that...

I wonder if there's a readership for an annual best blog posts of 2003 book. I know they do it for poetry and short stories.

Working notes from D. Keith Robinson's project of moving most of the hospital's intranet into Moveable Type. Useful observations on deployment, template design, new uses (project coordination). "Don’t let anyone tell you that you need to spend thousands of dollars to do distributed authorship or content management the right way. It’s simply not true." (Staff time excluded, of course.)

An entry from the Bush in 30 Seconds contest.

David Gammel:

I'll be leading a presentation on using weblogs as a knowledge sharing tool on January 8, 2004 in Washington DC. The event is sponsored by the American Society of Association Executives, an association I am active with, and can be attended in person or via conference call. While the content will be spun toward the pecularities of membership organizations, I think it will be useful for anyone interested in learning about klogging. It is very much an entry level session, so it may not cover new ground for many of you.

You can view our presentations notes and resources. This is a set of wiki pages, so feel free to add resources to the relevant pages if you know of something/sell something related to knowledge blogging. I'll continue to update the pages right up until the presentation, which is why some of the lists are a little thin at the moment. The main registration page for the session.

A lot of the presentation builds on discussions held here in the past as well as on the numerous blogs writing about knowledge management/sharing.

Looks good, the kind of briefing lots of us are giving.

I really want a standalone autodetection tool. As I surf, it will:

• live in the Windows system tray
• parse pages for urls pointing to syndication formats like RSS and Atom
• verify those feeds exist and collect their metadata
• write a log file of the detection and verification info, in OPML
• display the number of new discoveries when hovering over the system tray icon
• push the file to a server, periodically and optionally.

By being a separate application from the RSS newsreader, the autodetective will be:

• Smaller, consuming fewer system resources than a newsreader
• Focused on the craft of detection, becoming smarter about finding things on the pages I read
• Independent of a newsreader, so I can have more than one newsreader (including browser-based ones) without having every page I read parsed for each tool.
• Diverse, detecting tidbits in my emails, chats, IRC sessions, etc.

If we wanted to get fatter about the client, it could spider to discover deeper (crawl this site) or discover wider (crawl the blogrolls you see). Less relevance than pages you've actually seen, but more context - especially as you revisit favorite blogs and services.

I'd also like the detective to discover more kinds of things and make sense of them:

• Contact information (emails, phone numbers, postal addresses)
• Physical locations (postal addresses, city names, geocoding)
• Calendar events (dates, times, durations, descriptions)
• Rich media (sound, video, flash files)  

so I can review and bring them into other software.

There should be programming specs, so they know how to find the detective's journals, and check if they've been updated with fresh discoveries. I didn't include a "new headlines" balloon or ticker in the detective's features. The detective isn't a newsreader.

The detective should listen to your newsreaders too. Your newsreaders should also push the locations of your subscription lists ("you can find what Phil is reading at http://...") to the detective. This way the detective can optimize its reports by checking your subscriptions, then excluding them from discoveries. 

Let me browse and edit my discoveries in a human-usable form. I may want to delete items from my history before sharing them with a newsreader.  

I have an identity that lives across multiple computers and cell phones. I'll have detectives on each. My detectives should be able to confer and harmonize their discoveries. I may have multiple users on any computer, so detection prefs and journals should be aware of user profiles.

What's the business case?

• Strategy: Environmental Awareness. What's the cost of missing that a trusted feed has moved? That a key customer/competitor/regulator has a new feed? What if we made our collective surfing of the Internet into a competitive analysis tool, each person contributing their view of the world? With detectives on everyone's desk, we're less likely to be surprised, more likely to catch new opportunities, and be smarter as a group than our competitors.
• IT: Enterprise System Integration with Newsreaders. We're creating feeds of all sorts of information, including RSS of our SAP transactions. Many of these feeds will be customized for a specific context ("here's the RSS for orders Mary should approve.") The detective does away with error-prone cutting and pasting, automating the process of "I want to follow up on this". These feeds will drive attention to workflow and process. Some of the feeds will trigger people to write about specific items in team and project weblogs, improving communication.

I'll pay $20 retail for this.

Assuming you have an intranet blog server and either a server based news aggregator or desktop newsreaders, what would you pay for a 100 user site license?

Do you want one?