<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
	<meta http-equiv="Expires" content="Mon, 01 Jan 1990 01:00:00 GMT" />
	<meta name="generator" content="Squib/0.4.0.282" />
	<meta name="author" content="Matt Mower" />
	<meta name="keywords" content="matt mower,london,paoga,squib" />
	<meta name="description" content="Curiouser and Curiouser is the weblog of Matt Mower a London based technical marketing manager for software company PAOGA. In his spare time Matt Mower enjoyes developing software applications including this weblog application Squib." />
	<title>Curiouser and Curiouser!</title>
	<link href="http://matt.blogs.it/rss.xml" rel="alternate" title="RSS" type="application/rss+xml" />
<link href="http://matt.blogs.it/themes/fragen3.14/styles/theme_candc.css" media="screen" rel="stylesheet" type="text/css" />

</head>
<body>
<div id="page">
<div id="banner">
    <h1>Curiouser and Curiouser!</h1>
    <em>'Where shall I begin, please your Majesty?' He asked. 'Begin at the beginning,'
the King said, very gravely, 'and go on till you come to the end: then stop.'</em>
</div>
<div id="nav">
    
<div class="box" id="box_about">
<p><strong>About</strong></p>

<p>Wherein Matt Mower (aka rubymatt on FreeNode) rambles about technology, the love of a good MacTop, ruby coding, rails, topics, knowledge management and learning, and politics.</p>
</div>


    
<div class="box" id="box_navigation">
<p><strong>Navigation</strong></p>

<ul>
<li><a href="http://matt.blogs.it/">Home</a></li>
<li><a href="http://matt.blogs.it/all_posts.html">All Posts by Title</a></li>
<li><a href="http://matt.blogs.it/all_archives.html">Monthly Archives</a></li>
<li><a href="http://matt.blogs.it/topics/index.html">Topics</a></li>
</ul>
</div>


    
    
<div class="box" id="box_blogroll">
<strong>Blogroll</strong><ul class="blogroll"><li><a class="orangeButton" href="http://www.tapestrycomics.com/dilbert.xml">XML</a> <a href="http://www.dilbert.com/">Dilbert</a></li>
<li><a class="orangeButton" href="http://www.tapestrycomics.com/getfuzzy.xml">XML</a> <a href="http://www.comics.com//comics/getfuzzy/">Get Fuzzy</a></li>
<li><a class="orangeButton" href="http://www.tapestrycomics.com/liberty.xml">XML</a> <a href="http://www.comics.com/creators/liberty/">Liberty Meadows</a></li>
<li><a class="orangeButton" href="http://www.phoenyx.net/feeds/comics/hedge.rdf">XML</a> <a href="http://www.comics.com/comics/hedge/">Over the Hedge</a></li>
<li><a class="orangeButton" href="http://www.tapestrycomics.com/peanuts.xml">XML</a> <a href="http://www.comics.com//comics/peanuts/">Peanuts</a></li>
<li><a class="orangeButton" href="http://atheos.de/funnies/pvp.rdf">XML</a> <a href="http://www.pvponline.com/">PvP Online</a></li>
<li><a class="orangeButton" href="http://rss.xiffy.nl/xml.php?channel=391">XML</a> <a href="http://www.userfriendly.org/">User Friendly the Comic Strip. by Illiad</a></li>
<li><a class="orangeButton" href="http://www.tapestrycomics.com/wizardofid.xml">XML</a> <a href="http://www.comics.com/creators/wizardofid/">Wizard of Id</a></li>
<li><a class="orangeButton" href="http://matt.blogs.it/rss.xml ">XML</a> <a href="http://matt.blogs.it/">Curiouser and Curiouser!</a></li>
<li><a class="orangeButton" href="http://www.pubsub.com/site_stats_feed.php?site=matt.blogs.it">XML</a> <a href="http://www.pubsub.com/linkcounts.php">PubSub PubStats for matt.blogs.it</a></li>
<li><a class="orangeButton" href="http://www.technorati.com/watchlists/rss.html?wid=2122">XML</a> <a href="http://www.technorati.com/search/matt.blogs.it">Technorati Search for: Curiouser and curiouser!</a></li>
<li><a class="orangeButton" href="http://www.terryfrazier.com/weblog/rss.xml">XML</a> <a href="http://www.terryfrazier.com/weblog/index">b.cognosco</a></li>
<li><a class="orangeButton" href="http://www.bethlet.net/atom.xml">XML</a> <a href="http://www.bethlet.net/">bethlet.net</a></li>
<li><a class="orangeButton" href="http://del.icio.us/rss/devzero/osx">XML</a> <a href="http://del.icio.us/devzero/osx">del.icio.us/devzero/osx</a></li>
<li><a class="orangeButton" href="http://del.icio.us/rss/tag/osx">XML</a> <a href="http://del.icio.us/tag/osx">del.icio.us/tag/osx</a></li>
<li><a class="orangeButton" href="http://weblog.infoworld.com/foster/rss.xml">XML</a> <a href="http://weblog.infoworld.com/foster/">Ed Foster's Radio Weblog</a></li>
<li><a class="orangeButton" href="http://blog.grahamsadd.com/atom.xml">XML</a> <a href="http://blog.grahamsadd.com/">Graham Sadd's Weblog</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/letTheGoodTimesRollByGuyKawasaki">XML</a> <a href="http://blog.guykawasaki.com/">Let the Good Times Roll by Guy Kawasaki</a></li>
<li><a class="orangeButton" href="http://blog.mathemagenic.com/rss.xml">XML</a> <a href="http://blog.mathemagenic.com/">Mathemagenic</a></li>
<li><a class="orangeButton" href="http://maxblumberg.typepad.com/dailymusings/atom.xml">XML</a> <a href="http://maxblumberg.typepad.com/dailymusings/">Max Blumberg Positioning Game</a></li>
<li><a class="orangeButton" href="http://www.drmartinhall.com/index.rdf">XML</a> <a href="http://www.drmartinhall.com/">Minessence -- Doc Martin's Musings</a></li>
<li><a class="orangeButton" href="http://theobvious.typepad.com/blog/atom.xml">XML</a> <a href="http://theobvious.typepad.com/blog/">The Obvious?</a></li>
<li><a class="orangeButton" href="http://onlyagame.typepad.com/only_a_game/atom.xml">XML</a> <a href="http://onlyagame.typepad.com/only_a_game/">Only a Game</a></li>
<li><a class="orangeButton" href="http://paolo.evectors.it/rss.xml">XML</a> <a href="http://paolo.evectors.it/">Paolo Valdemarin: Paolo's Weblog</a></li>
<li><a class="orangeButton" href="http://bash.org/xml/">XML</a> <a href="http://www.bash.org">QDB: Quote Database</a></li>
<li><a class="orangeButton" href="http://ross.typepad.com/blog/index.rdf">XML</a> <a href="http://ross.typepad.com/blog/">Ross Mayfield's Weblog</a></li>
<li><a class="orangeButton" href="http://www.scripting.com/rss.xml">XML</a> <a href="http://www.scripting.com/">Scripting News</a></li>
<li><a class="orangeButton" href="http://www.myelin.co.nz/post/rss.xml">XML</a> <a href="http://www.myelin.co.nz/post/">Second p0st</a></li>
<li><a class="orangeButton" href="http://www.synesthesia.co.uk/blog/feed/rss2/">XML</a> <a href="http://www.synesthesia.co.uk/blog">Synesthesia</a></li>
<li><a class="orangeButton" href="http://the.taoofmac.com/space/RecentChanges?filter=blog&amp;amp;format=rss">XML</a> <a href="http://the.taoofmac.com/space">The Tao of Mac</a></li>
<li><a class="orangeButton" href="http://anjo.blogs.com/metis/index.rdf">XML</a> <a href="http://anjo.blogs.com/metis/">Anjo Anjewierden</a></li>
<li><a class="orangeButton" href="http://www.beyondbullets.com/index.rdf">XML</a> <a href="http://www.beyondbullets.com/">beyond bullets</a></li>
<li><a class="orangeButton" href="http://bps-research-digest.blogspot.com/atom.xml">XML</a> <a href="http://bps-research-digest.blogspot.com">BPS Research Digest</a></li>
<li><a class="orangeButton" href="http://chocnvodka.blogware.com/blog/index.xml">XML</a> <a href="http://chocnvodka.blogware.com/blog">Chocolate and Vodka</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/Corporatebloggingblog">XML</a> <a href="http://www.corporateblogging.info/">CorporateBloggingBlog</a></li>
<li><a class="orangeButton" href="http://del.icio.us/rss/tag/lifehacks">XML</a> <a href="http://del.icio.us/tag/lifehacks">del.icio.us/tag/lifehacks</a></li>
<li><a class="orangeButton" href="http://www.firstadopter.com/index.rdf">XML</a> <a href="http://www.firstadopter.com/">FirstAdopter.com</a></li>
<li><a class="orangeButton" href="http://homepage.mac.com/dave_rogers/news.rss">XML</a> <a href="http://homepage.mac.com/dave_rogers/">Groundhog Day</a></li>
<li><a class="orangeButton" href="http://cgi.pbs.org/cgi-registry/cringely/cringelyrdf.pl">XML</a> <a href="http://www.pbs.org/cringely/">I, Cringely @ PBS.org</a></li>
<li><a class="orangeButton" href="http://marktsinfoblog.blogspot.com/atom.xml">XML</a> <a href="http://marktsinfoblog.blogspot.com">Mark T's information blog</a></li>
<li><a class="orangeButton" href="http://maxblumberg.typepad.com/maxwellbeing/index.rdf">XML</a> <a href="http://maxblumberg.typepad.com/maxwellbeing/">MaxWellBeing</a></li>
<li><a class="orangeButton" href="http://dev.metavalues.com/metavalues/timeline?daysback=90&amp;amp;max=50&amp;amp;wiki=on&amp;amp;ticket=on&amp;amp;changeset=on&amp;amp;milestone=on&amp;amp;format=rss">XML</a> <a href="http://bidwell.textdrive.com:9009/metavalues/timeline">MetaValues: Timeline</a></li>
<li><a class="orangeButton" href="http://blog.monkeymethods.org/atom.xml">XML</a> <a href="http://blog.monkeymethods.org/">monkey methods</a></li>
<li><a class="orangeButton" href="http://googleblog.blogspot.com/atom.xml">XML</a> <a href="http://googleblog.blogspot.com">Official Google Blog</a></li>
<li><a class="orangeButton" href="http://presentationzen.blogs.com/presentationzen/atom.xml">XML</a> <a href="http://presentationzen.blogs.com/presentationzen/">Presentation Zen</a></li>
<li><a class="orangeButton" href="http://simon.incutio.com/syndicate/rss1.0">XML</a> <a href="http://simon.incutio.com/">Simon Willison's Weblog</a></li>
<li><a class="orangeButton" href="http://www.unstruct.org/wp-rdf.php">XML</a> <a href="http://www.unstruct.org">unstruct.org</a></li>
<li><a class="orangeButton" href="http://www.wingedpig.com/index.rdf">XML</a> <a href="http://www.wingedpig.com/">wingedpig.com - Mark Fletcher's Blog</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/Wonderland">XML</a> <a href="http://crystaltips.typepad.com/wonderland/">Wonderland</a></li>
<li><a class="orangeButton" href="http://psychcentral.com/blog/feed/">XML</a> <a href="http://psychcentral.com/blog">World of Psychology</a></li>
<li><a class="orangeButton" href="http://www.slash7.com/xml/rss/feed.xml">XML</a> <a href="http://www.slash7.com/">(24)slash7</a></li>
<li><a class="orangeButton" href="http://www.artima.com/rubycs/feeds/rubycs.rss">XML</a> <a href="http://www.artima.com/">Articles published in Ruby Code &amp; Style</a></li>
<li><a class="orangeButton" href="http://www.chadfowler.com/index.cgi?rss">XML</a> <a href="http://www.chadfowler.com/index.cgi">ChadFowler.com</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/curthibbs">XML</a> <a href="http://blog.curthibbs.us/articles">Curt's Comments</a></li>
<li><a class="orangeButton" href="http://eigenclass.org/hiki.rb?c=rss;tags=blog">XML</a> <a href="http://eigenclass.org/hiki.rb?c=recent">Eigenclass (blog)</a></li>
<li><a class="orangeButton" href="http://www.livejournal.com/users/drbrain/data/rss">XML</a> <a href="http://www.livejournal.com/users/drbrain/">Eric Hodel</a></li>
<li><a class="orangeButton" href="http://tomcopeland.blogs.com/juniordeveloper/rss.xml">XML</a> <a href="http://tomcopeland.blogs.com/juniordeveloper/">Junior developer</a></li>
<li><a class="orangeButton" href="http://www.koziarski.net/feed/atom/">XML</a> <a href="http://www.koziarski.net">Koz Speaks</a></li>
<li><a class="orangeButton" href="http://www.loudthinking.com/index.rdf">XML</a> <a href="http://www.loudthinking.com/">Loud Thinking</a></li>
<li><a class="orangeButton" href="http://www.mad4milk.net/feeds/tag/moo.fx/weblog">XML</a> <a href="http://www.mad4milk.net/tag/weblog/moo.fx">mad4milk feed for tag moo.fx in weblog section</a></li>
<li><a class="orangeButton" href="http://www.magpiebrain.com/index_full.xml">XML</a> <a href="http://www.magpiebrain.com/">magpiebrain</a></li>
<li><a class="orangeButton" href="http://mir.aculo.us/xml/rss/feed.xml">XML</a> <a href="http://mir.aculo.us/articles">mir.aculo.us</a></li>
<li><a class="orangeButton" href="http://jroller.org/rss/obie">XML</a> <a href="http://jroller.com/page/obie">Obie Fernandez</a></li>
<li><a class="orangeButton" href="http://outside-thoughts.octopod.info/xml/atom/feed.xml">XML</a> <a href="http://outside-thoughts.octopod.info/">Octoblog</a></li>
<li><a class="orangeButton" href="http://blog.zenspider.com/index.rdf">XML</a> <a href="http://blog.zenspider.com/">Polishing Ruby</a></li>
<li><a class="orangeButton" href="http://blogs.pragprog.com/cgi-bin/pragdave.cgi/index.rss">XML</a> <a href="http://blogs.pragprog.com/cgi-bin/pragdave.cgi">PragDave</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/projectionist">XML</a> <a href="http://project.ioni.st/">Projectionist</a></li>
<li><a class="orangeButton" href="http://feeds.feedburner.com/raganwald">XML</a> <a href="http://www.braithwaite-lee.com/weblog/">Raganwald</a></li>
<li><a class="orangeButton" href="http://railsexpress.de/blog/xml/rss20/feed.xml">XML</a> <a href="http://railsexpress.de/blog/">RailsExpress.blog</a></li>
<li><a class="orangeButton" href="http://onestepback.org/gemwatch.rss">XML</a> <a href="">Recent Gems</a></li>
<li><a class="orangeButton" href="http://redhanded.hobix.com/index.xml">XML</a> <a href="http://redhanded.hobix.com">RedHanded</a></li>
<li><a class="orangeButton" href="http://weblog.rubyonrails.com/feed/rss2/">XML</a> <a href="http://weblog.rubyonrails.com/">Riding Rails</a></li>
<li><a class="orangeButton" href="http://rubyweeklynews.org/index.xml">XML</a> <a href="http://www.rubyweeklynews.org">Ruby Weekly News</a></li>
<li><a class="orangeButton" href="http://blog.xeraph.org/feed/rss2/">XML</a> <a href="http://blog.xeraph.org">Slave To The Machine</a></li>
<li><a class="orangeButton" href="http://split-s.blogspot.com/atom.xml">XML</a> <a href="http://split-s.blogspot.com">split-s</a></li>
<li><a class="orangeButton" href="http://techno-weenie.net/blog/?rss=1">XML</a> <a href="http://techno-weenie.net/blog/">techno weenie</a></li>
<li><a class="orangeButton" href="http://tech.rufy.com/feed/rss2/">XML</a> <a href="http://tech.rufy.com">Technoblog</a></li>
<li><a class="orangeButton" href="http://jamis.jamisbuck.org/blog.cgi/index.rss">XML</a> <a href="http://jamis.jamisbuck.org/">the { buckblogs :here }</a></li>
<li><a class="orangeButton" href="http://onestepback.org/index.cgi/index.rss">XML</a> <a href="http://onestepback.org/index.cgi">{ | one, step, back | }</a></li>
<li><a class="orangeButton" href="http://habtm.com/xml/atom/feed.xml">XML</a> <a href="http://habtm.com/">~:caboose</a></li>
<li><a class="orangeButton" href="http://www.decafbad.com/atom.xml">XML</a> <a href="http://www.decafbad.com/">0xDECAFBAD</a></li>
<li><a class="orangeButton" href="http://www.alistapart.com/rss.xml">XML</a> <a href="http://www.alistapart.com/">A List Apart</a></li>
<li><a class="orangeButton" href="http://www.ajaxian.com/index.xml">XML</a> <a href="http://www.ajaxian.com/">Ajaxian</a></li>
<li><a class="orangeButton" href="http://www.backpackit.com/weblog/index.xml">XML</a> <a href="http://backpackit.com/weblog/">Backpack Weblog</a></li>
<li><a class="orangeButton" href="http://blog.monstuff.com/index.xml">XML</a> <a href="http://blog.monstuff.com/">Curiosity is bliss</a></li>
<li><a class="orangeButton" href="http://homepages.ihug.com.au/~naseby/rss.xml">XML</a> <a href="http://homepages.ihug.com.au/~naseby/">David Naseby's World</a></li>
<li><a class="orangeButton" href="http://www.docuverse.com/blog/donpark/rss.xml">XML</a> <a href="http://www.docuverse.com/blog/donpark/">Don Park's Daily Habit</a></li>
<li><a class="orangeButton" href="http://epeus.blogspot.com/atom.xml">XML</a> <a href="http://epeus.blogspot.com">Epeus' epigone</a></li>
<li><a class="orangeButton" href="http://dev.r.tucows.com/blog/index.xml">XML</a> <a href="http://farm.tucows.com/blog">The Farm: The Tucows Developers' Hangout</a></li>
<li><a class="orangeButton" href="http://grahamglass.blogs.com/main/atom.xml">XML</a> <a href="http://grahamglass.blogs.com/main/">Graham Glass, etc.</a></li>
<li><a class="orangeButton" href="http://haoli.dnsalias.com/index.xml">XML</a> <a href="http://haoli.dnsalias.com">h a o l i</a></li>
<li><a class="orangeButton" href="http://hypermetrics.com:3000/xml/rss/feed.xml">XML</a> <a href="http://hypermetrics.com:3000/">Hal-lucinations</a></li>
<li><a class="orangeButton" href="http://www.joelonsoftware.com/rss.xml">XML</a> <a href="http://www.joelonsoftware.com">Joel on Software</a></li>
<li><a class="orangeButton" href="http://weblog.infoworld.com/udell/rss.xml">XML</a> <a href="http://weblog.infoworld.com/udell/">Jon's Radio</a></li>
<li><a class="orangeButton" href="http://martinfowler.com/bliki/bliki.rss">XML</a> <a href="http://martinfowler.com/bliki">Martin Fowler's Bliki</a></li>
<li><a class="orangeButton" href="http://minimsft.blogspot.com/atom.xml">XML</a> <a href="http://minimsft.blogspot.com">Mini-Microsoft</a></li>
<li><a class="orangeButton" href="http://www.redhillconsulting.com.au/blogs/simon/index.xml">XML</a> <a href="http://www.redhillconsulting.com.au/blogs/simon/">My hovercraft is full of eels</a></li>
<li><a class="orangeButton" href="http://blogs.osafoundation.org/news/index.xml">XML</a> <a href="http://www.osafoundation.org/">OSAF News</a></li>
<li><a class="orangeButton" href="http://peterkaminski.com/index.rdf">XML</a> <a href="http://peterkaminski.com/">Peter Kaminski</a></li>
<li><a class="orangeButton" href="http://www.cincomsmalltalk.com/rssBlog/ralph-rss.xml">XML</a> <a href="http://www.cincomsmalltalk.com/userblogs/ralph/blogView">Ralph Johnson - Blog</a></li>
<li><a class="orangeButton" href="http://www.intertwingly.net/blog/index.rss2">XML</a> <a href="http://www.intertwingly.net/blog/">Sam Ruby</a></li>
<li><a class="orangeButton" href="http://37signals.com/svn/index_full.rdf">XML</a> <a href="http://37signals.com/svn/">Signal vs. Noise</a></li>
<li><a class="orangeButton" href="http://mmower.backpackit.com/feed/580c59a670b1f7c852e0901b7976e0e8">XML</a> <a href="http://mmower.backpackit.com/account/start">Backpack</a></li>
<li><a class="orangeButton" href="http://www.choof.org/MT/index.xml">XML</a> <a href="http://www.choof.org/MT/">choof.org</a></li>
<li><a class="orangeButton" href="http://www.idealgovernment.com/index.php/weblog/rss_2.0/">XML</a> <a href="http://www.idealgovernment.com/index.php/weblog/index/">Ideal Government</a></li>
<li><a class="orangeButton" href="http://www.idcorner.org/wp-rss2.php">XML</a> <a href="http://www.idcorner.org">The Identity Corner</a></li>
<li><a class="orangeButton" href="http://www.identityblog.com/rss.xml">XML</a> <a href="http://www.identityblog.com/">Kim Cameron's Identity Weblog</a></li>
<li><a class="orangeButton" href="http://danielsolove.blogspot.com/atom.xml">XML</a> <a href="http://danielsolove.blogspot.com">The Solove Chronicles</a></li>
<li><a class="orangeButton" href="http://www.technorati.com/watchlists/rss.html?wid=64358">XML</a> <a href="http://www.technorati.com/cosmos/search.html?url=paoga">Technorati Search for: paoga</a></li>
<li><a class="orangeButton" href="http://blogs.sun.com/roller/rss/wizidm">XML</a> <a href="http://blogs.sun.com/roller/page/wizidm">Wizard of IdM</a></li>
</ul>
</div>


    
<div class="box" id="box_syndication">
<strong>Syndication</strong>
<div id="syndication">
<ul>
	<li><a class="orangeButton" href="http://matt.blogs.it/rss.xml">XML</a></li>
	<li><script type="text/javascript">eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%73%65%6c%66%40%6d%61%74%74%6d%6f%77%65%72%2e%63%6f%6d%22%3e%45%6d%61%69%6c%20%4d%65%3c%2f%61%3e%27%29%3b'))</script></li>
</ul>
</div>
</div>


</div>
<div id="wrapper">
	<div id="content">
		<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:ent="http://www.purl.org/NET/ENT/1.0/">
  <channel>
    <title>Curiouser and Curiouser! on k-collector</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic k-collector</description>
    <copyright>Copyright 2006 Matt Mower</copyright>
    <generator>Squib/0.1</generator>
    <managingEditor>self@mattmower.com</managingEditor>
    <webMaster>self@mattmower.com</webMaster>
    <language>en-gb</language>
    <item>
      <title>Testing the k-collector client</title>
      <pubDate>Wed, 07 May 2003 12:59:50 +0100</pubDate>
      <description>&lt;P&gt;Testing the new &lt;FONT color=maroon&gt;k-collector&lt;/FONT&gt; client for Radio.&amp;nbsp; This is a cut down version of liveTopics that works with the &lt;A href="http://k-collector.evectors.it/"&gt;k-collector server&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;The k-collector client, unlike liveTopics, is dynamic and based upon a shared topic roll held on the k-collector server.&amp;nbsp; Compared to liveTopics k-collector is stripped down, however it is also smaller, lighter and more stable.&lt;/P&gt;
&lt;P&gt;I myself am switching over from using liveTopics to using k-collector so that we can test the new server properly.&amp;nbsp; I'm not sure what will happen to the liveTopics client at this point.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001454.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/aggregators.xml" ent:id="aggregators" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/ent-1.0.xml" ent:id="ent-1.0" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/foaf.xml" ent:id="foaf" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/marc-canter.xml" ent:id="marc-canter" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/rss.xml" ent:id="rss" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/rss-2-0.xml" ent:id="rss-2-0" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/topic-mapping.xml" ent:id="topic-mapping" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>More about k-collector</title>
      <pubDate>Wed, 07 May 2003 15:08:52 +0100</pubDate>
      <description>&lt;P&gt;A little bit of background about the k-collector client.&lt;/P&gt;
&lt;P&gt;k-collector client for Radio Userland is really a totally stripped down version of liveTopics.&amp;nbsp; Out go tables of contents, local databases of topics, lots of macros, XFML, XTM and a raft of other stuff i'm like.&lt;/P&gt;
&lt;P&gt;What you end up with is a simple client designed to bootstrap itself from an online cloud of topics.&amp;nbsp; For an example of such a cloud is &lt;A href="http://k-collector.evectors.it/itentdirectory/topicRoll.opml?dir=8"&gt;here&lt;/A&gt;.&amp;nbsp; Topics created on the local system are exported via the RSS feed using &lt;A href="http://www.purl.org/NET/ENT/1.0/"&gt;ENT&lt;/A&gt; and from there appear on the k-collector server.&amp;nbsp; Each k-collector client regularly polls the cloud looking for new topics and makes them available locally.&lt;/P&gt;
&lt;P&gt;It's a nice, simple, dynamic system for publishing using shared topics.&lt;/P&gt;
&lt;P&gt;What k-collector doesn't have most people probably won't miss (especially if they are using a k-collector server) and as a result k-collector is much smaller, lighter and more stable than liveTopics.&amp;nbsp; liveTopics is a complicated application and the combination of Radio &amp; Usertalk don't really support complexity very well.&amp;nbsp; k-collector should suffer from far less problems than it's bigger counterpart.&lt;/P&gt;
&lt;P&gt;More later.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001456.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/buy-music.xml" ent:id="buy-music" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/music.xml" ent:id="music" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/sony.xml" ent:id="sony" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>I'm lazy but that's not the reason</title>
      <pubDate>Mon, 12 May 2003 12:42:47 +0100</pubDate>
      <description>I haven't been posting much over the last week.&amp;nbsp; This is largely because i've been hard at work developing the k-collector client and switching over from liveTopics.&amp;nbsp; That switch is very nearly complete and hopefully from the end of today Paolo and I will be working from the same cloud of topics hosted on our k-collector &lt;A href="http://k-collector.evectors.com/"&gt;demo site&lt;/A&gt;.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001458.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/terry-frazier.xml" ent:id="terry-frazier" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/wiki.xml" ent:id="wiki" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>k-collector goes live</title>
      <pubDate>Tue, 13 May 2003 13:45:29 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://paolo.evectors.it/"&gt;Paolo&lt;/A&gt; and I are now subscribed to a single shared cloud (called &lt;A href="http://k-collector.evectors.it/itentdirectory/topicRoll.opml?dir=140"&gt;WWWW&lt;/A&gt;) of topics using the &lt;A href="http://k-collector.evectors.it/itentdirectory/home?dir=140"&gt;k-collector server&lt;/A&gt; and client for Radio.&lt;/P&gt;
&lt;P&gt;This means that our posts will be aggregated together by k-collector on the basis of the topics we use.&amp;nbsp; The demo interface shows a simple hierarchical view but we have lots of other things planned.&lt;/P&gt;
&lt;P&gt;Another poweful feature of this setup is the shared topic roll.&amp;nbsp; Because we are both subscribed to the WWWW topic roll we use the same topics and any topics we create are automatically made available to other subscribers.&lt;/P&gt;
&lt;P&gt;For example I am creating a topic 'Paolo Valdemarin' to attach to this post.&amp;nbsp; In a little while Paolo's client will automatically have this new topic available for those moments when he wishes to talk about himself!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001459.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/blogging-tools.xml" ent:id="blogging-tools" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/suw-charman.xml" ent:id="suw-charman" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Communal topics and super-blogs</title>
      <pubDate>Tue, 13 May 2003 18:04:02 +0100</pubDate>
      <description>&lt;P&gt;Something we've just got working today (okay &lt;A href="http://simone.blogs.it/english/"&gt;Simone&lt;/A&gt; got it working, but I did a valuable job cheering him on) is one of the final pieces in the k-collector puzzle.&amp;nbsp; The server now sends the client a URL corresponding to each topic in the cloud.&amp;nbsp; This enables the client to create on-the-fly links back to the server referring browsers to a live page about the topic.&lt;/P&gt;
&lt;P&gt;liveTopics had the concept of the table of contents, a local directory of your topics and what posts they related to.&amp;nbsp; All very well in it's way but a far cry from the super-blogs I &lt;A href="http://matt.blogs.it/2002/07/10.html#a193"&gt;wrote about&lt;/A&gt; last July.&amp;nbsp; Specifically it wasn't live (you couldn't do anything with that data) and it wasn't shared, MY topics MY posts, bleugh!&lt;/P&gt;
&lt;P&gt;If you click a topic name on my weblog &lt;EM&gt;now &lt;/EM&gt;you don't get a local page but, instead,&amp;nbsp;the dynamic k-collector page for that topic.&amp;nbsp; At the moment this is an aggregation of all the posts about that topic from anyone subscribing to the cloud.&amp;nbsp; Soon it will be much more.&amp;nbsp; k-collector has become my super blog and pretty soon we aim to have many more people subscribing.&amp;nbsp; We also hope to see other people creating clouds and boostrapping their own topic communities.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001463.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/social-networks.xml" ent:id="social-networks" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/social-software.xml" ent:id="social-software" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Wanna know how it works?</title>
      <pubDate>Tue, 13 May 2003 20:38:08 +0100</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://k-collector.evectors.it/"&gt;K-collector&lt;/A&gt;. Matt has already written about k-collector today &lt;A href="http://matt.blogs.it/2003/05/13.html#a916"&gt;here&lt;/A&gt; and &lt;A href="http://matt.blogs.it/2003/05/13.html#a919"&gt;here&lt;/A&gt;. What can I add? Maybe a little drawing? &lt;IMG src="http://paolo.evectors.it/myImages/entWorkflow3.jpg"&gt; [&lt;A href="http://paolo.evectors.it/"&gt;Paolo Valdemarin: Paolo's Weblog&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Yeah!&amp;nbsp; That's how it works.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001465.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/spam.xml" ent:id="spam" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Call for help:  Cross domain scripting</title>
      <pubDate>Fri, 06 Jun 2003 16:19:34 +0100</pubDate>
      <description>&lt;P&gt;We've run into a problem implementing the &lt;A href="http://www.movabletype.org/"&gt;MovableType&lt;/A&gt; client for &lt;A href="http://wwww.evectors.it/"&gt;k-collector&lt;/A&gt;:&lt;/P&gt;
&lt;P&gt;Our approach has been to bootstrap development by reusing a lot of the Radio client code (moved onto the k-collector server) and having the MT client call that as far as possible.&amp;nbsp; We made some good progress this way however we've hit a snag.&amp;nbsp; When the server side code needs to send information back to MovableType we hit the 'ol Javascript &lt;A href="http://www.mozilla.org/projects/security/components/same-origin.html"&gt;same origin policy&lt;/A&gt; problem.&lt;/P&gt;
&lt;P&gt;What we need is a way for the pages serverd by MovableType to allow the pages from k-collector access to some of their properties but without having to use signed pages (which appears to be a minefield).&amp;nbsp; Since the one should be allowed to trust the other I am hoping there is a way.&amp;nbsp; Is there?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001471.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/spam.xml" ent:id="spam" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Progress on k-collector for MovableType</title>
      <pubDate>Wed, 11 Jun 2003 19:38:17 +0100</pubDate>
      <description>With some much needed help from &lt;A href="http://www.crystalflame.net/"&gt;Richard&lt;/A&gt; work on the &lt;A href="http://wwww.evectors.it/"&gt;k-collector&lt;/A&gt; client for &lt;A href="http://www.movabletype.org/"&gt;MovableType&lt;/A&gt; is proceeding.&amp;nbsp; I won't say smoothly, my &lt;A href="http://www.perl.org/"&gt;perl&lt;/A&gt; is too ancient, and rusty, and MovableType too complex for that, but it is proceeding.&amp;nbsp; We're hoping to invite the first beta testers to get involved sometime next week.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001480.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/meaning-of-life.xml" ent:id="meaning-of-life" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>k-collector DMOZ style</title>
      <pubDate>Thu, 12 Jun 2003 07:34:04 +0100</pubDate>
      <description>&lt;P&gt;Richard Soderberg is &lt;A href="http://www.crystalflame.net/archives/000075.html"&gt;wondering&lt;/A&gt; whether there is utility in linking k-collector with a &lt;A href="http://www.dmoz.org/"&gt;DMOZ&lt;/A&gt; style directory.&amp;nbsp; The principle is that DMOZ editors have already come up with a wide-ranging category hierarchy so let people re-use it.&lt;/P&gt;
&lt;P&gt;I can see this being of benefit to a public k-collector server such as our beta but perhaps of far more limited utility for a company or team using k-collector internally.&lt;/P&gt;
&lt;P&gt;What do people think?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001483.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/blogging-tools.xml" ent:id="blogging-tools" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/conversations.xml" ent:id="conversations" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/david-gurteen.xml" ent:id="david-gurteen" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/euan-semple.xml" ent:id="euan-semple" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/evectors.xml" ent:id="evectors" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge-work.xml" ent:id="knowledge-work" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/lee-bryant.xml" ent:id="lee-bryant" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/london.xml" ent:id="london" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/marc-eisenstadt.xml" ent:id="marc-eisenstadt" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/matt-mower.xml" ent:id="matt-mower" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/paolo-valdemarin.xml" ent:id="paolo-valdemarin" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/phil-wolff.xml" ent:id="phil-wolff" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/social-networks.xml" ent:id="social-networks" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/social-software.xml" ent:id="social-software" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/social-tools-for-enterprises-symposium.xml" ent:id="social-tools-for-enterprises-symposium" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/stowe-boyd.xml" ent:id="stowe-boyd" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector white paper</title>
      <pubDate>Tue, 12 Aug 2003 19:59:12 +0100</pubDate>
      <description>I've spent a big chunk of today writing an email to a suspect in the US.&amp;nbsp; It occurs to me that, as an email, it fails to be concise yet precise.&amp;nbsp; However it would make the basis for a K-Collector white paper and that's a good&amp;nbsp;thing since I have been stuck on that task for a while now.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001541.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/how-to-develop-software.xml" ent:id="how-to-develop-software" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/microsoft-windows.xml" ent:id="microsoft-windows" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector &amp; Bayesian filtering</title>
      <pubDate>Sun, 17 Aug 2003 18:59:05 +0100</pubDate>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="http://www.decafbad.com/blog/geek/bayes_agg_one.phtml"&gt;Issues in using SpamBayes to filter news items&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;Despite a reading &lt;A href="http://www.srijith.net/trinetre/archives/2003/08/11/index.shtml#000373"&gt;an entry by Srijith&lt;/A&gt; discussing Bayes-based classification as unsuitable for use in news aggregators, I tied &lt;A href="http://www.spambayes.org"&gt;SpamBayes&lt;/A&gt; into my &lt;A href="http://www.decafbad.com/viewcvs.cgi/dbagg/"&gt;homebrew news aggregator&lt;/A&gt; and have been trying it out this week. I know Ive been &lt;A href="http://www.decafbad.com/blog/geek/syndicated_whuffie.phtml"&gt;talking about it&lt;/A&gt; for awhile, but procrastination and being busy all round kept me from getting to it. Funny thing is, when I finally got a chance to really check things out, the integration was a snap. Id anticipated a bit of work, but was pleasantly surprised. I doubt that any other aggregator written in Python would have a hard time with it.&lt;/P&gt;
&lt;P&gt;If, that is, anyone else wants to do it. I already knew it wasnt &lt;A href="http://diveintomark.org/archives/2003/07/07/linkdumps_are_like_sex"&gt;magic pixy dust&lt;/A&gt; but I figured it might be worth a try. I will be eating my dogfood for awhile with this, but Im thinking already that whats good for spam might not be so good for news aggregators.&lt;/P&gt;
&lt;P&gt;Srijiths &lt;A href="http://www.srijith.net/trinetre/archives/2003/08/11/index.shtml#000373"&gt;post&lt;/A&gt; mentions some snags in ignoring some of the semantics of a news item, such as whether a word appears in the items title or information about the items source. I dont think that this completely applies to how Im doing classification, since SpamBayes appears to differentiate between words found in email headers and the body itself. When I feed an item to SpamBayes for training and scoring, I represent it as something like an email message, with headers like date, subject, from, and an X-Link header for the link. However, even with this, I think Srijiths got a point when he writes that this method will miss a lot of available clues for classification.&lt;/P&gt;
&lt;P&gt;Unlike Srijiths examples, though, Im not trying to train my aggregator to sift entries into any specific categories. So far, Ive been trying to get it to discriminate between what I really want to read, and what Im not so interested in. So, I figured that something which can learn the difference between spam and normal email could help. But, although its early, Im noticing a few things about the results and Ive had a few things occur to me.&lt;/P&gt;
&lt;P&gt;See, in the case of ham vs spam, I really want all the ham and none of the spam. A method to differentiate between these two should be optimized toward one answer or the other. SpamBayes offers I dont know as a third answer, but its not geared toward anything else in-between. However, in measuring something like interest, inbetween answers are useful. I want all of the interesting stuff, some of the sort-of interesting stuff, and a little of the rest.&lt;/P&gt;
&lt;P&gt;This is also a problem for me in deciding to what I should give a thumbs up and what gets the thumbs down. Even though Ive subscribed to a little over 300 feeds, every item from each of them is somewhat interesting to me. I wouldnt have subscribed to the feed if there wasnt anything of interest there, so Ive already biased the content of what I receive. Some items are more interesting than others, but the difference between them is nowhere near the difference of wanted ham vs unsolicited spam. So, I find myself giving the nod to lots of items, but only turning down a few. SpamBayes would like equal examples of both, if possible.&lt;/P&gt;
&lt;P&gt;Ill still be playing with this for awhile, but I need to look around at other machine learning tech. Im just hacking around, but the important thing is to try to understand the algorithms better and know how they work and why. Bayes is in vogue right now, but as Mark Pilgrim intimated, its not magic. Its just advanced :)&lt;/P&gt;
&lt;P&gt;In the immortal words of &lt;A href="http://www.spidereyeballs.com/os6/set3/small_os6_d3_3596_sm.html"&gt;Mark Jason Dominus&lt;/A&gt;: You cant just make shit up and expect the computer to know what you mean, retardo! &lt;/P&gt;
&lt;P&gt;[&lt;A href="http://www.decafbad.com/blog"&gt;0xDECAFBAD&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Interesting.&amp;nbsp; Within &lt;A href="http://w4.evectors.it/"&gt;k-collector&lt;/A&gt; we already have a method for selecting a level of interest more granular than the feed and that is the topic (and, soon, groups of related topics).&lt;/P&gt;
&lt;P&gt;This allows you to say &lt;EM&gt;&lt;FONT color=maroon&gt;I'm interested in Java&lt;/FONT&gt;&lt;/EM&gt; rather than &lt;EM&gt;&lt;FONT color=maroon&gt;I want to read these 200 blogs where they talk about Java sometimes&lt;/FONT&gt;&lt;/EM&gt;.&amp;nbsp; Then within this view you could start to say &lt;EM&gt;&lt;FONT color=maroon&gt;well, so and so&amp;nbsp;is more interesting than Matt on this topic&lt;/FONT&gt;&lt;/EM&gt;.&amp;nbsp; But again, you are only dealing with the topic at hand.&amp;nbsp; You might still think I'm more interesting about something else even if I struggle for an example!&lt;/P&gt;
&lt;P&gt;We're already looking at interesting things we can do with this approach, maybe Bayesian filtering is something we should be thinking about.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001544.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>When aggregators attack</title>
      <pubDate>Mon, 18 Aug 2003 14:28:23 +0100</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://scriptingnews.userland.com/2003/08/18#wiredOnAggregators"&gt;Comments here&lt;/A&gt; on Wired's &lt;A href="http://www.wired.com/news/infostructure/0,1377,60053,00.html"&gt;article&lt;/A&gt; on news aggregators. [&lt;A href="http://www.scripting.com/"&gt;Scripting News&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The title of the article &amp;nbsp;&lt;FONT color=darkblue&gt;Aggregators Attack Info Overload&lt;/FONT&gt;&amp;nbsp; suggested to me a slightly more in depth piece looking at the value of using RSS and aggregators to communicate and share.&amp;nbsp; In this, I think it fell short.&lt;/P&gt;
&lt;P&gt;I'm also disappointed because it meant that &lt;A href="http://w4.evectors.it/"&gt;K-Collector&lt;/A&gt; didn't get a mention.&amp;nbsp; We may be the new kid on the block but with RSS+ENT I think we're doing something really interesting in this space.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001552.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Bayes makes topics</title>
      <pubDate>Tue, 19 Aug 2003 19:57:08 +0100</pubDate>
      <description>&lt;P&gt;Doing a bit of digging into Bayesian filtering.&amp;nbsp; Although it may have other uses in K-Collector later on, my initial thoughts are using a Bayesian filter to automatically suggest topics for weblog posts via K-Collector client.&amp;nbsp; If it's good enough we might even be able to skip the user having to approve some topics.&lt;/P&gt;
&lt;P&gt;At the moment the client is using a simple keyword stemmer which is effective, up to&amp;nbsp;a point, but suggests a lot of false positives.&amp;nbsp;&amp;nbsp; I'm hoping that a trained Bayesian classifier will do a lot better.&amp;nbsp; Of course this raises the issue of how it gets trained but that is a bridge of a very different colour.&lt;/P&gt;
&lt;P&gt;Some resources I have come across:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://www.paulgraham.com/spam.html"&gt;A Plan for Spam &lt;Paul Graham&gt;&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://sourceforge.net/docman/display_doc.php?docid=13334&amp;group_id=63137"&gt;Project POPFile&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001559.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>The whole is greater than the sum of it's parts</title>
      <pubDate>Wed, 20 Aug 2003 10:01:18 +0100</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://weblog.halmacomber.com/2003_08_17_archive.html#106135017216163658"&gt;Doing My Best Not to Scream&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;&lt;A href="http://weblog.halmacomber.com/2003_08_17_archive.html#106126040209696149"&gt;Yesterday's posting&lt;/A&gt; hit a nerve. (Seems at least three people agree with me!) What might we be able to accomplish on our projects if we put our attention on learning to increase the relatedness of people on our projects rather than studying for the &lt;A href="http://www.pmi.org/"&gt;PMI&lt;/A&gt; certification exam? Does anyone really think that doing better work breakdown structures will make our projects successful? No one. That's what I thought. How about learning to repair trust between two important team members? Now that would make a difference. Not the role of a project manager, you say? Then who's role is it?&lt;/P&gt;
&lt;P&gt;It's time we stopped acting like good technical wisdom is what makes for good project management. It doesn't. Likewise, accountability, authority, and responsibility (someone needs to explain the difference between accountability and responsibility for me) don't make a project manager. Let's try care, guidance, attention, listening, and openness. Now we're getting somewhere!&lt;/P&gt;
&lt;P&gt;I recognize my mood in writing this is somewhat impertinent. Frankly, I'm doing my best not to scream. (It would wake the dogs.) We must shift our conversation about project management from the things we do to the people we do it with. Only when we put people at the center of projects can we have the fantastic environments that projects are for our clients, for us and our team mates, and our companies.&lt;BR&gt;[&lt;A href="http://weblog.halmacomber.com/"&gt;Reforming Project Management&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I missed the original post in my aggregator but agree strongly with what is said here.&amp;nbsp; One of the key things I have learned over the last year or so is that it is people that do valuable things and they don't do them on their own.
&lt;P&gt;To take my own example, my productivity has soared since I started collaborating with &lt;A href="http://paolo.evectors.it/"&gt;Paolo&lt;/A&gt; and &lt;A href="http://simone.blogs.it/"&gt;Simone&lt;/A&gt; of evectors.&amp;nbsp; It's not our technical knowledge that has delivered this, it's the new interactions that we can provoke &amp; sustain&amp;nbsp;in each other.&amp;nbsp; The whole definitely is greater than the sum of it's parts.
&lt;P&gt;We're looking at ways in which &lt;A href="k-collector"&gt;K-Collector&lt;/A&gt; can help to connect people together in organsiations because we think it's a powerful tool.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001567.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Aggregator work</title>
      <pubDate>Wed, 27 Aug 2003 14:24:51 +0100</pubDate>
      <description>&lt;P&gt;We're rewriting part of the K-Collector aggregator using a new design.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001593.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Many heads in jars</title>
      <pubDate>Wed, 27 Aug 2003 20:32:32 +0100</pubDate>
      <description>&lt;P&gt;It's an amazing group of &lt;A href="http://k-collector.evectors.it/itentdirectory/wwwwclassification?dir=142"&gt;people&lt;/A&gt; K-Collector has acquired in just a few short months.&amp;nbsp; I wish I knew half these people or at least who they were!&lt;/P&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Adam Curry,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Adriaan Tijsseling,&lt;/SPAN&gt;&lt;SPAN&gt;Adrian Scott,&lt;/SPAN&gt;&lt;SPAN&gt;Alan Cooper,&lt;/SPAN&gt;&lt;SPAN&gt;Alf Eaton,&lt;/SPAN&gt;&lt;SPAN&gt;Alison Fish,&lt;/SPAN&gt;&lt;SPAN&gt;Andre Durand,&lt;/SPAN&gt;&lt;SPAN&gt;Barry Diller,&lt;/SPAN&gt;&lt;SPAN&gt;Ben Hammersley,&lt;/SPAN&gt;&lt;SPAN&gt;Ben Trott,&lt;/SPAN&gt;&lt;SPAN&gt;Beppe Caravita,&lt;/SPAN&gt;&lt;SPAN&gt;Bill Kearney,&lt;/SPAN&gt;&lt;SPAN&gt;Brewster Kahle,&lt;/SPAN&gt;&lt;SPAN&gt;Britt Blaser,&lt;/SPAN&gt;&lt;SPAN&gt;Cesare Lamanna,&lt;/SPAN&gt;&lt;SPAN&gt;Chris Pirillo,&lt;/SPAN&gt;&lt;SPAN&gt;Chuck Lawson,&lt;/SPAN&gt;&lt;SPAN&gt;Clay Shirky,&lt;/SPAN&gt;&lt;SPAN&gt;Cory Doctorow,&lt;/SPAN&gt;&lt;SPAN&gt;Dan Brickley,&lt;/SPAN&gt;&lt;SPAN&gt;Dan Gillmor,&lt;/SPAN&gt;&lt;SPAN&gt;danah boyd,&lt;/SPAN&gt;&lt;SPAN&gt;Danny Ayers,&lt;/SPAN&gt;&lt;SPAN&gt;Danny Goodman,D&lt;/SPAN&gt;&lt;SPAN&gt;ave Jacobs,&lt;/SPAN&gt;&lt;SPAN&gt;Dave Snowden,&lt;/SPAN&gt;&lt;SPAN&gt;Dave Winer,&lt;/SPAN&gt;&lt;SPAN&gt;David Galbraith,&lt;/SPAN&gt;&lt;SPAN&gt;David Gurteen,&lt;/SPAN&gt;&lt;SPAN&gt;David Isenberg,&lt;/SPAN&gt;&lt;SPAN&gt;David Sifry,&lt;/SPAN&gt;&lt;SPAN&gt;Dina Mehta,&lt;/SPAN&gt;&lt;SPAN&gt;Doc Searls,&lt;/SPAN&gt;&lt;SPAN&gt;Don Hopkins,&lt;/SPAN&gt;&lt;SPAN&gt;Don Norman,&lt;/SPAN&gt;&lt;SPAN&gt;Don Park,&lt;/SPAN&gt;&lt;SPAN&gt;Doug Baron,&lt;/SPAN&gt;&lt;SPAN&gt;Drummond Reed,D&lt;/SPAN&gt;&lt;SPAN&gt;uncan Wilcox,E&lt;/SPAN&gt;&lt;SPAN&gt;dd Dumbill,&lt;/SPAN&gt;&lt;SPAN&gt;Eric Norlin,&lt;/SPAN&gt;&lt;SPAN&gt;Eugene Kim,&lt;/SPAN&gt;&lt;SPAN&gt;Evan Williams,&lt;/SPAN&gt;&lt;SPAN&gt;Gary Santoro,&lt;/SPAN&gt;&lt;SPAN&gt;Giuseppe Granieri,&lt;/SPAN&gt;&lt;SPAN&gt;Greg Elin,&lt;/SPAN&gt;&lt;SPAN&gt;Harold Gilchrist,&lt;/SPAN&gt;&lt;SPAN&gt;Howard Dean,&lt;/SPAN&gt;&lt;SPAN&gt;Howard Rheingold,&lt;/SPAN&gt;&lt;SPAN&gt;Jason DeFillippo,&lt;/SPAN&gt;&lt;SPAN&gt;Jason Fried,&lt;/SPAN&gt;&lt;SPAN&gt;Jason Lefkowitz,&lt;/SPAN&gt;&lt;SPAN&gt;Jay Feinberg,&lt;/SPAN&gt;&lt;SPAN&gt;Jim McGee,&lt;/SPAN&gt;&lt;SPAN&gt;John Bransford,&lt;/SPAN&gt;&lt;SPAN&gt;John Doerr,&lt;/SPAN&gt;&lt;SPAN&gt;John Hagel,&lt;/SPAN&gt;&lt;SPAN&gt;John Norris,&lt;/SPAN&gt;&lt;SPAN&gt;John Robb,&lt;/SPAN&gt;&lt;SPAN&gt;John Seely Brown,&lt;/SPAN&gt;&lt;SPAN&gt;Joi ito,&lt;/SPAN&gt;&lt;SPAN&gt;Jon Lebkowsky,&lt;/SPAN&gt;&lt;SPAN&gt;Jon Udell,&lt;/SPAN&gt;&lt;SPAN&gt;Jonathan Abrams,&lt;/SPAN&gt;&lt;SPAN&gt;Jonathan Peterson,&lt;/SPAN&gt;&lt;SPAN&gt;Justin Hall,&lt;/SPAN&gt;&lt;SPAN&gt;Karlin Lillington,&lt;/SPAN&gt;&lt;SPAN&gt;Kevin Marks,&lt;/SPAN&gt;&lt;SPAN&gt;Kevin Werbach,&lt;/SPAN&gt;&lt;SPAN&gt;Kim Polese,&lt;/SPAN&gt;&lt;SPAN&gt;Lawrence Lessig,&lt;/SPAN&gt;&lt;SPAN&gt;Leigh Dodds,&lt;/SPAN&gt;&lt;SPAN&gt;Libby Miller,&lt;/SPAN&gt;&lt;SPAN&gt;Lisa Rein,&lt;/SPAN&gt;&lt;SPAN&gt;Liz Lawley,&lt;/SPAN&gt;&lt;SPAN&gt;LockerGnome,&lt;/SPAN&gt;&lt;SPAN&gt;Marc Barrot,&lt;/SPAN&gt;&lt;SPAN&gt;Mark Carey,&lt;/SPAN&gt;&lt;SPAN&gt;Mark Pilgrim,&lt;/SPAN&gt;&lt;SPAN&gt;Matt Webb,&lt;/SPAN&gt;&lt;SPAN&gt;Meg Hourihan,&lt;/SPAN&gt;&lt;SPAN&gt;Micah Alpern,&lt;/SPAN&gt;&lt;SPAN&gt;Michael Gartenberg,&lt;/SPAN&gt;&lt;SPAN&gt;Mitch Ratcliffe,&lt;/SPAN&gt;&lt;SPAN&gt;Morten Fredericksen,&lt;/SPAN&gt;&lt;SPAN&gt;Nat Friedman,&lt;/SPAN&gt;&lt;SPAN&gt;Neo,&lt;/SPAN&gt;&lt;SPAN&gt;Nick Gaydos,&lt;/SPAN&gt;&lt;SPAN&gt;Nikolaj Nyholm,&lt;/SPAN&gt;&lt;SPAN&gt;Ole Eichhorn,&lt;/SPAN&gt;&lt;SPAN&gt;Paolo Valdemarin,&lt;/SPAN&gt;&lt;SPAN&gt;Paul Boutin,&lt;/SPAN&gt;&lt;SPAN&gt;Peter Kaminsky,&lt;/SPAN&gt;&lt;SPAN&gt;Phil Pearson,&lt;/SPAN&gt;&lt;SPAN&gt;Phil Wolff,&lt;/SPAN&gt;&lt;SPAN&gt;Pierre Omidyar,&lt;/SPAN&gt;&lt;SPAN&gt;Ray Ozzie,&lt;/SPAN&gt;&lt;SPAN&gt;Reid Hoffman,&lt;/SPAN&gt;&lt;SPAN&gt;Richard MacManus,&lt;/SPAN&gt;&lt;SPAN&gt;Rob Adams,&lt;/SPAN&gt;&lt;SPAN&gt;Robb Beal,&lt;/SPAN&gt;&lt;SPAN&gt;Robert Scoble,&lt;/SPAN&gt;&lt;SPAN&gt;Ross Mayfield,&lt;/SPAN&gt;&lt;SPAN&gt;Russell Beattie,&lt;/SPAN&gt;&lt;SPAN&gt;Sam Ruby,&lt;/SPAN&gt;&lt;SPAN&gt;Scott Adams,&lt;/SPAN&gt;&lt;SPAN&gt;Scott Adans,&lt;/SPAN&gt;&lt;SPAN&gt;Scott Heiferman,&lt;/SPAN&gt;&lt;SPAN&gt;Scott Johnson,&lt;/SPAN&gt;&lt;SPAN&gt;Scott Mace,&lt;/SPAN&gt;&lt;SPAN&gt;Seb Paquet,&lt;/SPAN&gt;&lt;SPAN&gt;Shelly Powers,&lt;/SPAN&gt;&lt;SPAN&gt;Simone Bettini,&lt;/SPAN&gt;&lt;SPAN&gt;Sjoerd Visscher,&lt;/SPAN&gt;&lt;SPAN&gt;Steve Yost,&lt;/SPAN&gt;&lt;SPAN&gt;Thomas Burg,&lt;/SPAN&gt;&lt;SPAN&gt;Thomas Mygdal-Madsen,&lt;/SPAN&gt;&lt;SPAN&gt;Tim O'Reilly,&lt;/SPAN&gt;&lt;SPAN&gt;Ward Cunningham,&lt;/SPAN&gt;&lt;SPAN&gt;Will Wright,&lt;/SPAN&gt;&lt;SPAN&gt;Xeni Jardin,&lt;/SPAN&gt;&lt;SPAN&gt;Zack Lynch&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001599.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>A journey with Phil</title>
      <pubDate>Tue, 23 Sep 2003 20:33:41 +0100</pubDate>
      <description>So, I don't have the patience to do a complete re-write but here is a recap of some of the highlights of my &lt;a href="http://dijest.com/aka/2003/09/22.html#a2623"&gt;conversation with Phil&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
Obviously, since we were using it, we talked about Skype (i'm
pronouncing it 'sky'-'p').  I guess I'm both impressed and
frustrated in equal measure.  Most of the time (we were talking
for hours, god knows what state Phil was in the next day) the quality
was good, but it did crap out on us quite a bit.  It definitely
needs a cell-phone style signal meter.  We even mused that, since
Skype knows your address it could tap into the &lt;a href="http://www.internettrafficreport.com/main.htm"&gt;Internet Weather Report&lt;/a&gt; to tell you what sort of call to expect!&lt;br&gt;
&lt;br&gt;
We talked about the possible applications for a good, free, VOIP client
and there are many.  One in particular appeals to me and that is
seeing Skype support bundled with the software I buy.  What I want
is that when I need to contact a vendor I can press a &lt;span style="font-style: italic;"&gt;Skype me&lt;/span&gt;
button.  This lets them know that a CSA or Techie should get in
touch with me.  It's convenient for me because it means that I
will be at the computer when they call.  The win for the vendor is
that they only need to call when they see me online and the cost is
significantly cheaper than how they do this today.  (As an
example, doing webcallback via Netcall means the vendor has to pay for
2 PSTN calls.  One from the Netcall server to the CSA and one from
the Netcall server to the customer.  Then they have to pay Netcall
to manage it all as well.  Gets expensive).&lt;br&gt;
&lt;br&gt;
Phil and I are both lefties so we rapped about the war, Bush and the
Dean campaign.  It's incredibly for a guy that seemed such an
outside 12 months ago that if you search for Howard on Google, &lt;a href="http://www.deanforamerica.com/"&gt;Dean for America&lt;/a&gt;
is no. #2.   What is particularly impressive is the way the
Dean campaign have leveraged their digital savvy into on the ground
support.  Would that any UK politician had the same nouse.  I
can't imagine being so impressed with any MP I have come across that
i'd actually go talk about them.  &lt;span style="background-color: rgb(255, 255, 255); color: rgb(153, 0, 0);"&gt;I would love to feel differently though!&lt;br&gt;
&lt;span style="color: rgb(51, 0, 51);"&gt;&lt;br&gt;
I gave Phil a quick head's up on the work we are doing with &lt;a href="http://w4.evectors.it/"&gt;K-Collector/W4&lt;/a&gt;, he hadn't seen it since &lt;a href="http://blogtalk.net/"&gt;BlogTalk&lt;/a&gt; (it seems so long ago now...) and we've put a lot of effort in since then.&amp;nbsp; We also &lt;a href="http://dijest.com/aka/2003/09/22.html#a2623"&gt;talked about what's needed to get corporates into blogging&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
Oh he put me onto &lt;a href="http://www.amazon.co.uk/exec/obidos/ASIN/0451459156/ref=sr_aps_books_1_2/026-1765779-1917222"&gt;Ruled Brittania&lt;/a&gt;
(by Harry Turtledove) which is an alternate reality novel set in an
England conquered by Spain.&amp;nbsp; I'm a complete sucker for this stuff
so that went straight onto my &lt;a href="http://www.amazon.co.uk/exec/obidos/registry/2VBDDIPM7ZWQP/ref=wl_s_3/026-8728199-5122817"&gt;wishlist&lt;/a&gt;.&amp;nbsp; In return I suggested &lt;a href="http://www.amazon.co.uk/exec/obidos/ASIN/0099263815/ref=sr_aps_books_1_1/026-1765779-1917222"&gt;Fatherland&lt;/a&gt; (by Robert Harris) a detective thriller set in a victorious post WW II Germany and &lt;a href="http://www.amazon.co.uk/exec/obidos/ASIN/014017172X/ref=sr_aps_books_1_2/026-1765779-1917222"&gt;The Man in the High Castle&lt;/a&gt; (by Philip K. Dick and personal favourite of mine) set in an America split down the middle by Germany and Japan.&lt;br&gt;
&lt;br&gt;
There was lots more but I'm running out of steam...&lt;br&gt;
&lt;/span&gt;&lt;/span&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001646.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector top 10 since last night</title>
      <pubDate>Wed, 08 Oct 2003 09:28:18 +0100</pubDate>
      <description>Last night I enabled some new code in K-Collector to track visitors to
each topic.  In combination with other data we are collecting in
the system it should allow us to do some neat tricks, but for now it
tells us which topics people are visiting the most.  The top 10 in
descending order:&lt;br&gt;
&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=knowledge_management"&gt;Knowledge Management&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=don_park"&gt;Don Park&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=robert_scoble"&gt;Robert Scoble&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=bloggercon"&gt;BloggerCon&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=joi_ito"&gt;Joi Ito&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=ideas"&gt;Ideas&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=roland_tanglao"&gt;Rolang Tanglao&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=open_standards"&gt;Open Standards&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=laszlo"&gt;Laszlo&lt;/a&gt;&lt;br&gt;
&lt;a href="http://k-collector.evectors.it/itEntDirectory/w4topicbyid?id=k-collector"&gt;K-Collector&lt;/a&gt;&lt;br&gt;
&lt;br&gt;
The BloggerCon topic has been quite interesting since we added most of
the feeds from the BloggerCon blogroll.  With the new
auto-discovery code in place this has allowed it to link in quite a lot
of posts and relate them to other topics in the system.&lt;br&gt;
&lt;br&gt;
Take a look and let us know what you think.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001650.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector as an RSS catalogue</title>
      <pubDate>Tue, 14 Oct 2003 10:58:05 +0100</pubDate>
      <description>&lt;div style="margin-left: 40px;"&gt;&lt;a href="http://www.istori.com/log/archives/00000310.html"&gt;RSS Feed Catalogs&lt;/a&gt;. Wouldn't it be cool if sites that published lots of RSS feeds could also publish a catalog of those feeds ... [&lt;a href="http://www.istori.com/log/"&gt;istori/log&lt;/a&gt;]&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
We're publishing several hundred &lt;span style="font-style: italic;"&gt;topical &lt;/span&gt;feeds (in RSS2.0 + &lt;a href="http://matt.blogs.it/specs/ENT/1.0/"&gt;ENT&lt;/a&gt; format) from &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;.&amp;nbsp; You can navigate the feed structure quite easily.&amp;nbsp; Start at the &lt;a href="http://w4.evectors.it/"&gt;top-level&lt;/a&gt; and select a category such as &lt;a href="http://k-collector.evectors.it/itentdirectory/wwwwclassification?dir=142"&gt;Who&lt;/a&gt; then browse the available topics under that category.&amp;nbsp; Pick one like &lt;a href="http://k-collector.evectors.it/itentdirectory/wwwwtopic?dir=361"&gt;Don Park&lt;/a&gt; or &lt;a href="http://k-collector.evectors.it/itentdirectory/wwwwtopic?dir=468"&gt;Phil Wolff&lt;/a&gt; and then add the &lt;a href="http://k-collector.evectors.it/itentdirectory/rss2?dir=361"&gt;XML feed&lt;/a&gt; to your aggregator to read posts concerning that person.&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001673.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Knowledge Centrifuge</title>
      <pubDate>Sun, 26 Oct 2003 21:13:00 +0000</pubDate>
      <description>As we get closer to release I've found myself explaining what &lt;a href="http://paolo.evectors.it/"&gt;Paolo&lt;/a&gt; and I are doing with &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;, what the product is about.  So far the best explanation I have come up with is:&lt;br&gt;
&lt;br&gt;
&lt;div style="text-align: left; margin-left: 40px;"&gt;&lt;span style="font-weight: bold;"&gt;Realtime Knowledge Management&lt;/span&gt;&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
What I've been trying to do is make the case that knowledge management
and document management aren't the same thing.  Most knowledge in
a company begins life as a granule of information,
micro-knowledge.  It exists for a time and, if not exploited,
likely dies away to be discovered again later if needed.&lt;br&gt;
&lt;br&gt;
Quite often the inertia that has to be overcome in order to turn such a
granule into the sort of document you would load into Livelink,
Documentum or some equivalent product is overwhelming compared to the
perceived value, at that moment, of the knowledge itself.  It is
only when the cost of repeated rediscovery begins to bite that someone
finally does the decent thing.&lt;br&gt;
&lt;br&gt;
The corrollary to this is that the benefits of knowing that you know
this information are not felt until quite late in it's lifecycle. 
I would guess that, by the time a lot of information is formally
documented, it's probably well on the well to being out of date or
irrelevant (is this your intranet?)&lt;br&gt;
&lt;br&gt;
By contrast the K-Collector approach collects information while it is
still fresh and combines it with other related information before
presenting to users for them to see if it meets their needs.  That
which is good can be promoted to a more appropriate place (for example
a &lt;a href="http://www.socialtext.com/"&gt;Wiki&lt;/a&gt;)  Things which don't make the cut fade into the background but, crucially, are not lost.&lt;br&gt;
&lt;br&gt;
I imagine K-Collector as being a kind of &lt;span style="font-style: italic; color: rgb(0, 0, 153);"&gt;knowledge centrifuge&lt;/span&gt;, spinning together all kinds of different bits of information and separating out the good stuff for you.&lt;br&gt;
&lt;br&gt;
At the heart of K-Collector and determining what makes 'the good stuff'
are topics.  Topics act as markers for points of interest around
which information can be clustered.  The Who, What, Where, When
metaphor we have adopted is - we think - a really simple way of
considering what is important to us all (although, prompted by &lt;a href="http://www.henshall.com/blog/"&gt;Stuart Henshall&lt;/a&gt;, I have been wondering about &lt;span style="font-style: italic;"&gt;Why&lt;/span&gt; as a 5th &lt;span style="font-style: italic;"&gt;W&lt;/span&gt;).&lt;br&gt;
&lt;br&gt;
I think of K-Collector as a kind of multi-dimensional database where
each topic slices through the available information.  We're
working on some pretty cool topic related trickery for future versions
that will take this idea and make it a lot more powerful.&lt;br&gt;
&lt;br&gt;
I'm hoping to get back to writing soon and share more about what we are doing.  I hope this is useful in the meantime.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001679.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector for MovableType</title>
      <pubDate>Wed, 29 Oct 2003 22:57:24 +0000</pubDate>
      <description>I've spent a fair bit of time today working on the &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; client for &lt;a href="http://www.movabletype.org/"&gt;MovableType&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
We tried implementing a client about 6 months ago but it was very
brittle and, ultimately, even I couldn't write instructions for how to
install it on a new server.  This didn't seem like a good way
forward with MT Pro and Typepad around the cornern.&lt;br&gt;
&lt;br&gt;
Our new approach we're much happier with.  It only requires 1
change (adding 1 line) to an existing MT template, 1 perl module
(HTML::HeadParser) and the installation of a handful of new files. It
does not depend upon the MT database or other plugins.  It's
pretty lightweight.&lt;br&gt;
&lt;br&gt;
There is about half a days worth of clean-up required I think and then
it should be ready to beta test.  I'm hoping to start that on
Friday afternoon, interested parties should look out for an
announcement with a link to instructions.&lt;br&gt;
&lt;br&gt;
I'm grateful to &lt;a href="http://www.mplode.com/tima/"&gt;Timothy Appnel&lt;/a&gt; for his &lt;a href="http://www.oreillynet.com/pub/a/javascript/2003/03/18/movabletype.html?page=1"&gt;guide on writing MovableType plugins&lt;/a&gt;.  It was really helpful when things just weren't working.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001689.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector client for MT update</title>
      <pubDate>Mon, 03 Nov 2003 10:12:37 +0000</pubDate>
      <description>Over the weekend I finished the basic K-Collector client for
MovableType.&amp;nbsp; It's still a little rough around the edges,
unoptimized and what have you, but it seems to work here.&amp;nbsp;&amp;nbsp;
In the first instance we're looking for a handful of MT users who are
technically savvy (happy installing perl modules, CGI &amp; don't mind
mucking about with their templates and such) to do the testing, then
we'll open it out when we are sure we have any problems locked down.&lt;br&gt;
&lt;br&gt;
If you would like to be part of this first group please &lt;a href="mailto:k-collector@evectors.com"&gt;drop us a line&lt;/a&gt;.&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001697.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Learning from collaborative filtering</title>
      <pubDate>Thu, 06 Nov 2003 16:24:25 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://www.sims.berkeley.edu/resources/collab/"&gt;Collaborative Filtering resources &lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;[&lt;A href="http://www.decafbad.com/blog"&gt;0xDECAFBAD&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I need to understand how the work being done on collaborative filtering can help us to improve K-Collector.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001703.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Learning templates for organising content</title>
      <pubDate>Mon, 10 Nov 2003 11:14:26 +0000</pubDate>
      <description>I've just come across Denham Grey's &lt;a href="http://denham.typepad.com/km/2003/11/information_gat.html"&gt;Information Gathering Template&lt;/a&gt; post.&amp;nbsp; I'm not sure how I missed it before, I'm subscribed to Denham's feed.&amp;nbsp; Anyhow it's really interesting.&lt;br&gt;
&lt;br&gt;
What he's done is to publish his informal framework for categorizing information when doing research.&amp;nbsp; It goes like this:&lt;br&gt;
&lt;ul&gt;
  &lt;li&gt;People&lt;/li&gt;
  &lt;li&gt;Places&lt;/li&gt;
  &lt;li&gt;Problems&lt;/li&gt;
  &lt;li&gt;Promises&lt;/li&gt;
  &lt;li&gt;Principles&lt;/li&gt;
  &lt;li&gt;Patterns&lt;/li&gt;
  &lt;li&gt;Products&lt;/li&gt;
&lt;/ul&gt;
Please read Denham's post for his excellent notes on each
category.&amp;nbsp; Obviously this is very similar to the approach we have
taken with &lt;a href="http://k-collector.evectors.it/"&gt;K-Collector&lt;/a&gt;.&lt;br&gt;
&lt;ul&gt;
  &lt;li&gt;Who&lt;/li&gt;
  &lt;li&gt;Where&lt;/li&gt;
  &lt;li&gt;What&lt;br&gt;
  &lt;/li&gt;
  &lt;li&gt;When&lt;/li&gt;
&lt;/ul&gt;
to which I think it might make sense to add 'Why'.&amp;nbsp; In this case
our framework is simpler, conflating: problems, promises, principles,
patterns, and, products into what.&lt;br&gt;
&lt;br&gt;
Although W4 is less expressive than Denham's template we think making
it simpler keeps it suitable for general use (Denham is a consultant
and far more experienced than most people.)&lt;br&gt;
&lt;br&gt;
&amp;nbsp;However if we can find a way to layer additional levels of
meaning without giving up that simplicity I think we will do it.&amp;nbsp;
It makes sense to enable users who can benefit from that extra
expressability and for all users to benefit from the new relations we
can build among topics.&amp;nbsp; Since K-Collector's architecture allows
us to do this it's just a matter of working out the best way and Paolo
and I have been talking about this recently.&amp;nbsp; We'll also be
sounding out beta testers and customers to see what they think.&lt;br&gt;
&lt;br&gt;
I'm keen to hear from anyone about their frameworks for collecting
&amp; organising content.&amp;nbsp; I do think we have many lessons to
learn and want &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; to reflect that learning as much as possible.&lt;br&gt;
 </description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001713.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>What comes after a title?</title>
      <pubDate>Mon, 17 Nov 2003 15:32:28 +0000</pubDate>
      <description>&lt;div style="margin-left: 40px;"&gt;&lt;a href="http://radio.weblogs.com/0001011/2003/11/17.html#a5493"&gt;I'm using Titles Now&lt;/a&gt;. &lt;/div&gt;
&lt;p style="margin-left: 40px;"&gt;I'm trying to put titles on my items now,
which should help out my RSS feeds. Hope they work OK. I'm looking for
other ways to improve my weblog's usability. Any other good ideas out
there? Of course, if I forget to put the titles on, then what's the
use? I really hate having to do more work, but I think it's worth it.&lt;/p&gt;
&lt;div style="margin-left: 40px;"&gt; [&lt;a href="http://radio.weblogs.com/0001011/"&gt;The Scobleizer Weblog&lt;/a&gt;]&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
How about adding topics and linking your posts to the shared knowledge space that &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; is becoming?&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001738.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>NewsBayes</title>
      <pubDate>Thu, 20 Nov 2003 16:23:49 +0000</pubDate>
      <description>&lt;div style="margin-left: 40px;"&gt;&lt;a href="http://weblog.infoworld.com/udell/2003/11/20.html#a851"&gt;Working with Bayesian categorizers&lt;/a&gt;. &lt;/div&gt;
&lt;blockquote cite="O'Reilly Network" style="margin-left: 40px;"&gt; There's
been some discussion in the blog world about using a Bayesian
categorizer to enable a person to discriminate along various
interest/non-interest axes. I took a run at this recently and, although
my experiments haven't been wildly successful, I want to report them
because I think the idea may have merit. [Full story: &lt;a href="http://www.xml.com/pub/a/2003/11/19/udell.html"&gt;O'Reilly Network: Working with Bayesian Categorizers&lt;/a&gt;]
&lt;/blockquote&gt;
&lt;div style="margin-left: 40px;"&gt;This month's O'Reilly Network column
was a struggle because categorization itself is a struggle. I remain
convinced that the automated classifiers that are doing such a good job
beating back the tide of spam will also turn out to be more generally
useful. But finding the right synergy between an automated assistant
and a human overseer is a subtle and tricky thing. &lt;b&gt;...&lt;/b&gt; [&lt;a href="http://weblog.infoworld.com/udell/"&gt;Jon's Radio&lt;/a&gt;]&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
Great write-up by Jon of his experiments trying to hotwire Bayesian categorizers for auto-classifying blog posts.&lt;br&gt;
&lt;br&gt;
I think his conclusions demonstrate that there is value in the
approach, certainly as Jon notes, for auto-classification of incoming
items as in a news aggregator.&amp;nbsp; Of course this is exactly what we
are doing with &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; and I
have mused for a while about whether we could use a Bayesian classifier
to improve how we do that (at the moment we are using some pretty
simple keyword analysis).&lt;br&gt;
&lt;br&gt;
I think one of the biggest obstactles is the training.&amp;nbsp; We have
somewhere around 400 topics and many thousands of posts.&amp;nbsp; How hard
would it be to train a classifier?&amp;nbsp; How long would it take?&amp;nbsp;
Could you sell it?&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001745.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>What comes after changeblogs?</title>
      <pubDate>Thu, 20 Nov 2003 16:37:16 +0000</pubDate>
      <description>&lt;div style="margin-left: 40px;"&gt;&lt;a href="http://www.decafbad.com/blog/links/boocjaajai.html"&gt;Quick Links&lt;/a&gt;. &lt;/div&gt;
&lt;ul style="margin-left: 40px;"&gt;&lt;li&gt;&lt;a href="http://jeremy.zawodny.com/blog/archives/001075.html"&gt;CVS Commit + Weblog = Changeblog
&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;
&lt;div style="margin-left: 40px;"&gt;
 [&lt;a href="http://www.decafbad.com/blog"&gt;0xDECAFBAD&lt;/a&gt;]&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
&lt;a href="http://www.dijest.com/aka/"&gt;Phil Wolff&lt;/a&gt; and I were &lt;a href="http://matt.blogs.it/2003/07/21.html#a1042"&gt;talking&lt;/a&gt; about this a little while ago and now &lt;a href="http://www.multiply.org/notebook/"&gt;Jason Gessner&lt;/a&gt; has it working.&amp;nbsp; That's great!&lt;br&gt;
&lt;br&gt;
The next stage for me would be to start creating RSS feeds with &lt;a href="http://matt.blogs.it/spects/ENT/1.0/"&gt;ENT&lt;/a&gt; metadata from those changeblogs. At a very basic level I can imagine a &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;
topic corresponding to each project.&amp;nbsp; Then each topic view could
aggregated not only what developers were writing in their own blogs but
also CVS messages corresponding to the status of the project.&lt;br&gt;
&lt;br&gt;
But why stop there.&amp;nbsp; Your junit based daily smoke &amp; build test
could be generating a similar feed, your project management system,
issue database and so on.&amp;nbsp; All these feeds could be flowing into
project topics giving you an uptodate and holistic view of what is
happening in those projects.&lt;br&gt;
&lt;br&gt;
Who'd ever be caught on the hop in a project meeting again?&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001749.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/effectiveness.xml" ent:id="effectiveness" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/social-networks.xml" ent:id="social-networks" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Whose personality do you want today?</title>
      <pubDate>Fri, 21 Nov 2003 17:47:08 +0000</pubDate>
      <description>&lt;a href="http://www.decafbad.com/blog/"&gt;l.m.orchard&lt;/a&gt; &lt;a href="http://radiocomments.userland.com/comments?u=0107808&amp;p=1243"&gt;commented&lt;/a&gt; regarding the &lt;a href="http://matt.blogs.it/2003/11/20.html#a1243"&gt;using Bayesian analysis on news&lt;/a&gt;.  In fact, as soon as I saw it I remembered, I had read his &lt;a href="http://www.decafbad.com/blog/geek/bayes_agg_one.html"&gt;piece&lt;/a&gt; already.  It was probably his writing that triggered my initial interest in using a Bayesian classifier in &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
Re-reading that piece I got an interesting different angle since his
approach was to blend a Bayesian classifier with his news aggregator to
try and have it prioritize news he would find interesting and not to
categorize it by topic.  I think this is a much more scalable
task, from a K-Collector perspective, than what &lt;a href="http://weblog.infoworld.com/udell/2003/11/20.html#a851"&gt;Jon&lt;/a&gt;
is experimenting with.  I think the efforts of training a
system-wide recognizer to differentiate between topics would be too
much for most users of the product to bear.&lt;br&gt;
&lt;br&gt;
Our product roadmap for K-Collector already includes allowing users to
personalize the system.  For example we think that people should
be able to say which feeds they think are relevant on different
topics.  Notice that this is a much very granular relationship
since it means that I can say "Matt Mower is a real expert on the topic
sock puppets" but that this says nothing about how relevant I am on
"dating." or any other topic.  Indeed each user might rate
the exact same sources differently over a wide range of topics.&lt;br&gt;
&lt;br&gt;
What might be interesting is if people could "share" and "subscribe to"
preference maps.  As a new user of the system you might not really
know who is relevant on any particular topic.  But imagine you
worked with &lt;a href="http://www.hyperorg.com/blogger/"&gt;David Weinberger&lt;/a&gt;, &lt;a href="http://www.dijest.com/aka/"&gt;Phil Wolff&lt;/a&gt;, or &lt;a href="http://weblog.siliconvalley.com/column/dangillmor/"&gt;Dan Gillmor&lt;/a&gt;. 
If you knew them and trusted their judgement you could pick one of
their preference maps as a starting point and immediately gain a
usseful insight into the data as it is structured by topic.  You
might even switch between personalities to get more perspective!&lt;br&gt;
&lt;br&gt;
Thanks to l.m.'s piece I am now wondering also about whether a Bayesian
classifier might be more use in helping users to establish their own
preference maps about which content is most relevant to them.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001757.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/internet-archive.xml" ent:id="internet-archive" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Proud to announce K-Collector 1.0</title>
      <pubDate>Mon, 24 Nov 2003 15:14:55 +0000</pubDate>
      <description>Can it really be a &lt;a href="http://matt.blogs.it/2002/11/20.html#a555"&gt;year &lt;/a&gt;since that fateful day when &lt;a href="http://paolo.evectors.it/"&gt;Paolo&lt;/a&gt; and I scribbed on a whiteboard in Ronchi?&amp;nbsp; Can it really be six months since Paolo, &lt;a href="http://simone.blogs.it/"&gt;Simone&lt;/a&gt; and I gave the &lt;a href="http://paolo.evectors.it/myImages/blogtalk/21.html"&gt;first demo&lt;/a&gt; of the K-Collector prototype?&lt;br&gt;
&lt;br&gt;
Time flies when you're having fun and the last year with my new partners at &lt;a href="http://www.evectors.com/"&gt;Evectors&lt;/a&gt;
(Paolo, Simone, Monica and Fabrizio) has gone so quick my head is
spinning.&amp;nbsp; Or maybe it's the champagne because today we are
announcing the &lt;span style="font-weight: bold;"&gt;launch of &lt;a href="http://www.evectors.com/itkcollector"&gt;K-Collector 1.0&lt;/a&gt;&lt;/span&gt;!&lt;br&gt;
&lt;br&gt;
I'm so proud of what we've achieved together in the last 6
months.&amp;nbsp; The product is better than I could ever have imagined it
would be, and the best is yet to come!&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001766.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/academia.xml" ent:id="academia" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/censorship.xml" ent:id="censorship" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>I am not a vector.  I am a free man!</title>
      <pubDate>Mon, 24 Nov 2003 15:22:16 +0000</pubDate>
      <description>We've posted an &lt;A href="http://www.evectors.com/itkcollector/story$num=4&amp;sec=1&amp;data=kcollector"&gt;essay&lt;/A&gt; which attempts to highlight where we think organisations can benefit from blogging.&lt;BR&gt;&lt;%softShadow("http://paolo.evectors.it/stories/vectorWorkers/images/img6.gif")%&gt;&lt;BR&gt;It continues our &lt;SPAN style="FONT-WEIGHT: bold; FONT-STYLE: italic"&gt;effective organsiations&lt;/SPAN&gt; theme and uses what we think is a very strong visual metaphor for understanding how different organisations can apply similar amounts of effort but get wildy different results.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001771.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/making-money.xml" ent:id="making-money" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/meetup.com.xml" ent:id="meetup.com" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>What do you write after a Tonno e Zucchine sandwich?</title>
      <pubDate>Tue, 02 Dec 2003 19:57:57 +0000</pubDate>
      <description>It's been a good trip - I can't believe I fly back tomorrow.&amp;nbsp; Where did the time go?&amp;nbsp; &lt;a href="http://paolo.evectors.it/"&gt;Paolo&lt;/a&gt; and I have discussed a lot of the strategy behind how we are going to offer &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;
to customers. All those questions we've been putting off till last have
come due.&amp;nbsp; I think we've got some good answers and we'll be
publishing the details soon.&amp;nbsp; I'll also be spending increasing
amounts of my time on sales &amp; marketing now which, strangely, I
find I am looking forward to!&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001780.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/microsoft.xml" ent:id="microsoft" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/outlook.xml" ent:id="outlook" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/shitty-software.xml" ent:id="shitty-software" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>First steps with Lucene</title>
      <pubDate>Tue, 02 Dec 2003 20:43:39 +0000</pubDate>
      <description>I'm playing with the &lt;a href="http://jakarta.apache.org/lucene/"&gt;Jakarta Lucene&lt;/a&gt; search engine at the moment as a way of implementing some neat new stuff for &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt;.&amp;nbsp;
I've got a Java app talking to K-Collector via XML-RPC and indexing
posts from our database.&amp;nbsp; I think it took me about 15 minutes from
cold to having butchered the sample apps to do what I want.&amp;nbsp; That
seems like a good sign to me.&amp;nbsp; While browsing for more information
about Lucene I came across &lt;a href="http://www-106.ibm.com/developerworks/library/j-lucene/"&gt;an article&lt;/a&gt; talking about Lucene and another Jakarta library called &lt;a href="http://jakarta.apache.org/commons/digester.html"&gt;Digester&lt;/a&gt;.&amp;nbsp; Digester is a neat XML to Java object mapper.&amp;nbsp; I'll be taking a better look at it over the next few days.&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001782.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/powerpoint.xml" ent:id="powerpoint" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/story-telling.xml" ent:id="story-telling" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Gimme the highlights</title>
      <pubDate>Fri, 09 Jan 2004 18:52:59 +0000</pubDate>
      <description>&lt;p&gt;Today we've released a new feature for &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; which we think makes related topics more useful.&lt;/p&gt;
&lt;p&gt;Now when browsing a topic the related topics are rendered as checkboxes.  When the checkbox corresponding to a specific post is checked, the posts on the current page associated with that topic are highlighted.  This makes it very easy to spot posts referencing a specific combination of topics.&lt;/p&gt;
&lt;p&gt;For example: want to see what people have said about Howard Dean and Meetup? On the page for &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=howard_dean"&gt;Howard Dean&lt;/a&gt; check the topic &lt;em&gt;MeetUp&lt;/em&gt; and then quickly scroll down to find just those posts. It's a really quick way of finding something in the view.&lt;/p&gt;
&lt;p&gt;All feedback welcome.&lt;/p&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001793.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/adaptive-resonance-theory.xml" ent:id="adaptive-resonance-theory" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/algorithms.xml" ent:id="algorithms" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/ruby.xml" ent:id="ruby" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>ETCon'04 - We won't be there</title>
      <pubDate>Fri, 16 Jan 2004 08:57:46 +0000</pubDate>
      <description>&lt;blockquote&gt;&lt;a href="http://socialsoftware.weblogsinc.com/entry/4114434910144189/"&gt;ETECH is coming up....&lt;/a&gt;. &lt;A href="http://socialsoftware.weblogsinc.com/entry/4114434910144189/"&gt;O'Reilly's Emerging Technology Conference...&lt;/A&gt;. 
&lt;H2&gt;OReillys Emerging Technology Conference&lt;/H2&gt;
&lt;H3&gt;Posted Jan 15, 2004, 6:54 PM ET by Judith Meskill&lt;/H3&gt;&lt;IMG src="http://conferences.oreillynet.com/images/et2004/etcon_butterfly.gif" align=right&gt; 
&lt;P&gt;&lt;A href="http://conferences.oreillynet.com/etech/"&gt;&lt;FONT color=#660000&gt;OReillys Emerging Technology Conference&lt;/FONT&gt;&lt;/A&gt;  taking place at the Westin Horton Plaza, San Diego, CA, Feb. 9-12, 2004  will have a &lt;A href="http://conferences.oreillynet.com/pub/w/28/track_social.html"&gt;&lt;FONT color=#660000&gt;Social Software track&lt;/FONT&gt;&lt;/A&gt;. This promises to be an excellent event with a broad spectrum of notable speakers that includes (but is certainly not limited to): &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/1686"&gt;&lt;FONT color=#660000&gt;Helen Greiner&lt;/FONT&gt;&lt;/A&gt; - iRobot Corp., &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/521"&gt;&lt;FONT color=#660000&gt;Cory Doctorow&lt;/FONT&gt;&lt;/A&gt; - EFF, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/1730"&gt;&lt;FONT color=#660000&gt;Lili Cheng&lt;/FONT&gt;&lt;/A&gt; - Microsoft Research, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/1727"&gt;&lt;FONT color=#660000&gt;Gilman Louie&lt;/FONT&gt;&lt;/A&gt; - In-Q-Tel, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/363"&gt;&lt;FONT color=#660000&gt;David Sifry&lt;/FONT&gt;&lt;/A&gt; - Technorati, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/1703"&gt;&lt;FONT color=#660000&gt;Joichi Ito&lt;/FONT&gt;&lt;/A&gt; - Neoteny, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/1669"&gt;&lt;FONT color=#660000&gt;Elizabeth Lawley&lt;/FONT&gt;&lt;/A&gt; - Rochester Institute of Technology, and, of course, &lt;A href="http://conferences.oreillynet.com/cs/et2004/view/e_spkr/416"&gt;&lt;FONT color=#660000&gt;Tim OReilly&lt;/FONT&gt;&lt;/A&gt; - OReilly &amp; Associates. [&lt;A href="http://socialsoftware.weblogsinc.com/"&gt;The Social Software Weblog&lt;/A&gt;]&lt;/P&gt;
&lt;P&gt;This is the key event of the year.&amp;nbsp; We're gonna party like is USED to be 1999.&lt;/P&gt;
&lt;P&gt;I'll be there - sponsored by &lt;A href="http://laszlosystems.com"&gt;Laszlo Systems&lt;/A&gt; and I'll be giving a :05 minute talk on FOAF and the PeopleAggregator.&lt;/P&gt;
&lt;P&gt;But clearly the most exciting event will be the field trip to TJ and the House of Mole.&amp;nbsp; Something not to be missed.&lt;/P&gt; [&lt;a href="http://blogs.it/0100198/"&gt;Marc's Voice&lt;/a&gt;]&lt;/blockquote&gt;
&lt;p&gt;Anyone out there want to sponsor three Europeans with a kick-ass new RSS based collaborative knowledge organisation tool to go to ET'04?&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001810.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/javascript.xml" ent:id="javascript" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/web-ui.xml" ent:id="web-ui" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector @ Wonder Widgets, Inc.</title>
      <pubDate>Sat, 17 Jan 2004 17:10:37 +0000</pubDate>
      <description>&lt;p&gt;We have recently launched a new &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt; demo site.  This is intended to show prospective customers how K-Collector might look (&amp; be used) in their company.  The &lt;a href="http://w4.evectors.it/"&gt;W4 portal&lt;/a&gt; is interesting but too eclectic to really get an idea of how K-Collector is intended to work.&lt;/p&gt;
&lt;p&gt;The site in question is for our imaginary company &lt;em&gt;Wonder Widgets, Inc.&lt;/em&gt; who are purveyors of fine Java and .NET components.  We had a bit of fun making up lots of posts ...it's how I imagine soap opera are written... we've already had one person leave the company!&lt;/p&gt;
&lt;p&gt;So, if you've wondered what K-Collector is &lt;em&gt;really&lt;/em&gt; all about,  please drop me a line and I will organise a short (10-20 mins) demo for you.  I'm happy to do this as I need the practice :-)&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001822.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/search.xml" ent:id="search" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector demo site</title>
      <pubDate>Sun, 18 Jan 2004 08:57:58 +0000</pubDate>
      <description>&lt;p&gt;A quick clarification.  I notice that some people read my previous &lt;a href="http://matt.blogs.it/2004/01/17.html#a1294"&gt;post&lt;/a&gt; and thought the &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt; link in that post was pointing at the demo site I referrred to.&lt;/p&gt;
&lt;p&gt;In fact I has linking to the K-Collector page on the &lt;a href="http://www.evectors.com/"&gt;Evectors&lt;/a&gt; website.  This is because the demo site is behind a login at the moment -- we want to make sure that people who use the demo site get the best possible experience.  I realise now that this was not at all clear.  My apologies for that.&lt;/p&gt;
&lt;p&gt;If you want to see the demo please just drop me a line and i'll do the rest.  At some point we intend to provide an unguided demo (maybe in the form of a series of &lt;a href="http://www.qarbon.com/products/viewlet/"&gt;Viewlets&lt;/a&gt;).&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001830.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/consulting.xml" ent:id="consulting" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/self-publishing.xml" ent:id="self-publishing" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>So Dean lost Iowa</title>
      <pubDate>Tue, 20 Jan 2004 06:51:22 +0000</pubDate>
      <description>&lt;p&gt;I saw the headline when I went to &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; this morning and then read most of the details at the &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=howard_dean"&gt;Howard Dean&lt;/a&gt; topic.  It made a very nice summary of the night and the various viewpoints.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001842.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/tools.xml" ent:id="tools" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Permission based posting</title>
      <pubDate>Sun, 08 Feb 2004 00:13:18 +0000</pubDate>
      <description>&lt;p&gt;Just a couple of follow-on thoughts...&lt;/p&gt;
&lt;p&gt;&lt;ol&gt;&lt;li&gt;If a feed is copyright, does that mean an aggregator should not collect it?  Is this &lt;em&gt;reproducing&lt;/em&gt; the work?  (How is it different, for example, from downloading pirated software?)&lt;/li&gt;
&lt;li&gt;What does it say when an author asserts copyright of material, but publishes it in an RSS feed?  The Creative Commons licenses grant rights to the recipient.  Copyright (AFAIK) does not.&lt;/li&gt;
&lt;li&gt;Does it matter what type of aggregator it is?  For example &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt; aggregates in a different way (and for a different purpose) to, for example, &lt;a href="http://radio.userland.com/"&gt;Radio Userland&lt;/a&gt; or &lt;a href="http://ranchero.com/netnewswire/"&gt;NetNewsWire&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;If it aggregates a feed, should it prevent you from re-posting aggregated content?  In Radio this is very easy, I can click a button on a post in the aggregator to use it as the basis for a post to my own weblog.  If an item is copyright should it stop me doing that?&lt;/li&gt;
&lt;/ol&gt;&lt;/p&gt;
&lt;p&gt;I think this draws us awfully close to the kinds of things Ted Nelson was thinking about when he outlined his vision for transclusion based publishing.  I can almost envisage a system where, when I press the post button on a copyright item, my aggregator goes off to check with the original authors system for permission to publish.  You could imagine using the data from a social network to decide who can republish your content with your permission.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001859.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/health.xml" ent:id="health" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Licensed to aggregate (pt #2)</title>
      <pubDate>Tue, 10 Feb 2004 08:00:08 +0000</pubDate>
      <description>&lt;p&gt;I have received a couple of comments to my earlier &lt;a href="http://matt.blogs.it/2004/02/08.html#a1315"&gt;piece&lt;/a&gt; about licensing &amp; RSS.  Among others Phil Ringnalda pointed me at the &lt;a href="http://backend.userland.com/creativeCommonsRssModule"&gt;Creative Commons RSS Module&lt;/a&gt; authored by &lt;a href="http://www.scripting.com/"&gt;Dave Winer&lt;/a&gt; in Dec 2002.&lt;/p&gt;
&lt;p&gt;The CC module is pretty much the same solution as I was proposing in that it seems to be a start in the right direction.  However neither it, nor my own suggestion, answer all the questions in a way I can appreciate (e.g. as Phil points out, what is covered by the license: text only? images? etc...), so i'm going to keep chipping at this.&lt;/p&gt;
&lt;p&gt;A commentor, &lt;a href="http://www.lulop.com/"&gt;Lorenzo&lt;/a&gt;, has suggested that &lt;blockquote&gt;Copyright is a "state" and licensing is an "action" made possible by the state.&lt;/blockquote&gt;I kind of disagree with this statement but mainly on terminological grounds.  I hope we can cut through that by agreeing that the central point is &lt;em&gt;rights&lt;/em&gt;.  Who has them?  What uses do they permit?&lt;/p&gt;
&lt;p&gt;It seems to me that a Copyright statement reserves all rights relating to making copies (&amp; derivative works) to the author who can then make exceptions on a case-by-case basis.  As in the case where an author grants their publisher the right to make copies for sale.&lt;/p&gt;
&lt;p&gt;Hence an RSS feed with a copyright notice shouldn't be read (copied) unless you consider the act of offering feed to be an implicit agreement by the author to do so.  Of course from a software perspective implicit rights can be problematic, especially when they are not immutable or well understood. For an RSS feed with a copyright statement what rights are actually on offer?  People commonly republish content from posts they have aggregated either whole or in part.  How do they know they have the right to do so?&lt;/p&gt;
&lt;p&gt;Then you have some interesting anomalies when software gets in the way.  For example, my &lt;a href="http://matt.blogs.it/"&gt;weblog&lt;/a&gt; has a &lt;a href="http://creativecommons.org/"&gt;Creative Commons&lt;/a&gt; &lt;a href="http://creativecommons.org/licenses/by-nd-nc/1.0"&gt;license&lt;/a&gt;, yet my &lt;a href="http://matt.blogs.it/rss.xml"&gt;feed&lt;/a&gt; is Copyright.  I guess Radio is automatically adding the copyright notice, I don't know how to make it stop.  What am I telling you?&lt;/p&gt;
&lt;p&gt;Alternatively, and I guess this may be common, Phil Ringnalda's blog doesn't have any kind of license at all, neither does his feed.  Can I assume Phil intends all his material to be public domain?  If i'm not clear that this is the intension how can my software be?&lt;/p&gt;
&lt;p&gt;Creative Commons offer a range of licenses which offer the right to copy, or make derivative works, with certain restrictions such as &lt;em&gt;share alike&lt;/em&gt; and &lt;em&gt;non commercial use only&lt;/em&gt;. Primarily Public Domain takes this a step further in granting unlimited rights with exceptions being, if you'll excuse the pun, the exception.&lt;/p&gt;
&lt;p&gt;Maybe it's my developer "tunnel vision" at work but this looks very similar to the common model of permissions adopted in software everywhere:
&lt;ul&gt;
&lt;li&gt;include * except A, B, C,...&lt;/li&gt;
&lt;li&gt;exclude * except R, S, T,...&lt;/li&gt;
&lt;/ul&gt;
where A, B, etc.. are not users or hosts but &lt;em&gt;specific actions, by identified individuals, in specific circumstances.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;For most personal news aggregators I guess none of this matters much.  If someone publishes a feed, and you're just reading it, then whats the harm?  Unless of course you weren't supposed to have the URL to the feed.  But that's a different issue.&lt;/p&gt;
&lt;p&gt;However for aggregators like &lt;a href="http://w4.evectors.it/"&gt;K-Collector&lt;/a&gt; and users who are reposting content it's a different matter.  For example K-Collector doesn't mess with the content of posts, but it does republish them in a new context.  If K-Collector has a better Google page rank than the author then we even begin to suck traffic away from them based upon their own material!&lt;/p&gt;
&lt;p&gt;&lt;em&gt;(To be clear I am only talking about the public K-Collector portal &lt;a href="http://w4.evectors.it/"&gt;W4&lt;/a&gt;.  This is an untypical use of &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt; which is designed for use within organisations.  But the point still stands.  And what about &lt;a href="http://www.feedster.com/"&gt;Feedster&lt;/a&gt;?)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As ambitious, semi-automated, software like K-Collector become more common then a reasonable, dependable, system of rights is going to be required. To my way of thinking the &lt;a href="http://backend.userland.com/creativeCommonsRssModule"&gt;Creative Commons RSS Module&lt;/a&gt;, whilst a start in the right direction, addresses a necessary, but not sufficient, subset of the goals.  What do we do to take it further?&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001866.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/apple.xml" ent:id="apple" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/powerbook.xml" ent:id="powerbook" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>ESF, topics and K-Collector</title>
      <pubDate>Wed, 25 Feb 2004 22:08:05 +0000</pubDate>
      <description>&lt;blockquote&gt;Event Sharing, publishing, syndicating, etc. When we introduced the "when" part in the &lt;a href="http://w4.evectors.it/"&gt;w4&lt;/a&gt;
concept, almost one year ago, what we had in mind was a space where
events would be topics which could be aggregated in calendars and
allowed users to navigate information using a timeline.&lt;br&gt;
...
&lt;br&gt;
Using the same approach we are using with topics, new events will be
automatically distributed among members of a cloud allowing users to
pick an event if it already exist instead of creating it. &lt;br&gt;
&lt;br&gt;
There will also be relations between events and other topics on the
server, which we believe will create a sigificant added value to the
process (allowing, for example, to quickly move to all information
related to an event to all information related to one of the
participants).&lt;br&gt;
&lt;br&gt;[&lt;a href="http://paolo.evectors.it/"&gt;Paolo Valdemarin: Paolo's Weblog&lt;/a&gt;]&lt;/blockquote&gt;
&lt;p&gt;The &lt;em&gt;When&lt;/em&gt; classification was always a key part of the overall vision of K-Collector.  Being able to navigate sensibly based upon time &amp; date is a very powerful concept.&lt;/p&gt;
&lt;p&gt;One of the last things I did within liveTopics before moving on to K-Collector was to implement time as an &lt;a href="http://www.xfml.org"&gt;XFML&lt;/a&gt; facet.  This created a hierarchy of topics representing dates.  For example there was a topic "2003".  This in turn contained 12 sub-topics "Jan 2003" through "Dec 2003".  Each of these topics contained a further division by date.  Posts were linked to these topics based upon publication date.  The upshot was that you could browse based on an increasingly specific date filter.&lt;/p&gt;
&lt;p&gt;We will be looking to implement &lt;em&gt;When&lt;/em&gt; topics in K-Collector in conjunction with ESF events.  The idea will be to link the event (perhaps defined as a &lt;em&gt;What&lt;/em&gt; topic), with a particular point in time (a &lt;em&gt;When&lt;/em&gt; topic), a place (&lt;em&gt;Where&lt;/em&gt;) and possibly people attending (&lt;em&gt;Who&lt;/em&gt;).  Hence an event will form a glue which binds together a number of different topics in a context.&lt;/p&gt;
&lt;p&gt;Example:
&lt;dl&gt;
&lt;dt&gt;What&lt;/dt&gt;
&lt;dd&gt;blogtalk 2.0&lt;/dd&gt;
&lt;dt&gt;Where&lt;/dt&gt;
&lt;dd&gt;Vienna&lt;/dd&gt;
&lt;dt&gt;Who&lt;/dt&gt;
&lt;dd&gt;Thomas Burg&lt;/dd&gt;
&lt;dt&gt;When&lt;/dt&gt;
&lt;dd&gt;5-Jul-2004&lt;/dd&gt;
&lt;/dl&gt;&lt;/p&gt;
&lt;p&gt;There are still issues to work out like: What about events which span multiple days?  Do we represent time on the calendar?  What about recurring events?  And so on.  But I think even a simple model which dodges many of these questions would be amply useful at this point.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001924.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/london.xml" ent:id="london" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/news-coverage.xml" ent:id="news-coverage" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/terrorism.xml" ent:id="terrorism" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>More on #kmtalk and IRC integration</title>
      <pubDate>Tue, 13 Apr 2004 17:58:47 +0100</pubDate>
      <description>A couple more visitors to &lt;a href="http://matt.blogs.it/2004/04/09.html#a1399"&gt;#kmtalk&lt;/a&gt;.&amp;nbsp; First there was the author of &lt;a href="http://jcwinnie.us/MT/weblog/"&gt;Your Guess Is As Good as Mine&lt;/a&gt; (Jonathan Smith?).&amp;nbsp; Also &lt;a href="http://www.terryfrazier.com/weblog/"&gt;Terry Frazier&lt;/a&gt; and &lt;a href="http://www.rklau.com/tins/"&gt;Rick Klau&lt;/a&gt; stopped by.&amp;nbsp; Terry demonstrated his l33t skills by signing in using his Treo 600 (using &lt;a href="http://www.smittyware.com/palm/upirc/"&gt;upIRC&lt;/a&gt;).&lt;br&gt;
&lt;br&gt;
Anyone and everyone who is interested in knowledge management,
communities of practice, collaboration, wiki, social networks and other
related topics is welcome to stop by.&amp;nbsp; Right now I am interested
in how IRC can be linked to other tools (including &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt; of course).&lt;br&gt;
&lt;br&gt;
For example might it be useful to link K-Collector topics (e.g. &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=knowledge_management&amp;chunck=1"&gt;Knowledge Management&lt;/a&gt;) to IRC channels?&amp;nbsp; For example topics like &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=knowledge_management&amp;chunck=1"&gt;Knowledge Management&lt;/a&gt;, &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=k_logs&amp;chunck=1"&gt;K-Logs&lt;/a&gt;, &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=knowledge_organisation&amp;chunck=1"&gt;Knowledge Organisation&lt;/a&gt;, &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=knowledge_work&amp;chunck=1"&gt;Knowledge Economy&lt;/a&gt;, &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=collaboration&amp;chunck=1"&gt;Collaboration&lt;/a&gt;, &lt;a href="http://w4.evectors.it/itentdirectory/topic?topic=commercial_blogging&amp;chunck=1"&gt;Commercial blogging&lt;/a&gt;, ... could all be linked to the #kmtalk IRC channel. Topics about different subjects could be linked to other channels.&lt;br&gt;
&lt;br&gt;
The idea is that people viewing the web topic could see who was talking
in the channel (want to join in?) and recent traffic in the channel
(have something to add?) Could this be a useful application?&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002073.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/the-state.xml" ent:id="the-state" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Getting Real with Stowe</title>
      <pubDate>Tue, 20 Apr 2004 21:46:17 +0100</pubDate>
      <description>Had a first chat with &lt;a href="http://www.corante.com/getreal/"&gt;Stowe Boyd&lt;/a&gt;
this evening.&amp;nbsp; Enjoyed it very much despite some troubles with
Skype (poor voice quality in one direction or another at various
points) which we augmented with IM.&amp;nbsp; We talked about &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;, IRC, Wiki, Sense making, Cynefin, social tools and how KM is suffering from &lt;span style="font-style: italic;"&gt;fatigue&lt;/span&gt;.&amp;nbsp; Thanks Stowe!&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002088.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/spam.xml" ent:id="spam" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Presenting People Centred Knowledge Management at the CiG</title>
      <pubDate>Thu, 29 Apr 2004 18:16:24 +0100</pubDate>
      <description>On Tuesday night I did my first proper speakers gig, giving a 20 minutes presentation of &lt;b&gt;People Centred Knowledge Management&lt;/b&gt; (PCKM) to members of the &lt;a href="http://www.cityinformation.org.uk"&gt;City Information Group&lt;/a&gt;
(I'll link to their event page when it's been updated).  I had a
great time doing the event and I've had some positive feedback - I hope
everyone there got something out of it.  My thanks to the &lt;a href="http://www.cityinformation.org.uk/Committee/committee.htm"&gt;organizers&lt;/a&gt; Jackie, Genevieve and Nick.&lt;br&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href="http://matt.blogs.it/gems/presentations/CIG_apr_2004/CIG%20Presentation.htm"&gt;Web&lt;/a&gt; version of the presentatin.  (Should work in all browsers, but you know PowerPoint)&lt;br&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;a href="http://matt.blogs.it/gems/presentations/CIG_apr_2004/CIG%20Presentation_export.pdf"&gt;PDF&lt;/a&gt; version of the presentation here. (447K)&lt;/li&gt;
  &lt;li&gt;&lt;a href="http://matt.blogs.it/gems/maps/cig_apr_2004/Speakers%20notes.html"&gt;Speakers notes&lt;/a&gt; (This will give you a better idea of &lt;b&gt;what I said&lt;/b&gt;).&lt;/li&gt;
&lt;/ul&gt;
I'd like to express my thanks to &lt;a href="http://paolo.evectors.it/"&gt;Paolo&lt;/a&gt;, &lt;a href="http://www.dijest.com/aka/"&gt;Phil&lt;/a&gt;, &lt;a href="http://www.hyperorg.com/blogger/"&gt;David&lt;/a&gt;, and &lt;a href="http://chocnvodka.blogware.com/blog"&gt;Suw&lt;/a&gt; who were all invaluable in helping me to get prepared.  I think it really paid off. &lt;br&gt;
&lt;br&gt;
Update: It occurs to me that really you don't get very much from my
slides.  The presentation was a lot about me talking, waving my
arms and hopping up and down.  You don't get that from
PowerPoint.  Next time I'd like to be able to webcast the
presentation.  Anyone have any advice about that sort of thing?&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002138.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Teenage Taxonomies</title>
      <pubDate>Sat, 01 May 2004 10:40:23 +0100</pubDate>
      <description>I've been thinking about how topics are organized in &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;. 
As of my writing the largest K-Collector site is &lt;a href="http://w4.evectors.it/"&gt;W4&lt;/a&gt; which currently has
726 topics defined in 3 classifications.&lt;br&gt;
&lt;ul&gt;
  &lt;li&gt;What - 410 topics&lt;br&gt;
  &lt;/li&gt;
  &lt;li&gt;Who - 227 topics&lt;br&gt;
  &lt;/li&gt;
  &lt;li&gt;Where - 89 topics&lt;br&gt;
  &lt;/li&gt;
&lt;/ul&gt;
This is beginning to present some challenges.  For example current
interfaces in K-Collector clients for selecting topics highlite
suggested topics but also display all available topics (under their
classifications) for you to choose from.  The problem is that,
with this number of topics, it's all rather unwieldy.&lt;br&gt;
&lt;br&gt;
I already think that it would be advantageous to allow a further
subdivision of the classifications to form a 3-level hierarchy. 
For example What could subdivide into things like products, protoocols,
principles, patterns and so on (sort of modelled after Denham Grays &lt;a href="http://denham.typepad.com/km/2003/11/information_gat.html"&gt;Information Gathering Template&lt;/a&gt;).  But this is not a complete answer.&lt;br&gt;
&lt;br&gt;
First I do not want to grow arbitrarily nested taxonomies.  If you
think about your own experience with menu bars, how often do you look
more than 3 levels deep?  And how irritating is it to have to poke
around like that?  Also the deeper the taxonomy the more effort
has to be put into designing it and this is the domain of experts and
to be avoided&lt;br&gt;
&lt;br&gt;
Second faceted classifications only work when they narrow things. 
As you descend the hierarchy you become more precise about the term you
are talking about (Anything =&gt; any person =&gt; a member of a group
=&gt; an individual).  But for example, when I am writing a post
about politics and economics I am really only interested in topics
related to those subjects, i.e. I have cross-cutting concerns (like &lt;a href="http://server2.hostvalu.com/pipermail/discuss_aosd.net/2002-January/000052.html"&gt;Aspects w.r.t. OOP&lt;/a&gt;) &lt;br&gt;
&lt;br&gt;
I've been thinking a little bit about Peter Van Dijck's &lt;a href="http://poorbuthappy.com/ease/archives/002822.html"&gt;suggestion&lt;/a&gt; for &lt;i&gt;nested facets&lt;/i&gt;.  As Travis Wilson described it in a post to the facetedclassification list:&lt;br&gt;
&lt;blockquote&gt;
  &lt;pre wrap=""&gt;For example, Peter's article poses a "Product Type" facet where "Cameras" &lt;br&gt;is a heading down in the taxonomy somewhere. Cameras have certain &lt;br&gt;properties like "Resolution" and "Lens Type" that just aren't relevant to, &lt;br&gt;say, hubcaps. So "Resolution" and "Lens Type" are facets with a scope of &lt;br&gt;"Product Type = Camera". A faceted navigation interface would expose them &lt;br&gt;whenever a search was already restricted to "Camera". Otherwise, they're &lt;br&gt;structured like every other facet you've ever seen.&lt;/pre&gt;
&lt;/blockquote&gt;
to see whether there is a role for nested facets.  I'm still thinking about that.&lt;br&gt;
&lt;br&gt;
It's also possible that we could also use the many relations (thousands
and thousands of them) that K-Collector builds up to create dynamic
cross-cutting hierarchies.  The idea here would be to take one or
two dominant topics and then order all other topics according to how
relevant they were.  This should, in theory, put more relevant
topics closer to your attention.&lt;br&gt;
&lt;br&gt;
No solutions yet, just questions &amp; ideas.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002158.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>What ever happened to the Event Share Framework?</title>
      <pubDate>Sat, 01 May 2004 11:13:54 +0100</pubDate>
      <description>The &lt;a href="http://www.esfstandard.org/"&gt;Event Share Framework&lt;/a&gt;
seemed to have some buzz a little while back.&amp;nbsp; I posted a question
about implementation (we really wanted to do something like this in &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;)
to the ESF list but got zero response and can't say I've seen anyone
talking about it since.&amp;nbsp; Did it disappear off the radar?&amp;nbsp; Has
it gone underground?&amp;nbsp; Does anyone know?&amp;nbsp; Or care?&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002168.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>800 topics bouncing around</title>
      <pubDate>Wed, 12 May 2004 09:03:13 +0100</pubDate>
      <description>&lt;blockquote&gt;&lt;a href="http://www.community-intelligence.com/blogs/public/archives/000264.html"&gt;Visualizing social networks&lt;/a&gt;.
Increasing the capacity of people and communities to visualize their
(online) social networks is essential to the evolution of Collective
Intelligence. [&lt;a href="http://www.community-intelligence.com/blogs/public/"&gt;Blog of Collective Intelligence&lt;/a&gt;]&lt;br&gt;
&lt;/blockquote&gt;
&lt;br&gt;
I still really want some kind of visualization for K-Collector.&amp;nbsp;
We're generating lots of data, relationships between topics and posts,
topics and topics, people and posts, people and topics, people and
people and more all the time.&amp;nbsp; When all you have is tables full of
data it's hard to work out what might be interesting or valuable.&lt;br&gt;
&lt;br&gt;
The &lt;a href="http://prefuse.sourceforge.net/"&gt;prefuse visualization library&lt;/a&gt; looks very neat although I have done similar things in the past with &lt;a href="http://www.touchgraph.com/"&gt;Touchgraph&lt;/a&gt;.&amp;nbsp;
However a key problem remains, when dealing with large data sets, how
to make a meaningful subset of them usable.&amp;nbsp; Do you really want a
graph with 800 topics bouncing around?&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002230.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>K-Collector client demystified</title>
      <pubDate>Thu, 20 May 2004 08:49:02 +0100</pubDate>
      <description>&lt;blockquote&gt;&lt;a href="http://www.readwriteweb.com/archives/001877.html"&gt;More on Topic-Sharing Community&lt;/a&gt;. 
  &lt;p&gt;There's already been a great response to &lt;a href="http://www.readwriteweb.com/archives/001876.html"&gt;my post last night&lt;/a&gt; (see the comments to previous entry). &lt;a href="http://www.blogdigger.com/blog/index.html"&gt;Greg&lt;/a&gt; suggested his aggregator &lt;a href="http://www.blogdigger.com/"&gt;Blogdigger&lt;/a&gt; could be included in this - I agree! &lt;a href="http://matt.blogs.it/"&gt;Matt&lt;/a&gt; and &lt;a href="http://www.andrewsw.com/news/index.php"&gt;Andrew&lt;/a&gt; also posted very thoughtful responses.&lt;/p&gt;
  &lt;p&gt;Here's some of my feedback (copied from the comments - I must get these enabled inline...):&lt;/p&gt;
  &lt;p&gt;Overnight while pondering my post (which I regard as just a
'starter for 10' btw, not a final solution by any means), I did
conclude that KC essentially already does what I describe - polls
registered RSS feeds with ENT in them and aggregates them. It would be
great if TE also had that functionality.&lt;/p&gt;
  &lt;p&gt;It's the client ping that I think is unnecessary and possibly
holding back community uptake - with TE the ping is a manual process
for the blogger, and with KC you need to install an add-on tool to
enable the pinging. Both require too much manual effort for the blogger
(IMHO of course). eg Bloglines does all its aggregation automatically
(every hour I think), with no pinging required from the blogger.&lt;/p&gt;
  &lt;p&gt;Although Andrew I take your point about bandwidth utilization. But if Bloglines (and Blogdigger) can do it, why not KC and TE?&lt;/p&gt;
 [&lt;a href="http://www.readwriteweb.com/"&gt;Read/Write Web&lt;/a&gt;]&lt;br&gt;
&lt;/blockquote&gt;There seems to be some confusion about how &lt;a href="http://www.evectors.it/itkcollector/"&gt;K-Collector&lt;/a&gt;
server works and the role of the K-Collector client so I thought I would try and give an explanation of how things fit together.&lt;br&gt;
&lt;br&gt;
The first thing to understand is that you absolutely &lt;b&gt;do not&lt;/b&gt;
need the K-Collector client for your blog to be part of a K-Collector
site.  The client offers a set of benefits aimed at improving the
experience for the user, but they are entirely optional.  We
currently aggregate many feeds to the &lt;a href="http://w4.evectors.it/"&gt;W4&lt;/a&gt; site which are not using one of our clients.&lt;br&gt;
&lt;br&gt;There are three reasons why we think using the client is beneficial:&lt;br&gt;
&lt;br&gt;
1) The ping (it's the least important, but seems most misunderstood so I'll cover it first)&lt;br&gt;
&lt;br&gt;
The K-Collector server contains an aggregator which reads all feeds on a
rotating basis.  It aims to read each feed more or less once per
hour but this isn't guaranteed.  It collects posts from feeds and assigns them to topics using either &lt;a href="http://www.purl.org/NET/ENT/1.0/"&gt;ENT&lt;/a&gt;
metadata supplied in the feed or choices which are auto-discovered using various word-stemming and matching techniques.&lt;br&gt;
&lt;br&gt;
This all happens entirely independent of the client ping.  &lt;b&gt;All the
ping does is to move your feed up the list so that new posts
you have written are likely to be collected sooner.&lt;/b&gt;  If you don't ping the server just reads your feed automatically a little later on, that's all.&lt;br&gt;
&lt;br&gt;
2) The topic manager&lt;br&gt;
&lt;br&gt;
Through the client, the topic manager is integrated into the blog
editing process and gives authors the ability to assign community
topics to their posts as well as being able to create new topics. 
The topic manager also attempts to suggest topics which may be relevant
to the content of the post to make choosing topics easier.&lt;br&gt;
&lt;br&gt;
Without the client you have no way to decide which topics should be
assigned to each post.  In this case the server will, when it
reads the feed, use it's own automatcher to automatically assign those
topics it thinks are relevant.&lt;br&gt;
&lt;br&gt;
3) ENT feeds&lt;br&gt;
&lt;br&gt;
Where the author has choosen topics in the topic manager the client
adds the appropriate ENT metadata to the outgoing RSS feed. 
K-Collector can then use this metadata to accurately assign posts to
topics.&lt;br&gt;
&lt;br&gt;
In summary the K-Collector client offers what we think are very useful
benefits to weblog authors, however it is entirely optional and you do
not need it for you weblog to be part of a K-Collector site.
Equivalently K-Collector itself only cares about RSS.&amp;nbsp; It doesn't
care whether ENT metadata was created by our client or some other
application, we're completely agnostic about that.&lt;br&gt;
&lt;br&gt;
I hope this goes some way to clearing up how the K-Collector system works.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002257.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Getting my head shifted</title>
      <pubDate>Tue, 25 May 2004 09:29:09 +0100</pubDate>
      <description>Had a very nice lunch with Lee Bryant of &lt;a href="http://www.headshift.com/"&gt;HeadShift&lt;/a&gt; yesterday.&amp;nbsp; We met in &lt;a href="http://matt.blogs.it/2004/04/09.html"&gt;#kmtalk&lt;/a&gt; talking about the &lt;a href="http://www.socialtext.net/stes/"&gt;Social Tools for Enterprises Symposium&lt;/a&gt; I am helping to create..&amp;nbsp; Headshift are based in &lt;a href="http://www.pooloflondon.co.uk/visiting.builder/places/0010.html"&gt;Butlers wharf&lt;/a&gt;, right on the river, which is a great setting for a meet up.&lt;br&gt;
&lt;br&gt;
Over spinach &amp; ricotta parcels and some &lt;a href="http://www.staropramen.cz/"&gt;Staropramen&lt;/a&gt;
we chatted about: social software, the challenges facing organisation
and employees, the central importantance of people at all stages of
collaborative/KM projects, the roles of blognets, &lt;a href="http://www.headshift.com/work/proj.cfm"&gt;projects&lt;/a&gt; they are working on, &lt;a href="http://www.foaf-project.org/"&gt;FOAF&lt;/a&gt; (esp. how we need to be careful with what we infer from the data), &lt;a href="http://www.sysval.org/"&gt;metavalues&lt;/a&gt;, &lt;a href="http://www.linkedin.com/"&gt;LinkedIn&lt;/a&gt;, &lt;a href="http://matt.blogs.it/2003/06/19.html#a956"&gt;Dave Snowden&lt;/a&gt;, &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;, &lt;a href="http://www.purl.org/NET/ENT/1.0/"&gt;ENT 1.0&lt;/a&gt;, &lt;a href="http://blogtalk.net/"&gt;BlogTalk 2.0&lt;/a&gt;, the &lt;a href="http://topicexchange.com/t/blogwalk/"&gt;BlogWalkers&lt;/a&gt;, Vienna, services vs. products, and a host of other topics.&lt;br&gt;
&lt;br&gt;
I look forward to talking to Lee &amp; co. again in the near future.&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002276.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Tracking ENT support</title>
      <pubDate>Wed, 09 Jun 2004 11:21:27 +0100</pubDate>
      <description>I've just made a minor change to the &lt;a href="http://www.purl.org/NET/ENT/1.0/"&gt;ENT 1.0 spec&lt;/a&gt; to add an &lt;a href="http://www.purl.org/NET/ENT/1.0/index.html#implementations"&gt;implementations section&lt;/a&gt;.  Obviously I've listed &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;
as the first implementation would like to gather together references to
anyone who has supported the format in some way.  So, if you know
of any software or service which is supporting, or working on
supporting, ENT please let me know so that I can add it to the spec
document.&lt;br&gt;
&lt;br&gt;
Update: &lt;a href="http://www.myelin.co.nz/post/"&gt;Phil Peasons&lt;/a&gt; &lt;a href="http://topicexchange.com/"&gt;Internet Topic Exchange&lt;/a&gt;, of course!&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002308.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title></title>
      <pubDate>Mon, 05 Jul 2004 22:15:06 +0100</pubDate>
      <description>In &lt;a href="http://www.blogtalk.net/"&gt;BlogTalk&lt;/a&gt; 2.0 &lt;a href="http://randgaenge.net/"&gt;Thomas&lt;/a&gt;
&amp; crew have, once again, brought together a lot of interesting
people &amp; wherever possible conversations are flourishing as
evidenced by tonights get together.  It was good to meet &lt;a href="http://www.dijest.com/aka/"&gt;Phil&lt;/a&gt; again after a year and to meet &lt;a href="http://radio.weblogs.com/0100875/"&gt;Mikel&lt;/a&gt; for the first time, especially as his talk prompted lots of interesting ideas we might look at for &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector&lt;/a&gt;.  After a day where I had felt very tired and jaded I found the atmosphere quite reviving.&lt;br&gt;
&lt;br&gt;
I had the pleasure of dining with &lt;a href="http://paolo.evectors.it/"&gt;Paolo&lt;/a&gt;, &lt;a href="http://www.markbernstein.org/"&gt;Mark Bernstein&lt;/a&gt;, &lt;a href="http://www.sumofmyparts.com/blog/"&gt;Stephanie Hendrick&lt;/a&gt;, and &lt;a href="http://blog.humlab.umu.se/therese"&gt;Therese Örnberg&lt;/a&gt;. 
Mark gave a very interesting keynote this morning which provoked lots
of questions for me.  Stephanie &amp; Therese gave, I think, the
most stylish presentation of the day (including an amusing near-death
audioblog to end) and their discussion of presence and spaces was
stimulating.  From my perspective a happy coincidence that we all
ended up together.  We had an interesting discussion about a range
of topics spanning language, blogging, literary discourse, topics,
flame wars, comments &amp; trackbacks, software tools and how you build
them, tinderbox, Dave Allen, and test first development.&lt;br&gt;
&lt;br&gt;
Taking antibiotics means I cannot drink alchohol so my opinions whilst
maybe better formed were far less robust than usual &amp; I was open to
colonization ;-)  I got persuaded that comments are bad and that
even trackback requires considerable architectural revision to work
properly.  Mark's suggestion of making trackback default to being
private (i.e. you get a file of trackbacks and you decide what, if
anything, to do with them) seems to be a good one.  I think this
can be assisted by some sort of intelligent filtering of trackback
contents &amp; authorship to help you decide about those you do &amp;
don't want to handle.  I think emulating the LinkedIn
FOAFOAFOAFOAF network model could be useful in this regard.&lt;br&gt;
&lt;br&gt;
Also, based on comments by Stephanie and Mark, I have finally concluded that I must do something in K-Collector for the &lt;a href="http://blog.mathemagenic.com/"&gt;Lilia's&lt;/a&gt; and &lt;a href="http://www.mcgeesmusings.net/"&gt;Jim McGee's&lt;/a&gt; of this world who used (and maybe still cling to) &lt;a href="http://www.google.com/search?num=20&amp;hl=en&amp;lr=lang_en&amp;ie=UTF-8&amp;safe=off&amp;c2coff=1&amp;q=livetopics&amp;btnG=Search"&gt;liveTopics&lt;/a&gt;. 
I think that part of my problem has been misunderstanding where they
are coming from.  liveTopics, for me, was a stepping stone towards
a larger vision which, at that time, I couldn't achieve.  But for
them it was actually what they were looking for.  No wonder then
that I've had a hard time convincing them that K-Collector is better.&lt;br&gt;
&lt;br&gt;
I haven't quite worked out the answer yet but I think it may be as
simple as offering some kind of discriminator where you can choose
whether K-Collector should default to showing you only your own work,
or the work of the community as a whole.  We may even have enough
smarts in the database to do this without requiring additional work but
I'll have to get some clear space (i.e. after &lt;a href="http://stes.evectors.com/"&gt;STES&lt;/a&gt;) to think this through properly.&lt;br&gt;
</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002390.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Visualizing concepts in weblogs</title>
      <pubDate>Tue, 06 Jul 2004 13:10:30 +0100</pubDate>
      <description>&lt;a href="http://anjo.blogs.com/"&gt;Anjo Anjewierden&lt;/a&gt; &amp; &lt;a href="http://blog.mathemagenic.com/"&gt;Lilia&lt;/a&gt;
are demonstrating a very interesting
tool for visualizing conceptual relationships within weblogs.&amp;nbsp; It
uses technology similar, but more advanced, to K-Collector for
analyzing the content of weblog posts and drawing out concepts which
can be analyzed and displayed as a network so that you can explore the
relationships.&amp;nbsp; It also allows comparison of terms between
different weblogs.&lt;br&gt;
&lt;br&gt;
Very intriguing!&lt;br&gt;

</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002404.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>DelphiGroup: Making the case for taxonomy</title>
      <pubDate>Mon, 16 Aug 2004 11:56:57 +0100</pubDate>
      <description>I'm reading an excellent report from &lt;a href="http://www.delphigroup.com/"&gt;Delphi Group&lt;/a&gt; called Information Intelligence: &lt;i&gt;Content Classification and the Enterprise Taxonomy Practice&lt;/i&gt; (see &lt;a href="http://www.delphigroup.com/coverage/taxonomy.htm"&gt;here&lt;/a&gt; for a download link).  The gist of the report is that, for enterprises, search is not enough.&lt;br&gt;
&lt;br&gt;
The report makes the case that whilst search technology has improved a
lot in recent years, and continues to improve, the majority of
professionals still find it an unsatisfactory way to work and often
spend in the region of 20% of their time searching for
information.  Often cited problems were constantly changing
information and a lack of precision about what they were looking
for.  The report then makes a case that introducing taxonomy based
services can significantly improve performance and save money by eating
into that 20%.&lt;br&gt;
&lt;br&gt;
Whilst the report is funded by a number of companies with a vested
interest in taxonomy (for example Autonomy or Verity) the case seems to
be well made off the back of a credible piece of research (which is a
follow-up to similar research done last year).&lt;br&gt;
&lt;br&gt;
My summary:&lt;br&gt;
&lt;ul&gt;
  &lt;li&gt;82% of users do not have access to a centralized point of search &amp; information across information systems&lt;/li&gt;
  &lt;li&gt;The provision of a singular navigational front end (e.g.
taxonomy) and omnipresent search tool that collectively aggregate
disparate content resources, can, from an end-user perspective, deliver
the simple single point of access that many users strive for.&lt;/li&gt;
  &lt;li&gt;Lack of organisation of information is the number one problem in information management &amp; retrieval.&lt;/li&gt;
  &lt;li&gt;If professionals are spending 20% of their time (or more) looking
for information then this results in an opportunity cost &amp;
represents a runaway expense item in many organisations.&lt;/li&gt;
  &lt;li&gt;Keyword search assumes you know what you are looking for &amp; that it an often erroneous assumption.&lt;/li&gt;
  &lt;li&gt;75% of people surveyed during a Yahoo market research project preferred browsing to searching.&lt;/li&gt;
  &lt;li&gt;In some instances it is easier to discover information about a
particular subject if you see it in the context of related
thought.  Browsing encourages associative thought.&lt;/li&gt;
  &lt;li&gt;The availablity of taxonomy eliminates the need for the researcher to completely understand the subject before issuing a query.&lt;/li&gt;
  &lt;li&gt;Browsing via a taxonomy in essence provides an education on the
subject and lends insight into the issues or facets of the subject.&lt;/li&gt;
  &lt;li&gt;The number one source of frustration with search of on-line
content is the fact that the content they search for is constantly
changing, which both frustrates the user and reduces the effectiveness
of simple search.&lt;/li&gt;
  &lt;li&gt;Use of a taxonomy can provide a dynamic bookmark so to speak, a
one-stop-shopping guide to all relevant content on a subject. 
Return to a subject node exposes the latest and complete collection of
content about that subject area.  This addresses the number one
cause of frustration, the dynamic, volatile nature of information
sources.&lt;/li&gt;
  &lt;li&gt;Navigation of a well-designed interface to information on a web
site/portal automatically directs the researcher to other relevant
topics.&lt;/li&gt;
  &lt;li&gt;The tagging effort represents another process that a business
must undertake in order to obtain the benefits of a taxonomy.  In
some cases this could be done manually.  But this approach is not
easily scalable.&lt;/li&gt;
  &lt;li&gt;Will authors be willing or available to perform this classification manually?&lt;/li&gt;&lt;li&gt;68%
concur that the process of locating &amp; retrieving the information
needed to effectively execute their jobs is difficult and time
consuming.&amp;nbsp; Not a single respondent strongly disagreed with this
statement.&lt;/li&gt;
  &lt;li&gt;Whilst users see some improvement in information retrieval over
the last 2 years, their attitude towards its level of difficulty
remained virtually the same.&lt;/li&gt;
  &lt;li&gt;Respondents overwhelmingly pointed to the fact that business content is constantly changing and has to be continually relocated.&lt;/li&gt;
  &lt;li&gt;Findings pointed more towards the speed and ease of use of
retrieval environments and less to effectiveness, as the primary point
of pain amongst todays business people.&lt;br&gt;
  &lt;/li&gt;

&lt;/ul&gt;
I think this report is very well worth reading to anyone interested in
search, taxonomy, or knowledge organisation.  Of course I too am baised because I think &lt;a href="http://www.evectors.com/itkcollector/"&gt;K-Collector's&lt;/a&gt; integrated approach addresses a number of the concerns raised by this report.&lt;br&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002446.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
  </channel>
</rss>

	</div>
</div>
<div id="footer">
	<div class="info">
Copyright 2006 Matt Mower -- <a href='http://squib.rubyforge.org/'>Squib</a> Version 0.4.0 (Release 282)&nbsp;&nbsp;Updated: 19/01/2006 18:52
	</div>
</div>
</div>
</body>
</html>