I've posted the 3rd draft of the liveTopics license here for review.  It's nearly done I just need to know that people are comfortable with section 3 and what, if anything, I need to go in section 5.  The end is in sight (which is good because I've done a fair bit of work that I want to release).

There are two dimensions to their differences - the first the psychological dimension and the second the technology dimension. One of the major psychological differences is that you own your weblog - it is YOURS - and it represents a history of YOUR thinking - so you take pride in its ownership - something that does not make a lot of sense in a discussion forum. On the hand on the technology front - [Ray Ozzie] sums up one of the major differences:

From [Architecture Matters: The Rebirth of Public Discussion by] by [Ray Ozzie] [Gurteen Knowledge-Log]

» Excellent point.

CKO mistakes. Udai Shekawat writes about Five Mistakes CKOs Must Avoid, which explores why many KM initiatives fail, from a Chief Knowledge... [Column Two]

» Really good thoughtful article.  Some highlights:

• Solution: CKOs must execute their strategies in the context of the business problem, define the criteria for an ideal solution and then identify the closest technological match.
• After all, what good is a KM solution if employees do not use it?
• While the 20% of the organizational know-how that is represented in documents is indeed important, the remaining 80% of know-how walks out the door every evening.
• There is a natural tendency in large organizations to assess what knowledge resources already exist in the company and then select a KM solution that can best enable the employees to utilize those resources.
• It is the responsibility of every person in the organization to create, share, refine knowledge.
• So, coaching is a key -- you cannot take people out of the equation, and capturing the "context" or the story or the situation around the answer is just as important as capturing the answer or solution itself.

Especially interesting was the view that a CKO must take a strategic, demand-driven approach rooted in solving business problems.  Not KM for KM's sake.  This gels with the comments at Knowledge Cafe that it was hard to justify KM.  I'm not suggesting that the person who said that was not taking a strategic approach, simply that it is not necessarily widely understood.

From NewScientist: Musical approach helps programmers catch bugs. Professors developed a system that automatically converts Pascal source code into simple "music". 

Can we mine RCS community servers, blogs and posts for metadata to compose a live music track?

Help me tell posts/sources apart. Help wade through hundreds of feeds and thousands of posts in a newsreader.

• Use popularity, link density, post length, freshness, Flesch and other readability statistics, comment thread length

Help me find gems.

• Connections with my blog, the relevance of this source's last 50 posts to my last 50 posts.

This is not audio blogging so much as blog visualization. Cool. Something to do after DayPop and blog SNA become blasé.

I sing the blogspace electric.

[a klog apart]

» It's a lovely idea.

How do you turn ideas into music?

Questions for Dave. In the comments to Entry below, Dave Winer says: "To everyone, I believe the new spec is leaps and bounds... [Content Syndication with XML and RSS]

» Depressing, depressing, depressing.

One of the 7 habits (of Stephen Covey fame) is "Seek first to understand, then to be understood."  The tension in this discussion is rising fast and empathic listening seems to be out of the window.  It's all sounding more and more like a debate in the house.

I think Joe Gregorio makes an interesting point.  If the RSS1.0 folks could stand to walk away from the name RSS then much of the tension disappears.  You can't stop Dave issuing his own 2.0 and trumping him with an RDF 3.0 is just going to escalate things.   Sounds a bit like the middle east doesn't it?

Bill Kearney has already proved that any new standard, even one that Userland doesn't support, can introduced into Radio.

I vote for taking the creative energy in this discussion into a new TLA and a new forum.   The worst that suggests itself to me about this route is having to support two specifications.  But isn't that the case already with RSS1.0?