<!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 livetopics</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic livetopics</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></title>
      <pubDate>Tue, 07 May 2002 17:48:58 +0100</pubDate>
      <description>&lt;A href="http://www.quotationspage.com/quotes.php3?author=Ralph+Waldo+Emerson"&gt;Ralph Waldo Emerson&lt;/A&gt;. "Don't waste yourself in rejection, nor bark against the bad, but chant the beauty of the good." [&lt;A href="http://www.quotationspage.com/mqotd.html"&gt;Motivational Quotes of the Day&lt;/A&gt;]</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000001.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics</title>
      <pubDate>Fri, 21 Jun 2002 17:32:13 +0100</pubDate>
      <description>&lt;P&gt;I haven't posted much the last couple of days because I've been working hard on my latest Radio tool.&amp;nbsp; It's called &lt;FONT color=red&gt;liveTopics&lt;/FONT&gt; and you can see the results on this page.&amp;nbsp; Some of the postings have a new Topics: section under them with links from various topics that the postings are related to.&lt;/P&gt;
&lt;P&gt;Each link goes to a central Topic &lt;EM&gt;Table of Contents&lt;/EM&gt; for my weblog.&amp;nbsp; Where you can see all the postings related to a particular topic grouped together.&lt;/P&gt;
&lt;P&gt;The tool also provides automatic generation of META tags with keywords and a "what i'm talking about" banner showing the topics associated with recent postings.&lt;/P&gt;
&lt;P&gt;It should start being tested in the next couple of days and, if all goes well,&amp;nbsp;I hope to release it next week.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000029.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics progress</title>
      <pubDate>Mon, 24 Jun 2002 23:33:08 +0100</pubDate>
      <description>&lt;P&gt;Once again I'm neglecting all other interests in the rush to make liveTopics a workable tool for Radio listeners.&amp;nbsp; I'm learning what a struggle it is to debug problems on an unfamiliar OS over a 4,000 mile and 5 hours gap.&amp;nbsp; Maybe I should just write better code, it'll be easier in the long run!&lt;/P&gt;
&lt;P&gt;The good news is that two people now seem able to use liveTopics and hopefully by the end of play tomorrow there will be four.&amp;nbsp; If we don't find any more serious bugs&amp;nbsp;then I am on schedule to release version 1.0 at the end of the week.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000036.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Categories, topics &amp; audiences</title>
      <pubDate>Tue, 25 Jun 2002 12:39:37 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0108019/2002/05/20.html#a55"&gt;Blog Notes 4: Categories&lt;/A&gt;. 
&lt;P&gt;No Audience is Interested in Everything You Produce&lt;/P&gt;
&lt;P&gt;XML gives Weblogs the capacity to be organized into categories. It's good news and bad. When authoring an article (or one of those littler bloglets), the author is confonted immediately with a series of usability questions like:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If I put this piece in several categories, does that reduce the meaning of each category? 
&lt;LI&gt;If the piece is on the home page and in a category, why would anyone ever go to both? 
&lt;LI&gt;If the piece is only in a category and not on the home page, how does anyone know? 
&lt;LI&gt;If the piece is only on the home page, what are categories for?&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0108019/"&gt;5th Constituency&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;» Another interesting piece.&amp;nbsp; I heartilty concur.&lt;/P&gt;
&lt;P&gt;My own take on categories is that they are difficult to use.&amp;nbsp; I currently define six categories including the &lt;EM&gt;Home Page&lt;/EM&gt;.&amp;nbsp; They are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;home page&lt;/LI&gt;
&lt;LI&gt;learning&lt;/LI&gt;
&lt;LI&gt;community&lt;/LI&gt;
&lt;LI&gt;personal&lt;/LI&gt;
&lt;LI&gt;technology&lt;/LI&gt;
&lt;LI&gt;tuning&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;My guess is that only "home page" and "tuning" are separably useful.&amp;nbsp; I do put items in the other categories but I suspect no-one would ever subscribe to them rather than the "home page."&amp;nbsp; (Assuming you wanted to subscribe at all!)&lt;/P&gt;
&lt;P&gt;This was really my reason for developing the liveTopics tool.&amp;nbsp;&amp;nbsp; My problem with categories is that they are not granular enough.&amp;nbsp; "tuning" works as a category because I only use that for discussing Radio development work which is, for the most part, orthoganol to what I'm talking about normally.&lt;/P&gt;
&lt;P&gt;Using liveTopics I can associate a number of individual topic references to each post (as I have done with this one).&amp;nbsp; This can be used to determine what I'm talking about and by using the topic table of contents what else I've said about a particular topic.&amp;nbsp; Where this will really score though, to my mind, is when you and I can filter each others RSS feed based on the topics we reference.&lt;/P&gt;
&lt;P&gt;Categories are dead!&amp;nbsp; Long live topics!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000046.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Classification schemes</title>
      <pubDate>Thu, 27 Jun 2002 14:56:21 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.steptwo.com.au/columntwo/archives/000030.html"&gt;Classification schemes&lt;/A&gt;. I've just stumbled across a paper on faceted classification of information, which talks about applying multiple sets of indexes to [&lt;A href="http://www.steptwo.com.au/columntwo/"&gt;Column Two&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; Note to self: Read this paper.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000053.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Bringing topics to RSS</title>
      <pubDate>Sun, 30 Jun 2002 10:10:55 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.iaslash.org/node.php?id=4523"&gt;Bringing metadata back into RSS with subject taxonomies&lt;/A&gt;. I hope to be able to spend time experimenting with XML again after a few projects I'm working on settle down. First on my plate will be to read more about how to bring &lt;A href="http://www.xml.com/pub/a/2001/05/02/semanticwebsite.html"&gt;subject-headings/topics into RSS&lt;/A&gt;. Specifically, I think &lt;A href="http://www.topicmaps.org/xtm/index.html"&gt;XTM for Topic Maps&lt;/A&gt;, the &lt;A href="http://groups.yahoo.com/group/rss-dev/files/Modules/Proposed/mod_taxonomy.html"&gt;RSS taxonomy and Dublin Core modules&lt;/A&gt;, and Peter's &lt;A href="http://xfml.org/"&gt;XFML&lt;/A&gt; are where I am going to be spending my time at first. [&lt;A href="http://www.iaslash.org/"&gt;ia/ - news for information architects&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; Serendipity!&lt;/P&gt;
&lt;P&gt;I'm also interested in how to add topic-based metadata to RSS feeds.&amp;nbsp; I'd come across XTM a while back but not had an immediate use for it.&amp;nbsp; Time to start reading I guess.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000062.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics progress</title>
      <pubDate>Sat, 06 Jul 2002 22:41:21 +0100</pubDate>
      <description>&lt;P&gt;Only a week after I had hoped to release version 1.0 of liveTopics and I'm nearly there.&lt;/P&gt;
&lt;P&gt;I've had a lot of good feedback from uber-testers &lt;FONT face=Verdana,Geneva,Arial,Helvetica,Sans-Serif color=blue&gt;Marc Barrot&lt;/FONT&gt; and &lt;FONT face=Verdana,Geneva,Arial,Helvetica,Sans-Serif color=blue&gt;Jack Mancilla&lt;/FONT&gt;.&amp;nbsp; This thing should be pretty well shaken out when it arrives.&lt;/P&gt;
&lt;P&gt;The basic functionality is now all in place.&amp;nbsp; You can successfully add topics to posts, have them displayed with the post and traverse the weblog using the Topic Table of Contents (TTOC).&lt;/P&gt;
&lt;P&gt;The TTOC, for example &lt;A href="http://radio.weblogs.com/0107808/outlines/topics/allTopics.opml#liveTopics"&gt;Curiouser and curiouser!&lt;/A&gt; shows every topic defined in the weblog.&amp;nbsp; For each topic it lists the weblog posts associated with that topic, in chronological order.&amp;nbsp; Each of these postings in turn lists the other topics associated with that particular posting.&amp;nbsp; The end result is a very easy way to traverse the weblog following &lt;EM&gt;threads of thought&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;Things that are in the pipeline just past v1.0:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Exporting topic information in your RSS stream. &lt;/LI&gt;
&lt;UL&gt;
&lt;LI&gt;Clever aggregators will be able to use this topic information to rank &amp; prioritize postings in your news view.&lt;/LI&gt;&lt;/UL&gt;
&lt;LI&gt;Topic Mining&lt;/LI&gt;
&lt;UL&gt;
&lt;LI&gt;Quickly and easily add topic information to&amp;nbsp;archive postings&lt;/LI&gt;&lt;/UL&gt;
&lt;LI&gt;Sharing topics 
&lt;UL&gt;
&lt;LI&gt;Your topics will be published as &lt;A href="http://www.topicmaps.org/xtm/1.0/"&gt;XTM&lt;/A&gt; topic maps. 
&lt;LI&gt;Subscript to other users &lt;EM&gt;&lt;STRONG&gt;topic rolls&lt;/STRONG&gt;&lt;/EM&gt; and be able to use their topics as well&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Please let me know of any other ideas you would like to see implemented.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000104.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>TopicRolling 101</title>
      <pubDate>Tue, 09 Jul 2002 20:56:58 +0100</pubDate>
      <description>&lt;P&gt;A feature that I have planned for the next release of liveTopics (the finishing touches go on the 1.0 release this week, for definite) is the topicRoll.&lt;/P&gt;
&lt;P&gt;In the same way as a blogroll represents your subscription to other what other people are writing, the topicRoll represents your subscription to what other people are writing about -- &lt;EM&gt;their topics&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;Whenever you add a topic to a post it is added to your topicRoll and (optionally)&amp;nbsp;published automatically to your weblog.&amp;nbsp;&amp;nbsp; In turn you can subscribe to as many other topicRolls as you like.&amp;nbsp; This means that as soon as someone uses a new topic, it is automatically added to the topics that your copy of liveTopics has ready for you to use.&amp;nbsp; In the same way other users can see &amp; re-use the topics you are using.&lt;/P&gt;
&lt;P&gt;When combined with the idea of topicMiner (also due in version 1.5) this will allow you to thread together existing archived discussions in a completely new way.&amp;nbsp; Mining topics allows you to find existing topics in archived posts.&amp;nbsp; You will be able to mine other peoples topics from your own posts and vice verca.&lt;/P&gt;
&lt;P&gt;I'm hoping this will enable some interesting cross-blog exchanges.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000141.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Splitting topics</title>
      <pubDate>Tue, 09 Jul 2002 22:28:55 +0100</pubDate>
      <description>&lt;P&gt;The topics being used in liveTopics now are likely, if you're like me, to be quite simple.&amp;nbsp; Usually one word, or two words joined with a hyphen.&amp;nbsp; This is fine when you're blogging alone.&lt;/P&gt;
&lt;P&gt;However in preparation for adding topicRolls where you can share your topics with others it becomes a little more complicated.&amp;nbsp; Where I might be talking about aids in the sense of AIDS you might be talking about hearing aids.&lt;/P&gt;
&lt;P&gt;It seems sensible to have some kind of scheme for allowing topics to crop up in different contexts:&amp;nbsp;"aids with respect to deafness" versus "AIDS as a disease" and so on.&amp;nbsp;&amp;nbsp; I've written them in this rather stilted way to avoid introducing a syntax too early.&lt;/P&gt;
&lt;P&gt;This will inevitably complicate the interface a little.&amp;nbsp; However it may also make it simpler to use.&amp;nbsp; At the moment the drop-down for selecting pre-existing topics fills up pretty quickly.&amp;nbsp; Selecting a "topic theme" might drastically reduce the choices to be waded through looking for the right topic.&lt;/P&gt;
&lt;P&gt;I'd welcome feedback...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000142.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>More on liveTopics</title>
      <pubDate>Wed, 10 Jul 2002 21:51:52 +0100</pubDate>
      <description>&lt;P&gt;I gave an initial pitch of some of my ideas today.&amp;nbsp; Not a pitch that I would like to give to an objective audience but, then, this is only my second day &lt;A href="http://radio.weblogs.com/0107808/2002/07/09.html#a179"&gt;&lt;FONT size=+0&gt;off the job&lt;/FONT&gt;&lt;/A&gt;!!&lt;/P&gt;
&lt;P&gt;I was trying to show how &lt;FONT color=blue&gt;liveTopics&lt;/FONT&gt; and &lt;FONT color=blue&gt;blogPlex&lt;/FONT&gt; fit together.&lt;/P&gt;
&lt;P&gt;liveTopics really started life as a bootstrap technology for the blogPlex.&amp;nbsp; blogPlexing depends upon being able to extract meaningful information from what people say on their weblogs.&amp;nbsp; Until such time as technologies like Cyc or Summarizer (see Share in the sidebar) can deliver the goods I needed something else.&amp;nbsp; Hence liveTopics was born to allow you to annotate your posts with descriptive concepts.&amp;nbsp; From a very simple original concept it has taken on a life of its own which is kind of cool.&lt;/P&gt;
&lt;P&gt;There are two steps on the way to blogPlex that I think are worth sharing.&amp;nbsp; The first is topicRolling which I have discussed in another &lt;A href="http://radio.weblogs.com/0107808/2002/07/09.html#a181"&gt;recent post&lt;/A&gt;.&amp;nbsp; Briefly topicRolling allows you to publish your topics &amp; subscribe to the topics used by others.&amp;nbsp; This allows a group of people to develop a shared conceptual vocabulary or &lt;FONT color=red&gt;BlogSpeak&lt;/FONT&gt;.&lt;/P&gt;
&lt;P&gt;The second is the super-blog.&amp;nbsp; This was really &lt;A href="http://www.wwpp.org/"&gt;Jack Foster Mancilla's&lt;/A&gt; idea.&amp;nbsp; This is an extension of the Blog Topic Table of Contents (TTOC) idea which will be familiar if you click through any of the topic links on my page (or click &lt;A href="http://radio.weblogs.com/0107808/outlines/topics/allTopics.html"&gt;here&lt;/A&gt;).&amp;nbsp;&amp;nbsp; At the moment the TTOC is an individual affair, however pretty soon I am to provide the ability for a group of people to create a super-blog together.&lt;/P&gt;
&lt;P&gt;In the same way that the TTOC now lists each of an individuals posts under a topic, the super-blog will list the posts of every member creating a way to see what each member of the group has posted regarding specific concepts.&amp;nbsp; This makes topicRolling very important.&amp;nbsp; We will also need tools to support the merging and grouping of topics into &lt;FONT color=red&gt;&lt;A href="http://radio.weblogs.com/0107808/2002/07/09.html#a182"&gt;topicThemes&lt;/A&gt;&lt;/FONT&gt;&lt;FONT color=black&gt;.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;My view at the moment is rather than embarking on a massive project to create some kind of control language or standardized vocabulary that we allow Darwinian pressures to select topics.&amp;nbsp; As has been written elsewhere people will gravitate towards "good" topics and abandon the bad (and there will be tools to help the losers graciously migrate).&amp;nbsp;&amp;nbsp; The pressure will come from the other users of the plex, in order to be listed you have to use the right topics.&lt;/P&gt;
&lt;P&gt;I can imagine situations where two similar topics will grow equal in size.&amp;nbsp; Thats okay.&amp;nbsp; Clever software can work out that they are synonymous by examing their associations with other topics.&amp;nbsp; And the use of topicThemes&amp;nbsp;will help to prevent unnecessary isolation.&lt;/P&gt;
&lt;P&gt;And then we reach the &lt;FONT color=blue&gt;blogPlex&lt;/FONT&gt; itself.&amp;nbsp; At the moment I envisage this as a service subscribed to many blogs or klogs.&amp;nbsp; Using the data in each along with the topical metadata to create profiles of bloggers and kloggers.&lt;/P&gt;
&lt;P&gt;The value of the profiles is that they will allow the blogPlex service to match up bloggers who are writing about similar concepts - who are not already linking to each other.&amp;nbsp; This is a key point because it is this that enables &lt;STRONG&gt;new&lt;/STRONG&gt; communities to form.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000159.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>The Tao of Topic Maps</title>
      <pubDate>Wed, 10 Jul 2002 22:30:08 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.ontopia.net/topicmaps/materials/tao.html"&gt;The TAO of Topic Maps&lt;/A&gt;. &lt;A href="http://www.ontopia.net/topicmaps/materials/tao.html"&gt;The &lt;ACRONYM title="Topics, Associations, and Occurrences"&gt;TAO&lt;/ACRONYM&gt; of Topic Maps&lt;/A&gt; introduces &lt;A href="http://www.topicmaps.org/"&gt;topic maps&lt;/A&gt;, a new &lt;A class=acronym title="International Organization for Standardisationclick to visit the ISO web site" href="http://www.iso.ch/"&gt;ISO&lt;/A&gt; standard for describing knowledge structures and associating them with information resources. [&lt;A href="http://home.netcom.com/~luskr/weblog/radio/categories/kLogs/"&gt;Ron Lusk: Ron's K-Logs&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;» Wow cool.&amp;nbsp; More reading for tomorrow!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000167.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/cms.xml" ent:id="cms" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>TAO of topic maps</title>
      <pubDate>Mon, 15 Jul 2002 21:52:39 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.steptwo.com.au/columntwo/archives/000090.html"&gt;The TAO of Topic Maps&lt;/A&gt;. Steve Pepper has written a succinct introduction to topic maps, titled The TAO of Topic Maps. To quote Steve: Topic [&lt;A href="http://www.steptwo.com.au/columntwo/"&gt;Column Two&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; I finally got a chance to read this paper on the tube going to London today.&amp;nbsp; A key paragraph that leapt out at me was:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;"&lt;FONT face="Courier, Monospace"&gt;But knowledge is fundamentally different from information: the difference is that between knowing a thing versus simply having information about it.&amp;nbsp; And if, as one writer claims, 'knowledge management covers three main knowledge activities: generation, codification, and transfer', then topic maps can be regarded as the standard for codification that is the necessary prerequisite for the development of tools that assist in the generation and transfer of knowledge.&lt;/FONT&gt;"&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;In general the topic maps approach seems very sound to me with very laudible goals.&amp;nbsp; It also dovetails nicely with a lot of my liveTopics efforts and lends some new and credible directions.&lt;/P&gt;
&lt;P&gt;For example I have already implemented code in the liveTopics plugin to export the topical references in the weblog as an XTM topic map.&amp;nbsp;&amp;nbsp; Additionally my idea for &lt;EM&gt;topic themes&lt;/EM&gt; seems almost identical to the concept of themes in the document.&lt;/P&gt;
&lt;P&gt;It also highlights some things I should address.&amp;nbsp; The idea of synonyms and homynyms are clearly important once people start sharing their topics (via topicRolls).&amp;nbsp; It may also be useful to allow people to define their own glossaries (maybe integrated with the existing Radio glossary).&amp;nbsp; And in order to generate occurrence data the permalinks of each posting should be used as topic references to that posting.&lt;/P&gt;
&lt;P&gt;All in all a useful guide to the capabilities of topic maps.&amp;nbsp; What is required now is another work building upon this that details some of the applications that topic maps will enable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000200.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-log.xml" ent:id="k-log" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics 1.0 release iminent</title>
      <pubDate>Wed, 17 Jul 2002 02:01:56 +0100</pubDate>
      <description>&lt;P&gt;Okay I've said it before, but barring major incident liveTopics should be released before the end of the week.&amp;nbsp; My current target is thursday since I move house on Friday and I'm not sure what my connectivity is after that.&amp;nbsp; Or, maybe that's not a good time to release... :)&lt;/P&gt;
&lt;P&gt;Oh well, damn the torpedo's, full steam ahead!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000238.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/gurteen.xml" ent:id="gurteen" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge-management.xml" ent:id="knowledge-management" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Let's see what's on the slab...</title>
      <pubDate>Thu, 08 Aug 2002 20:52:14 +0100</pubDate>
      <description>&lt;P&gt;Well in the last couple of days I have been working hard on the liveTopics 1.0 release.&amp;nbsp; It's so close I can almost feel it.&amp;nbsp; We're testing and hopefully will have the kinks worked out in the next couple of days then I can finally get this sucka out the door.&lt;/P&gt;
&lt;P&gt;Also I'm really besotted with TrackBack but haven't seen it work the way I would like yet.&amp;nbsp; So I've rolled a TrackBack server in Frontier that comes with a Radio client.&amp;nbsp; The two communicate with a simple XML-RPC interface that would allow any klogging system to join in.&lt;/P&gt;
&lt;P&gt;At the moment the Radio client automatically harvests each posting for links (when you submit it) and automagically pings each one.&amp;nbsp; The ping contains the permalink for the post, the Url of your weblog, the title of the post, your name &amp; email address.&amp;nbsp; But you can drop most of this information you don't want to pass it.&amp;nbsp; I guess some people will also want fine-grained control over what they ping.&amp;nbsp; That shouldn't be too hard.&lt;/P&gt;
&lt;P&gt;Along with this are some macros to show your TrackBack information against each item.&lt;/P&gt;
&lt;P&gt;At the moment the server is hosted on my laptop which isn't ideal but is good enough for testing.&amp;nbsp; The next job is to find a better host and then look at adding a simple federation mechanism.&amp;nbsp; That would allow lots of different people to provide TrackBack servers and share the results.&lt;/P&gt;
&lt;P&gt;More on this later.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000265.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/collaboration.xml" ent:id="collaboration" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/groove.xml" ent:id="groove" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Integrating klogs with Big-KM</title>
      <pubDate>Thu, 08 Aug 2002 23:08:31 +0100</pubDate>
      <description>&lt;P&gt;In order for klogging to be successfully I think it is going to have to come to an understanding with Big-KM.&lt;/P&gt;
&lt;P&gt;Example:&amp;nbsp; BigCo has invested half a million dollars in a big knowledge management system for their world-wide operations.&amp;nbsp; This kind of investment can become a lode-stone around any other systems neck.&amp;nbsp; For klogging to thrive here it is going to have to integrate.&lt;/P&gt;
&lt;P&gt;Here's one idea I have for how this could work.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Extend Big-KM System-X so that it can aggregate RSS feeds like Radio, MT and others do now.&lt;/LI&gt;
&lt;LI&gt;Extend your klogging software to allow per-post meta data.&amp;nbsp; (liveTopics does this for Radio)&lt;/LI&gt;
&lt;LI&gt;For each project in System-X define a set of topics that will act as trigger phrases for that project&lt;/LI&gt;
&lt;LI&gt;Get the kloggers to use those topics when they want to involve a post in a particular project&lt;/LI&gt;
&lt;LI&gt;Now subscribe System-X to every klog in the organization and watch as it indexes and archives all that information.&amp;nbsp; Each project grabbing only those postings that are appropriate (by use of the trigger phrases)&lt;/LI&gt;
&lt;LI&gt;This means that the klogs add value to the big-KM system.&amp;nbsp; Suddenly it doesn't just have the dry dusty project documention, but all the live vibrant stuff that people are really doing!&lt;/LI&gt;
&lt;LI&gt;Now extend System-X to generate a per-project RSS feed.&lt;/LI&gt;
&lt;LI&gt;If I am on the project I can subscribe to this feed.&amp;nbsp; Now instead of receiving email from System-X or having to go to an arbitrary web page, I get all the "official" project stuff (new documents, forms etc...) delivered in my RSS stream.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Closing the loop between the big-KM and the klog so that they both add value to each other.&lt;/P&gt;
&lt;P&gt;Just an idea....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000277.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/pkp.xml" ent:id="pkp" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/radio.xml" ent:id="radio" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/security.xml" ent:id="security" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics and categories</title>
      <pubDate>Sat, 10 Aug 2002 13:57:09 +0100</pubDate>
      <description>&lt;P&gt;The the real use of categories to my mind&amp;nbsp;is to allow upstreaming to multiple locations.&amp;nbsp; That way I can have my public weblog (and maybe a salon blog too like &lt;A href="http://blogs.salon.com/0001048/"&gt;Marc Barrot&lt;/A&gt;) as well as a number of private klogs.&lt;/P&gt;
&lt;P&gt;I would still like to be able to use liveTopics when posting to a private klog, but the topics perhaps should not be shared or, if they are shared, it should be done in an intelligent way.&amp;nbsp; Specifically each category needs it's own Table of Contents where the URL's to posts are not cross-referenced.&lt;/P&gt;
&lt;P&gt;I'll have to figure out how to do this and it probably won't be easy.&lt;/P&gt;
&lt;P&gt;Of course a better solution would be for Radio to natively support the idea of mutli-site operations.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000299.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/business.xml" ent:id="business" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/corruption.xml" ent:id="corruption" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/enron.xml" ent:id="enron" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics license</title>
      <pubDate>Sun, 18 Aug 2002 16:13:44 +0100</pubDate>
      <description>&lt;P&gt;So I'm ready at last to release liveTopics 1.0, the last remaining task is to find the license to use.&amp;nbsp;&amp;nbsp; I want a license that allows me to release it free for personal use whilst still retaining my ability to charge businesses for it.&amp;nbsp; I want a license that allows me to publish the source&amp;nbsp;(with Radio is there any other choice?)&amp;nbsp;and encourage others to contribute, yet doesn't allow my work to be &lt;EM&gt;unfairly&lt;/EM&gt; exploited.&lt;/P&gt;
&lt;P&gt;Can anyone recommend what license I should be using?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000341.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-log.xml" ent:id="k-log" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/sfa.xml" ent:id="sfa" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics licensing. It's getting thorny</title>
      <pubDate>Tue, 20 Aug 2002 12:27:13 +0100</pubDate>
      <description>&lt;P&gt;I've been thinking about licensing and how it applies to my business, to my plans for making my living.&lt;/P&gt;
&lt;P&gt;I've used free software and appreciated it.&amp;nbsp; I've bought commerical software and been happy to do so.&amp;nbsp; I am happy to buy reasonably priced software - when I have the money.&amp;nbsp; I don't expect, or even want, all software to be free.&amp;nbsp; Now, for the first time, I am releasing software in the context of my own business, &lt;EM&gt;making a living&lt;/EM&gt;.&amp;nbsp; It colours things.&lt;/P&gt;
&lt;P&gt;My plans for liveTopics means that it will, increasingly, be relevant in an organizational context.&amp;nbsp; I anticipate a point where I could have commercial and non-commercial customers.&amp;nbsp; I want to license liveTopics appropriately but my head is getting very sore trying to work that out.&lt;/P&gt;
&lt;P&gt;I need help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000358.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/culture.xml" ent:id="culture" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/gurteen.xml" ent:id="gurteen" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge-management.xml" ent:id="knowledge-management" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/organisational-development.xml" ent:id="organisational-development" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>More on licensing</title>
      <pubDate>Tue, 20 Aug 2002 12:33:56 +0100</pubDate>
      <description>&lt;P&gt;Maybe I should just GPL liveTopics and avoid the subject of money altogether.&lt;/P&gt;
&lt;P&gt;Is there a way to make a living from software without licensing it when the source is freely available?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000361.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics to create virtual weblog channels</title>
      <pubDate>Tue, 20 Aug 2002 16:57:14 +0100</pubDate>
      <description>&lt;P&gt;Here's an idea I've been thinking about for the use of liveTopics.&lt;/P&gt;
&lt;P&gt;At the moment as author's &lt;FONT color=blue&gt;we categorize&lt;/FONT&gt; our posts for our readers.&amp;nbsp; If using default Radio by explicitly putting them into categories (or, by default, not doing so).&amp;nbsp; With liveTopics I can add some granularity to that.&amp;nbsp; But basically it doesn't have too much impact on my reader.&amp;nbsp; It also doesn't give the reader much choice.&lt;/P&gt;
&lt;P&gt;What I'd like to do is offer the reader is the chance to &lt;FONT color=red&gt;create their own categories &lt;/FONT&gt;and here's how I think it would work:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;We add a "customise this site" button that pop's up a list of all the topics available on the site.&lt;/P&gt;
&lt;P&gt;The reader can then group topics they are interested in together to create "virtual channels."&amp;nbsp; These along with the default selection are bundled up into a cookie that is stored in the readers browser (with their permission).&lt;/P&gt;
&lt;P&gt;The next time the reader visits the page they only get posts that match the selected "virtual channel."&amp;nbsp;along with&amp;nbsp;a drop-down to change channel and the customise button.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;Anybody else think this is an interesting idea?&lt;/P&gt;
&lt;P dir=ltr&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000381.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/cms.xml" ent:id="cms" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Entropy, big-KM, klogging and the wheel</title>
      <pubDate>Tue, 20 Aug 2002 19:57:17 +0100</pubDate>
      <description>&lt;A href="http://www.rolandtanglao.com/2002/08/18.html#a2630"&gt;Roland's Natural Klog Progression.&lt;/A&gt;. 
&lt;P&gt;I spoke of&amp;nbsp;&lt;A href="http://dijest.com/2002/08/13.html#a1927"&gt;four klogging roles&lt;/A&gt; last week: catalyst, coach, armorer, practice leader.&amp;nbsp;&lt;A href="http://radio.weblogs.com/0107808/2002/08/19.html#a287"&gt;Matt Mower&lt;/A&gt; advocates the the role of "Intranet Editor:"&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;Much as the users of a Wiki should occasionally re-factor pages that are becoming "busy" I think that a good intranet editor should be grooming the klogs in their organization and drawing together useful strangs to form part (or all) of the static intranet.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="http://www.rolandtanglao.com/"&gt;Roland Tanglao&lt;/A&gt; builds on this: &lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;I think &lt;A href="http://www.rolandtanglao.com/categories/radiouserland/2002/06/02.html#a2066"&gt;a natural progression for knowledge&lt;/A&gt; is: &lt;/P&gt;
&lt;P dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;OL&gt;
&lt;LI&gt;blog breaking news 
&lt;LI&gt;harvest it periodically (say weekly) into an FAQ and/or other knowledge base type of documents 
&lt;LI&gt;Put the link into a a directory that supports transclusion like Manila style directories. &lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;K-Log =&gt; (FAQ or other knowlegebase article)&amp;nbsp;=&gt; directory.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;K-Logs need to be periodically (at least once a month) harvested for content that should go into an FAQ or other knowledgebase document and links that that should go into a directory. This is the job of a K-Log editor :-)! I have been trying to do this with VanEats but after a klog gets to a certain size, it really needs to have some time set aside for it.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;Practice Leader is probably the closest to a dedicated multi-author editor. Summarizing work in a field, showing the aggregate progress and useful threads. Structuring knowledge into FAQs or other KM systems may be a natural progression, especially as klogging tools and KM tools build bridges. &lt;/P&gt;
&lt;P dir=ltr&gt;Entropy, bad. &lt;/P&gt;
&lt;P dir=ltr&gt;Fighting entropy,&amp;nbsp;expensive, slow.&amp;nbsp;&lt;/P&gt;
&lt;P dir=ltr&gt;Self-review is a powerful tool for learning. Going over my own posts for the past week, month, and quarter has shown patterns I missed, ideas I was skirting but never wrote outright. It reinforced brief social connections, blogs to which I linked to and people with whom I briefly corresponded.&amp;nbsp;It takes concentrated time and effort. It helps me to print out all the pages on my blog for that period; something about shuffling through paper. &lt;/P&gt;
&lt;P dir=ltr&gt;Folks are trying hard to automate this work. Summarizers. Cluster analysis. Text to Structure converters. Taxonomy systems. &lt;/P&gt;
&lt;P dir=ltr&gt;But the expert author of the original content is often the best judge of relevance. &lt;/P&gt;
&lt;P&gt;[&lt;A href="http://dijest.com/aka/"&gt;a klog apart&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; I think one of the things about klogs is that are no better than any other KM system when it comes to entropy.&amp;nbsp; In fact they are likely to be a hell of a lot worse -- it's just the entropy matters less.&amp;nbsp; Any information system that isn't properly maintained has the potential to quickly deteriorate into chaos.&lt;/P&gt;
&lt;P&gt;The fact is that most people don't want to have to&amp;nbsp;find just the right place to put something.&amp;nbsp; Most people aren't going to review what they have done.&amp;nbsp;&amp;nbsp; You can force this behaviour, you can encourage it.&amp;nbsp; But &lt;FONT color=blue&gt;is it really necessary that everyone has to become a librarian in order to function in a knowledge environment&lt;/FONT&gt;?&lt;/P&gt;
&lt;P&gt;My alternative is that we recognize and promote the value of good editing (and, hence, good editors).&amp;nbsp; Have an editor/practice leader to head each area whose responsibility it is to aggregate good knowledge.&amp;nbsp; Then reward them when they do it well.&amp;nbsp;&amp;nbsp; Example:&amp;nbsp; Look at the number of search engine queries for specific keywords.&amp;nbsp; Tie those keywords to projects/areas.&amp;nbsp; If the number of searches trends downwards something is working.&amp;nbsp; Okay, too simplistic? Then suggest something better!&lt;/P&gt;
&lt;P&gt;An area I have been thinking about is how I would integrate the idea of uploading files to a KM system when klogging.&amp;nbsp; One approach would be to provide some kind of clever dialogue to allow the user to specify where they want the file to end up.&amp;nbsp; That sounds like hard work for me &amp; for the user.&lt;/P&gt;
&lt;P&gt;Alternative strategy:&amp;nbsp; Allow the user to put a file in an enclosure.&amp;nbsp; Radio will upstream it to the KM server as part of the RSS feed.&amp;nbsp; The KM server will toss the file into an upload bucket in an area based upon the metadata of the post (ala liveTopics).&amp;nbsp; It's then up to the practice leader for that area to decide where the document actually belongs and move it there (or indeed if it belongs at all).&lt;/P&gt;
&lt;P&gt;Is this less efficient?&amp;nbsp; Maybe so.&amp;nbsp; Is it more effective?&amp;nbsp; I think so.&lt;/P&gt;
&lt;P&gt;Agree? Disagree?&amp;nbsp; Ideas?&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000388.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/patents.xml" ent:id="patents" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>More on licensing for liveTopics</title>
      <pubDate>Tue, 20 Aug 2002 23:18:09 +0100</pubDate>
      <description>&lt;P&gt;Here's how I'm leaning:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;I make liveTopics free software issued under the GPL.&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I can see the arguments for and against commercial licenses for the software.&amp;nbsp; But like the Zope guys I have weigh up how much license revenue I'm actually likely to generate versus the inertia that having to pay could generate.&amp;nbsp; I'm hoping to build a reputation in the KM/klogging space and liveTopics if widely accepted could be&amp;nbsp;a part of that.&amp;nbsp; I also want to take liveTopics into corporate blogging directories, topic-maps, XTM, and visualization.&amp;nbsp; I want to take it into group/shared-blogging.&amp;nbsp; I want lots of you to come along for the ride.&lt;/P&gt;
&lt;P&gt;So I think it's real values to me&amp;nbsp;are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;reputation&lt;/LI&gt;
&lt;LI&gt;a lead-in to other services&lt;/LI&gt;
&lt;LI&gt;the vision&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The other services could be support, as well as more general KM/klogging consultancy or integration work.&lt;/P&gt;
&lt;P&gt;Am I making sense?&amp;nbsp; I guess we'll know if I end up starving and homeless in 6 months time!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000401.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics license</title>
      <pubDate>Wed, 21 Aug 2002 18:10:08 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0108194/2002/08/21.html#a279"&gt;More on licensing for liveTopics&lt;/A&gt;. 
&lt;BLOCKQUOTE&gt;[&lt;A href="http://radio.weblogs.com/0107808/"&gt;Curiouser and curiouser!&lt;/A&gt;]&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I've gotta say I really love watching this process.&lt;/P&gt;
&lt;P&gt;One point of potential revenue could very well be 'corporate consulting' i.e. installation and integration. People aren't going to know what to do with liveTopics (or blogging directories, topic-maps, XTM &amp; visualization for that matter) without being pitched and well trained, and even then it's going to be difficult for them to wrap their head around the concept enough to drop it into their IT culture effectively. It's much easier from that perspective to hire the people who wrote it to come in, train IT in the installation process (or actually provide the service) and talk with the user base to bring them up to speed and show them some of the possibilities and how it "affects their day."&lt;/P&gt;
&lt;P&gt;If liveTopics is (or is going to be) that robust I think you should have no particular difficulty generating a revenue stream through such ancillary services.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0108194/"&gt;The Universal Church Of Cosmic Uncertainty&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;» Thanks for the perspective.&amp;nbsp; That's kinda what I'm looking for right now.&amp;nbsp; Well either that or "You're mad!&amp;nbsp; Mad! Mad! Mad!"&lt;/P&gt;
&lt;P&gt;I guess this will become one of those experiments that my life has now become.&lt;/P&gt;
&lt;P&gt;Exciting!&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000420.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/pingback.xml" ent:id="pingback" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Active reading with liveTopics</title>
      <pubDate>Thu, 22 Aug 2002 11:05:40 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0110772/2002/08/21.html#a155"&gt;liveTopics to create virtual weblog channels&lt;/A&gt;. 
&lt;P&gt;&lt;EM&gt;Here's an idea I've been thinking about for the use of liveTopics.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;What I'd like to do is offer the reader is the chance to &lt;FONT color=red&gt;create their own categories &lt;/FONT&gt;and here's how I think it would work:&lt;/EM&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;
&lt;P&gt;&lt;EM&gt;&lt;/EM&gt;&lt;/P&gt;&lt;EM&gt;The next time the reader visits the page they only get posts that match the selected "virtual channel."&amp;nbsp;along with&amp;nbsp;a drop-down to change channel and the customise button.&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;EM&gt;Anybody else think this is an interesting idea? &lt;/EM&gt;[&lt;A href="http://radio.weblogs.com/0107808/"&gt;Curiouser and curiouser!&lt;/A&gt;]&lt;/P&gt;
&lt;P dir=ltr&gt;It is interesting, but in my view it would be even better if we could subscribe to a RSS feed for the shared categories we like. This is a generalization of &lt;A href="http://www.highcontext.com/kmpings/"&gt;KMPings&lt;/A&gt;. The following step would be to document and interlink the shared categories in a (shared) wiki.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0110772/"&gt;Seb's Open Research&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=maroon&gt;»&lt;/FONT&gt; Agreed.&amp;nbsp; For a while now the ability to create dynamic channels from the RSS feed has been part of my plan.&amp;nbsp; RSS 0.92 already has the necessary &lt;category&gt; tag that can be co-opted to take topics instead / as well.&amp;nbsp; I've patched the Radio RSS generator to do this, but need to do some more work in terms of turning this patch into something that can be distributed in Radio.&lt;/P&gt;
&lt;P&gt;A key advantage would be the ability to have multiple RSS feeds aggregated together into a channel when they reference the same topics.&lt;/P&gt;
&lt;P&gt;However I still think there is a role for the browser view.&amp;nbsp; Despite the growing popularity of RSS I think people are still going to want to read some sites and at the moment they don't work for the reader.&lt;/P&gt;
&lt;P&gt;The way I see it is that this is a control thing in the same way that blogging itself is a control thing.&amp;nbsp; As a blogger I write what I like, that's where I get my control.&amp;nbsp; But as a reader I have no control.&amp;nbsp; I see what the writer intends (or not -- consider the font sizing issue that has been hot recently).&lt;/P&gt;
&lt;P&gt;I was just musing that it would be interesting for the reader of a site to be able to re-frame the content in a way that suited them.&amp;nbsp; But RSS does come first...&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000423.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/rant.xml" ent:id="rant" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Licensing: The final word (from me)</title>
      <pubDate>Thu, 22 Aug 2002 20:24:42 +0100</pubDate>
      <description>&lt;P&gt;Okay the GPL license is now embedded in liveTopics 1.0&lt;/P&gt;
&lt;P&gt;So far most of the comments I have received suggest that making liveTopics free software has more advantages than keeping it proprietary and trying to commercialize it.&amp;nbsp; Although the idea of money seems really great (and really remote) to me right now it's how I was leaning anyway.&lt;/P&gt;
&lt;P&gt;I'm going to sleep on it and, barring an overnight conversion or conclusive message to the contrary, I shall be releasing liveTopics 1.0 tomorrow under the GPL.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000435.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/marketing.xml" ent:id="marketing" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/selling.xml" ent:id="selling" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Tables of Contents</title>
      <pubDate>Thu, 22 Aug 2002 21:43:33 +0100</pubDate>
      <description>&lt;P&gt;As anyone who has clicked on a topic link for one of my posts recently will be aware, my Table of Contents is now pretty big.&amp;nbsp; I hadn't realised how big until someone told me it was over 600K!!&amp;nbsp; I guess if I didn't have broadband now I wouldn't have let it get this far without addressing it.&lt;/P&gt;
&lt;P&gt;My solution is to provide&amp;nbsp;2 "drivers" for building the table of contents.&amp;nbsp; A single outline driver suitable for small sites and a&amp;nbsp;mutli-outline driver suitable for larger sites.&amp;nbsp; These and other drivers can be selected using a preference (it's pretty simple to add a new driver, e.g. one for doing tables instead of outlines).&lt;/P&gt;
&lt;P&gt;The new mutli-outline driver will split the table of contents alphabetically.&amp;nbsp; This might still lead to some pages being heavier than others but is a simple strategy to implement and should spread things out better than they are at the moment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000437.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Java XML-RPC</title>
      <pubDate>Fri, 23 Aug 2002 16:25:14 +0100</pubDate>
      <description>&lt;P&gt;I've not done anything Java wise for a couple of months but, partly to keep my hand in, and partly because I think it's easier I've been thinking about using an applet or Java WebStart application for managing the topic information in liveTopics.&amp;nbsp; This leads to some questions:&lt;/P&gt;
&lt;P&gt;What's the best XML-RPC implementation for Java at the moment?&lt;/P&gt;
&lt;P&gt;For a simple API is XML-RPC a better bet than SOAP?&lt;/P&gt;
&lt;P&gt;Is it safe to use Swing in applets these days?&lt;/P&gt;
&lt;P&gt;What are the relative advantages/disadvanages of JWS over Applets?&amp;nbsp; Maybe even thinlets?&lt;/P&gt;
&lt;P&gt;And what IDE should I be using (I used to use JBuilder)&lt;/P&gt;
&lt;P&gt;Can anyone help me out?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000447.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Not quite the last word on licensing</title>
      <pubDate>Fri, 23 Aug 2002 22:54:09 +0100</pubDate>
      <description>&lt;P&gt;Not quite the last word on licensing.&lt;/P&gt;
&lt;P&gt;I've been speaking to Mark Paschal about his choice of the BSD license for Stapler.&amp;nbsp; Mark's reasons for open sourcing Stapler may, fundamentally, be more altruistic than mine but having decided to do it (open source liveTopics) I want to do it properly.&lt;/P&gt;
&lt;P&gt;They key difference as Mark explains it is that under the GPL liveTopics could not be integrated into Radio, because Radio is not itself GPL compatible.&amp;nbsp;&amp;nbsp;Indeed Mark couldn't incorporate any functionality from liveTopics into Stapler (for&amp;nbsp;example) without breaking the license.&amp;nbsp; Is that what I intended? &amp;nbsp;I'm actually wondering now whether whether it would be breaking my own license to distribute Radio &amp; liveTopics to a customer?&amp;nbsp; Would I have to require a separate download &amp; install step to comply?&lt;/P&gt;
&lt;P&gt;Since I don't think I can go back and do this again I need to get it right.&amp;nbsp; Some stuff I need to understand:&amp;nbsp; Am I bound by my own license?&amp;nbsp; Can I re-issue liveTopics later with a different license?&amp;nbsp; Can I grant exceptions to the GPL?&amp;nbsp; If so, what happens when an exception is contradictory to the GPL?&lt;/P&gt;
&lt;P&gt;Does anyone else want to weigh in on the best license to use?&amp;nbsp;&amp;nbsp; [please!]&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000454.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/community.xml" ent:id="community" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/k-log.xml" ent:id="k-log" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Klogs can  improve the value of what you write</title>
      <pubDate>Wed, 28 Aug 2002 15:27:46 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0107808/"&gt;Curiouser and curiouser!&lt;/A&gt;&amp;nbsp;in &lt;A href="http://radio.weblogs.com/0107808/2002/08/27.html#a339"&gt;There's a hole in my bucket...&lt;/A&gt;. 
&lt;P&gt;
&lt;BLOCKQUOTE&gt;&lt;FONT color=darkblue&gt;As a klogger, over the past 3 months or so, I have recorded &amp; published tens if not hundreds of thoughts.&amp;nbsp;&amp;nbsp;I doubt if I shared one&amp;nbsp;quarter of output during the last 6 years I worked at various companies.&amp;nbsp; Oh I would probably have emailed here and there, spoken up during meetings.&amp;nbsp; But I wonder just how much knowledge is being &lt;EM&gt;lost&lt;/EM&gt;, second by second, in most companies by each employee.&amp;nbsp; Then multiply up...&lt;/FONT&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;But even if they would catch those thoughts, it's going to be very difficult to find something relevant and to understand it our of the context. More or less like forum discussion: you have to follow for some time to make sense of it.&lt;/P&gt;
&lt;P&gt;Going through blog archives is not easy... So far I benefit more from the distributed dialog and from the collective filtering. So, blogs is more for sharing, rather than capturing...&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0109961/"&gt;Mathemagenic&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=maroon&gt;»&lt;/FONT&gt; I don't think this problem is necessarily inherent in blogging/klogging as practiced, more a problem in the simple calendar based access method most weblogs provide by default.&lt;/P&gt;
&lt;P&gt;But there are other options, for example a Radio weblog with &lt;FONT color=maroon&gt;liveTopics&lt;/FONT&gt;&amp;nbsp;adds another dimension for relating posts together to create a &lt;EM&gt;train of thought&lt;/EM&gt;.&amp;nbsp; You can follow a topic from a post into a table of contents where you can see other posts referencing that topic.&amp;nbsp; You can also see, for each post, other topics that were associated with it allowing you to hop from one subject of conversation to another.&lt;/P&gt;
&lt;P&gt;The next level is based upon XML topic maps (in XTM format) which I am experimenting with generating right now.&amp;nbsp; This will allow you to &lt;EM&gt;reconstruct &lt;/EM&gt;the weblog to serve different purposes and, by merging topic maps from different weblogs together, to analyse a larger conversational "space."&lt;/P&gt;
&lt;P&gt;All in all I think klogs will, ultimately,&amp;nbsp;vastly improve the ability for people to find things that are relevant and meaningful among the discourse of themselves and others.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000469.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/american-culture.xml" ent:id="american-culture" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/corruption.xml" ent:id="corruption" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>A step towards the license</title>
      <pubDate>Wed, 04 Sep 2002 10:56:45 +0100</pubDate>
      <description>&lt;P&gt;Okay I want to get the liveTopics license issue resolved once and for all.&amp;nbsp; To this end I have setup a &lt;A href="http://www.quicktopic.com/16/H/tVkeJYmT2Wr"&gt;QuickTopic&lt;/A&gt; to discuss it and hopefully reach a consensus.&amp;nbsp; If you are at all interested (even in the process of a license being worked out in the open) please join in the topic and share your views.&lt;/P&gt;
&lt;P&gt;My intention is that once an approach is decided I will use QuickTopic again to review the license text (if any one is interested to participate in that process) before issuing the final agreed license.&lt;/P&gt;
&lt;P&gt;All are welcome.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000483.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/instant-messenger.xml" ent:id="instant-messenger" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/multimedia-conversations.xml" ent:id="multimedia-conversations" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics license</title>
      <pubDate>Thu, 05 Sep 2002 22:52:57 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://radio.weblogs.com/0104487/2002/09/05.html#a288"&gt;Radio Tools Licensing&lt;/A&gt;. &lt;A href="http://radio.weblogs.com/0107808/"&gt;Matt&lt;/A&gt; is looking for the &lt;I&gt;perfect&lt;/I&gt; license model for his Radio tool. If you want to get your hands on &lt;A href="http://radio.weblogs.com/0107808/outlines/liveTopics.html"&gt;liveTopics 1.0&lt;/A&gt; before Hell freezes, you'd better join the discussion at &lt;A href="http://www.quicktopic.com/16/H/tVkeJYmT2Wr/p-1.-1"&gt;http://www.quicktopic.com/16/H/tVkeJYmT2Wr/p-1.-1&lt;/A&gt; and help Matt make up his mind fast.&amp;nbsp;[&lt;A href="http://radio.weblogs.com/0104487/2002/09/05.html#a288" target=_blank&gt;read more&lt;/A&gt;] [&lt;A href="http://radio.weblogs.com/0104487/"&gt;s l a m&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; Oh how I wish Marc was being unkind with that "Hell freezes over" remark :-)&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000496.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/dynamic-dns.xml" ent:id="dynamic-dns" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/hardware.xml" ent:id="hardware" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics Software License Agreement posted for review</title>
      <pubDate>Sun, 08 Sep 2002 07:35:29 +0100</pubDate>
      <description>&lt;P&gt;Hopefully today I've taken a positive step.&amp;nbsp; I posted in the &lt;A href="http://www.quicktopic.com/16/H/tVkeJYmT2Wr"&gt;license discussion&lt;/A&gt; at QuickTopic a draft of a license for liveTopics that covers personal use.&amp;nbsp; It won't be perfect, it may be too restrictive but it's there for you to comment on and I hope that you will.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000503.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-log.xml" ent:id="k-log" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/process-logging.xml" ent:id="process-logging" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/visibility.xml" ent:id="visibility" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics rename done</title>
      <pubDate>Sun, 08 Sep 2002 20:07:35 +0100</pubDate>
      <description>If anything appears to be messed up about my weblog it's probably to do with testing the rename topic functionality of liveTopics.&amp;nbsp; I've done quite a lot of testing today and the feature seems to be stable now.&amp;nbsp; Unfortunately I need to republish the entire weblog to clear up the mess!</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000505.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/trackback.xml" ent:id="trackback" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/trust.xml" ent:id="trust" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Analysing new topics</title>
      <pubDate>Sun, 08 Sep 2002 22:58:49 +0100</pubDate>
      <description>&lt;P&gt;I'm reading a paper [&lt;A href="http://citeseer.nj.nec.com/cache/papers/cs/1119/http:zSzzSzwww.cs.jhu.eduzSz~sheppardzSzcs.605.754zSzpaperszSzpaper3a.pdf/joachims96probabilistic.pdf"&gt;Joachims, 1996&lt;/A&gt;] about text analysis.&amp;nbsp; The idea is to produce a facility within liveTopics for suggesting topics based upon the text entered in a post.&amp;nbsp; At the moment there is a simple facility based upon a word search for existing topics, I'm keen to improve upon that in the future.&lt;/P&gt;
&lt;P&gt;Does anyone know of any good papers on this subject?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000507.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/palladium.xml" ent:id="palladium" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/pigopoly.xml" ent:id="pigopoly" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>2nd draft of liveTopics license posted</title>
      <pubDate>Mon, 09 Sep 2002 21:15:24 +0100</pubDate>
      <description>I've posted a &lt;A href="http://www.quicktopic.com/16/D/FtsR9n38BJYc4.html"&gt;2nd draft&lt;/A&gt; of the proposed "free for personal use"&amp;nbsp;liveTopics license agreement.&amp;nbsp; It's modelled philosophically after the BitKeeper license.&amp;nbsp; Hopefully the text is now clearer.&amp;nbsp; I'm really looking for comments/criticisms to surface now so that I can get this knocked out soon.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000520.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/politics.xml" ent:id="politics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/surveillance.xml" ent:id="surveillance" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>3rd draft of the license</title>
      <pubDate>Tue, 10 Sep 2002 21:12:57 +0100</pubDate>
      <description>&lt;P&gt;I've posted the 3rd draft of the liveTopics license &lt;A href="http://www.quicktopic.com/16/D/saTXuaJkyNZP.html"&gt;here&lt;/A&gt; for review.&amp;nbsp; It's nearly done I just need to know that people are comfortable with section 3 and what, if anything, I need to go in section 5.&amp;nbsp; The end is in sight (which is good because I've done a fair bit of work that I want to release).&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000533.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Beginning to market your software</title>
      <pubDate>Thu, 12 Sep 2002 09:20:32 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0107789/2002/09/11.html#a839"&gt;TidBITS: Marketing Software, Part 1&lt;/A&gt;. 
&lt;P&gt;A great article on &lt;A href="http://db.tidbits.com/getbits.acgi?tbart=06933"&gt;Marketing Software&lt;/A&gt; in todays TidBITS&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;"&lt;EM&gt;You may have an application, and it might be truly useful (rather than a candidate for MacHack), but you don't necessarily have a product or, more importantly, a solution. What's the difference? A pencil is a product, but it's not a solution.&lt;/EM&gt;"&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;A good read for anyone in the software business. Also the first time I've ever read an article and actually contacted the author to query about &lt;A href="http://www.emortal.com"&gt;their services&lt;/A&gt;. We'll see what comes of it.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0107789/"&gt;rebelutionary&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; Thanks Mike, A great article.&amp;nbsp; Timely to as I was just thinking about productising liveTopics now that the non-commercial license is finallly worked out.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000535.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics pre-release update</title>
      <pubDate>Thu, 12 Sep 2002 20:57:02 +0100</pubDate>
      <description>&lt;P&gt;The license is, unless a last minute incident crops up, done and I'm packaging the liveTopics release to go out either tonight or tomorrow depending upon how quickly I can tidy the loose ends.&amp;nbsp; I think I'm going to have to abandon my hope of producing a proper installation since I can't seem to find an installer that runs on Windows and can build installation packages for both Windows &amp; Mac.&amp;nbsp; I'm also struggling to get the website into reasonable shape for launch.&lt;/P&gt;
&lt;P&gt;This time it's for real...&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000541.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics finally released</title>
      <pubDate>Fri, 20 Sep 2002 00:43:40 +0100</pubDate>
      <description>&lt;P&gt;Kind of a double celebration:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Today, and with great relief,&amp;nbsp;I formally announce the release of liveTopics (v1.0.3) which is now available for &lt;A href="http://www.novissio.com/html/livetopics.html"&gt;download&lt;/A&gt;. 
&lt;LI&gt;You can read more about it at my company's &lt;A href="http://www.novissio.com/"&gt;website&lt;/A&gt;&amp;nbsp;which I am also launching today.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;It's been hard work putting together even the little currently on the website, but I hope to improve it significantly in the days and weeks ahead.&amp;nbsp; Any feedback would be very welcome. &lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000560.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/pax-americana.xml" ent:id="pax-americana" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/the-middle-east.xml" ent:id="the-middle-east" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>It was due</title>
      <pubDate>Fri, 20 Sep 2002 09:18:29 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://radio.weblogs.com/0109150/2002/09/19.html#a640"&gt;It's Too Much For A Single Week!&lt;/A&gt;. First &lt;A href="http://www.theshiftedlibrarian.com/"&gt;Jenny Levine at TSL&lt;/A&gt; returns, then liveTopics actually gets released. [&lt;A href="http://radio.weblogs.com/0109150/"&gt;blog cognosco v 0.1&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; After the endless delays I guess I was due a healthy dose of sarcasm :-)&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000562.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics issue management by JIRA</title>
      <pubDate>Fri, 20 Sep 2002 10:31:22 +0100</pubDate>
      <description>liveTopics now has an&amp;nbsp;&lt;A href="http://opensource.atlassian.com/novissio/secure/Dashboard.jspa"&gt;issue management&lt;/A&gt; database.&amp;nbsp; This is hosted by &lt;A href="http://www.atlassian.com/"&gt;Atlassian software&lt;/A&gt; on their excellent &lt;A href="http://www.atlassian.com/software/jira/default.jsp"&gt;JIRA&lt;/A&gt; application.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000564.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/big-media.xml" ent:id="big-media" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/business.xml" ent:id="business" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/copyright.xml" ent:id="copyright" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/publishing.xml" ent:id="publishing" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/respect.xml" ent:id="respect" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/tv.xml" ent:id="tv" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>JIRA roadmaps see into the future!</title>
      <pubDate>Sat, 21 Sep 2002 11:46:43 +0100</pubDate>
      <description>&lt;P&gt;One of the really cool features in JIRA is the RoadMap.&lt;/P&gt;
&lt;P&gt;JIRA allows you to create versions in your project, both released and unreleased, and to attach issues to them.&amp;nbsp; In effect, specifying which release the bug will be fixed in.&amp;nbsp; This is pretty neat.&amp;nbsp; Then you can look at the project roadmap which will show you upcoming releases, which issues are attached to them and, by looking at how many of those issues are resolved, how close the release is to being ready.&lt;/P&gt;
&lt;P&gt;It's a great project visualisation tool and I already have the next 4 releases of liveTopics mapped out.&amp;nbsp; I'll flesh out the issues for those as we go forwards.&amp;nbsp; If you're interested then sign up and vote!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000566.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/metadata.xml" ent:id="metadata" 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/topics.xml" ent:id="topics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Working towards 1.0.5</title>
      <pubDate>Sat, 21 Sep 2002 12:11:34 +0100</pubDate>
      <description>&lt;P&gt;I'm concentrating on fixing bugs now for liveTopics 1.0.5 which I hope to make available early next week.&lt;/P&gt;
&lt;P&gt;A great thing about having issue management is that it actually makes fixing bugs so much easier.&amp;nbsp; I can see the bugs I am intending to fix for this release all in one convenient display, but still get at the details quickly.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000568.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/law.xml" ent:id="law" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/the-economy.xml" ent:id="the-economy" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>JIRA does RSS, so cool!</title>
      <pubDate>Tue, 24 Sep 2002 23:05:56 +0100</pubDate>
      <description>&lt;P&gt;Oh man &lt;A href="http://opensource.atlassian.com/novissio/secure/IssueNavigator.jspa?pid=10000&amp;tempMax=25&amp;view=rss&amp;reset=true"&gt;this&lt;/A&gt; &lt;FONT color=red&gt;so rocks&lt;/FONT&gt;!&lt;/P&gt;
&lt;P&gt;I'm now have Radio subscribed to a &lt;A href="http://opensource.atlassian.com/novissio/secure/IssueNavigator.jspa?pid=10000&amp;tempMax=25&amp;view=rss&amp;reset=true"&gt;feed&lt;/A&gt; coming out of my liveTopics &lt;A href="http://opensource.atlassian.com/novissio/secure/Dashboard.jspa"&gt;JIRA project&lt;/A&gt;.&amp;nbsp; I get an RSS item for each change that happens, i.e. someone adds a new issue, someone adds a comment, it's all there.&amp;nbsp; This is *so great* for project visibility.&lt;/P&gt;
&lt;P&gt;Unfortunately it does kinda point out the weaknesses in the Radio aggregator interface.&amp;nbsp; It was probably fine when you only had a dozen or so feeds but I'm up to 58 and some of them are really big.&amp;nbsp; I need a tabbed interface that lets me organize feeds the way I want.&amp;nbsp; I need keyword prioritzation, I need the ability to delete all items from a specific feed at once.&amp;nbsp; I'd like them outlined to save screen real-estate.&amp;nbsp; [&lt;EM&gt;Actually John Robb's just pointed out that I can delete all the items at once, using the magnifying glass icon - must check that out&lt;/EM&gt;]&lt;/P&gt;
&lt;P&gt;Damnit I want aggregator Mark 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000584.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/dublin-core.xml" ent:id="dublin-core" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/metadata.xml" ent:id="metadata" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/rdf.xml" ent:id="rdf" 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/topics.xml" ent:id="topics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Sharing zones of control</title>
      <pubDate>Tue, 24 Sep 2002 23:48:52 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.smartmobs.com/archives/000171.html"&gt;IBM turns to social network analysis&lt;/A&gt;. &lt;EM&gt;A critical resource embedded within organizations is the knowledge that highly skilled workers bring to work on a day-to-day basis. However, aside from human resource policies targeted at the attraction, development and retention of skilled knowledge workers, &lt;STRONG&gt;there has been little effort put into systematic ways of leveraging knowledge that is embedded in people and relationships&lt;/STRONG&gt;. Given the extent to which people rely on their own knowledge and the knowledge of their contacts to solve problems, this is a significant shortcoming. Social network analysis allows us to understand how a given network of people create and share knowledge, helping us to move beyond this approach.&lt;/EM&gt; [&lt;A href="http://www.smartmobs.com/"&gt;Smart Mobs&lt;/A&gt;]&lt;/P&gt;
&lt;P&gt;An important issue that would arise for me, if I were to work in an enterprise, would be to restrict my sharing to the organization. This would require a degree of corporate loyalty that I just might have some trouble with. &lt;/P&gt;
&lt;P&gt;From a personal standpoint, it would be more useful for me to share all my knowledge publicly: it would enable me to build more&amp;nbsp;relationships with outsiders, and establish a reputation that is not limited to my organization. When the time comes to move on, I'd probably be in a better position.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0110772/"&gt;Seb's Open Research&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; As in most human endeavours I think there's going to have to be a compromise.&amp;nbsp; I can imagine increasingly relaxed zones of control over blogged information.&amp;nbsp; Sharing layers if you like:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;My personal private blog (backup brain)&lt;/LI&gt;
&lt;LI&gt;Team / Project Group / Community blog (private sharing)&lt;/LI&gt;
&lt;LI&gt;Intranet blog (corporate sharing)&lt;/LI&gt;
&lt;LI&gt;Public blog (real sharing)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;All of which could be done now using Radio category routing.&amp;nbsp; A simpler interface could be introduced in Radio so that people can specify how wide they want that post shared and Radio selects the right routing category itself.&lt;/P&gt;
&lt;P&gt;I'd add that liveTopics (plug, plug) will &lt;EM&gt;soon&lt;/EM&gt; support categories and less soon the idea of a corporate weblog directory.&amp;nbsp; This will group posts from different weblogs around shared topics.&amp;nbsp; Add &lt;EM&gt;theme support&lt;/EM&gt;&amp;nbsp;and you can cluster related topics to create a real navigable knowledge structure for each layer.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;I haven't forgotten about BlogPlexes either...&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;[I do seem to have gone italic mad lately though]&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000589.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/metadata.xml" ent:id="metadata" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/topics.xml" ent:id="topics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/xfml.xml" ent:id="xfml" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics RSS Feed now available</title>
      <pubDate>Wed, 25 Sep 2002 12:33:28 +0100</pubDate>
      <description>For anyone interested in liveTopics I have added an &lt;A href="http://www.novissio.com/ltlog/rss.xml"&gt;RSS feed&lt;/A&gt; which will be used to announce new releases and important events.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000596.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>For a well baked blog, add topics</title>
      <pubDate>Sat, 28 Sep 2002 12:59:52 +0100</pubDate>
      <description>&lt;A href="http://www.networkcomputing.com/1320/1320buzz2.html"&gt;Michael DeMaria&lt;/A&gt; over at Network Computing wants weblogs to have topical lists of posts.&amp;nbsp; He points out that the time-based format isn't the easiest thing to use when looking for specific posts on selected topics.&amp;nbsp; There are obviously two ways find posts contain a specific topic: 
&lt;P&gt;1) Use a search engine.&amp;nbsp; This is the best approach to use when people are resistant to entering metadata.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) Use a metadata tool like LiveTopics by &lt;A href="http://radio.weblogs.com/0107808/"&gt;Matt Mower&lt;/A&gt;.&amp;nbsp; Matt has built a tool for Radio that makes it easy for authors to enter in metadata with each post.&amp;nbsp; This makes it easy to provide directories that list post by topic (through use of the outliner).&amp;nbsp;&amp;nbsp; Basically, Livetopics can create a simple list of topical links to posts, or a complex hierarchy of topical links.&amp;nbsp; Matt has a complex hierarchy on his site.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://jrobb.userland.com/"&gt;John Robb's Radio Weblog&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; With thanks to John for the link.&lt;/P&gt;
&lt;P&gt;Clearly I think Mike makes a very valid point.&amp;nbsp; Weblogs make great diaries, but the by-date navigation structure sucks for locating topical information.&amp;nbsp; More information about liveTopics can be had by either clicking the liveTopics see-also reference under this post, or going to the &lt;A href="http://www.novissio.com/products/liveTopics/liveTopics.html"&gt;liveTopics&lt;/A&gt;&amp;nbsp;page on the &lt;A href="http://www.novissio.com/"&gt;Novissio&lt;/A&gt; website.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000617.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/topics.xml" ent:id="topics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>What's the difference between topics and categories?</title>
      <pubDate>Sat, 28 Sep 2002 17:05:23 +0100</pubDate>
      <description>&lt;P&gt;With more people interested in liveTopics the question is coming up: "What is the difference between topics and categories?"&lt;/P&gt;
&lt;P&gt;I think Rick Klau &lt;A href="http://www.rklau.com/tins/2002/08/21.html#a448"&gt;sums it up&lt;/A&gt; excellently on his weblog (thanks Rick).&lt;/P&gt;
&lt;P&gt;What categories do best is act as a channel to route content to different places.&amp;nbsp; This allows you to, for example, run multiple weblogs from one copy of Radio, or have RSS feeds for specific purposes (e.g. I have a feed dedicated to liveTopics announcements, there is no HTML just RSS).&lt;/P&gt;
&lt;P&gt;But, as Rick points out, categories are a poor choice for organising the metadata for your posts.&amp;nbsp; They are too inflexible and&amp;nbsp;too hard to setup.&amp;nbsp; They require choices (e.g. theme) that aren't relevant to metadata and impose limitations (both of interface and duplication of content) that are unwelcome.&lt;/P&gt;
&lt;P&gt;On the other hand liveTopics are very simple to use.&amp;nbsp; You create a new topic by using it.&amp;nbsp; Just type it's name into the field provided when you edit your post.&amp;nbsp; You can remove topics just as easily.&lt;/P&gt;
&lt;P align=center&gt;&lt;IMG alt="Weblog Post Form with liveTopics" src="http://www.novissio.com/static/weblogPostForm2.png" border=0&gt;&lt;/P&gt;
&lt;P&gt;When you publish a post, liveTopics automatically creates a table of contents that contains every topic you have used, and links to each post using each topic.&amp;nbsp; You also get a number of handy macros to display topics on your weblog.&amp;nbsp; For example, here is the output from a macro that shows your "Hot Topics" (i.e. the ones you use most often).&lt;/P&gt;
&lt;P align=center&gt;&lt;IMG alt="hot topics" src="http://www.novissio.com/static/hotTopics2.png"&gt;&lt;/P&gt;
&lt;P&gt;So that's what topics &amp; liveTopics can do for you today.&amp;nbsp; Tomorrow?&amp;nbsp; That's another story.&amp;nbsp;&amp;nbsp; If you want to see for yourself, click the button and download liveTopics today.&lt;/P&gt;
&lt;P align=center&gt;&lt;A href="http://www.novissio.com/Downloads/liveTopics/livetopics.html"&gt;&lt;IMG alt=Download src="http://www.novissio.com/downloadLT.png" border=0&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000621.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/culture.xml" ent:id="culture" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/information.xml" ent:id="information" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/media.xml" ent:id="media" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/metalogue.xml" ent:id="metalogue" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Playing with liveTopics</title>
      <pubDate>Sat, 05 Oct 2002 09:56:07 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://radio.weblogs.com/0104487/2002/10/04.html#a413"&gt;Playing With liveTopics - Part II&lt;/A&gt;. I still don't know how many &lt;A href="http://radio.weblogs.com/0104487/2002/10/02.html#a403"&gt;episodes&lt;/A&gt; this mini &lt;A href="http://radio.weblogs.com/0104487/2002/09/30.html#a393"&gt;series&lt;/A&gt; will consist of, but today I'm focusing on the liveTopicsSeeAlso macro, which displays a list of related topics with each post.&amp;nbsp;[&lt;A href="http://radio.weblogs.com/0104487/2002/10/04.html#a413" target=_blank&gt;read more&lt;/A&gt;] [&lt;A href="http://radio.weblogs.com/0104487/"&gt;s l a m&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; I'm grateful to Marc for his excellent introduction to the features of liveTopics.&amp;nbsp;&amp;nbsp; His work has shamed me sufficiently to promise that the next full release will come with a complete macro reference.&amp;nbsp; I aim to put more emphasis on the new user in future releases as well.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000640.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>XFML and the weblog</title>
      <pubDate>Sat, 05 Oct 2002 10:38:06 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0110772/2002/10/04.html#a393"&gt;An overview of faceted classification&lt;/A&gt;. 
&lt;P&gt;Peter over at &lt;A href="http://poorbuthappy.com/ease/"&gt;Ease&lt;/A&gt; provides a short overview of what's happening&amp;nbsp;now in &lt;A href="http://poorbuthappy.com/ease/000481.html"&gt;faceted classification&lt;/A&gt;. Worth looking at if you're interested in metadata and taxonomies. Peter writes:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT color=darkblue&gt;tool availability is coming, and that's good because that will allow us to experiment and then refine the theory.&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;This is precisely how I think it should happen. It's a bootstrap process.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0110772/"&gt;Seb's Open Research&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; The forthcoming 1.0.5 release of liveTopics will have a built in XFML exporter.&amp;nbsp; However, in a sense, this is nothing more than the simple XTM exporter already present (although somewhat buried).&lt;/P&gt;
&lt;P&gt;To see a sample of the XFML from a liveTopics enabled weblog take a look &lt;A href="http://radio.weblogs.com/0107808/outlines/topics/xfml-map.xml"&gt;here&lt;/A&gt;.&amp;nbsp; As you will see we have only one XFML facet &lt;EM&gt;generic&lt;/EM&gt; defined to which all of the topics belong.&lt;/P&gt;
&lt;P&gt;In considering my own ideas for theme support in liveTopics I think they can be mapped to XFML 'parent topics' and so we won't really be using XFML facets at all.&lt;/P&gt;
&lt;P&gt;This then begs the question:&amp;nbsp; Of what use is XFML faceted classifaction in a weblog?&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000645.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-log.xml" ent:id="k-log" 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/topics.xml" ent:id="topics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Faceted Radio weblog demo</title>
      <pubDate>Mon, 07 Oct 2002 21:14:52 +0100</pubDate>
      <description>&lt;P&gt;This is pretty exciting.&lt;/P&gt;
&lt;P&gt;I've just exported an XFML version of my weblog to facetmap.com so that you can browse my weblog by-liveTopics and drill-down by Date of Publication (e.g. start at 2002, drill-down into May, drill-down into 23rd May).&lt;/P&gt;
&lt;P&gt;If you go to &lt;A href="http://facetmap.com/demo/browse.jsp?map=curiouserandcuriouser"&gt;here&lt;/A&gt;&amp;nbsp;you will see an example faceted browsing interface. It's basic but quite functional.&lt;/P&gt;
&lt;P&gt;You will see two "facets"&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The &lt;FONT color=maroon&gt;liveTopics &lt;/FONT&gt;facet contains all my regular topics in a big old list (with number of posts in parens) 
&lt;LI&gt;The &lt;FONT color=maroon&gt;Date of Publication&lt;/FONT&gt; facet contains one topic &lt;FONT color=red&gt;2002&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Underneath you will see the "top 10" pages at this point.&lt;/P&gt;
&lt;P&gt;If you drill down into either facet (please try drilling down into 2002 first) you narrow the range of available posts to display. Keep drilling down via and notice how this restricts the liveTopics that are displayed in the other facet to only those used in posts that are still available in your selected date range.&lt;/P&gt;
&lt;P&gt;Now start to think about other ways of chopping your weblog than just "Date of Publication"&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000658.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge-management.xml" ent:id="knowledge-management" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/roi.xml" ent:id="roi" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/selling.xml" ent:id="selling" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/software.xml" ent:id="software" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>XFML 1.0 (CORE) Support in liveTopics 1.0.5</title>
      <pubDate>Mon, 07 Oct 2002 22:19:23 +0100</pubDate>
      <description>&lt;P&gt;Just a note to say that "beta" support for the new &lt;A href="http://xfml.org/spec/1.0.html"&gt;XFML 1.0 (CORE)&lt;/A&gt; specification has been included in &lt;A href="http://www.novissio.com/products/liveTopics/liveTopics.html"&gt;liveTopics&lt;/A&gt; version 1.0.5 which is now available from the beta update server and will be available from the release server at the end of this week.&lt;/P&gt;
&lt;P&gt;The new liveTopics XFML exporter will allow you to publish an XFML topic map from your weblog that contains all of the topic information defined in your public weblog, with each topic&amp;nbsp;linked to the pages it occurs on.&lt;/P&gt;
&lt;P&gt;Additionally support for a Date of Publication &lt;A href="http://xfml.org/spec/1.0.html#facetconcept"&gt;facet&lt;/A&gt; has been included.&amp;nbsp; Using this facet a compliant application can offer users the ability to drill-down by year, month and even to a single date &lt;STRONG&gt;as well as&lt;/STRONG&gt; drilling down by topic.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000661.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/software.xml" ent:id="software" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/xml.xml" ent:id="xml" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/xslt.xml" ent:id="xslt" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Ad hoc group forming with liveTopics and BlogPlex</title>
      <pubDate>Wed, 09 Oct 2002 16:42:14 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0110772/2002/10/09.html#a426"&gt;Making group-forming ridiculously easy&lt;/A&gt;. 
&lt;P&gt;Now, the idea is this.&amp;nbsp;When I come across a post on an interesting theme that seems like it might have lasting value, I want to be able to &lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Create a topic, with a title of its own and a definition or description in plain English (which may contain arbitrary hyperlinks). Just "where" the topic is stored is unimportant. The important thing is that it is a public entity. 
&lt;LI&gt;Subscribe to that topic. Subscribing has two effects: it adds the topic to a personal topic list of mine, and it means I'll get posts by other people on that topic in my RSS aggregator because each topic is associated to a&amp;nbsp;shared RSS feed. 
&lt;LI&gt;Post to that topic whenever I talk about it in my weblog. This has to be *easy*, like checking a box or selecting from a drop-down menu displayed under the box where I write my posts. 
&lt;LI&gt;Access an archive of posts on that topic somewhere on the Web. 
&lt;LI&gt;Let anyone edit the description of the topic when important things are added to the "state of the art" on the topic, or when other related topics spring out of the discussion, to let people know where the conversation has branched off.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Basically, from where&amp;nbsp;I stand,&amp;nbsp;this sounds a little like a witch's brew of &lt;A href="http://radio.weblogs.com/0107808/outlines/liveTopics.html"&gt;liveTopics&lt;/A&gt;, &lt;A href="http://www.movabletype.org/news/2002_08.shtml#000571"&gt;standalone TrackBack&lt;/A&gt;,&amp;nbsp;and this peculiar brand of editable web sites known as &lt;A href="http://www2.iro.umontreal.ca/~paquetse/cgi-bin/om.cgi?Wiki"&gt;wikis&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://radio.weblogs.com/0110772/"&gt;Seb's Open Research&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; What you are describing sounds very like the idea behind the &lt;A href="http://radio.weblogs.com/0107808/2002/05/31.html#a63"&gt;BlogPlex Server&lt;/A&gt;, for forming ad hoc communities, I put forward a little while back and is the start and endpoint for liveTopics.&lt;/P&gt;
&lt;P&gt;In order to form BlogPlexes you need enough good metadata in someones weblog to being to make connections between them.&amp;nbsp; When I looked around I realised categories weren't going to cut it, AI wasn't ready and hence I began working on liveTopics.&lt;/P&gt;
&lt;P&gt;Obviously since those initial thoughts (which I don't claim are particularly original) I have come across lots of other new ideas like RSS, XFML and so on.&amp;nbsp; These will all feed in to the design and I think improve it.&amp;nbsp; For example&amp;nbsp;in considering item&amp;nbsp;(5) one of the powerful features of XFML is to allow us to connect topics together.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000691.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:cloud>
    </item>
    <item>
      <title>Anybody got a wrench?</title>
      <pubDate>Sun, 13 Oct 2002 19:30:49 +0100</pubDate>
      <description>&lt;P&gt;So, a description of services, I should be able to whip that up in a couple of minutes shouldn't I?&amp;nbsp;&amp;nbsp; Turns out its a bit of a &lt;EM&gt;chase your own tail&lt;/EM&gt; problem for me.&lt;/P&gt;
&lt;P&gt;Services I can offer fall under three broad categories:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Consulting 
&lt;LI&gt;Implementation 
&lt;LI&gt;Product&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Way back, when the madness first gripped me, it was on my mind to be a consultant.&amp;nbsp; I'd done product and implementation and really wanted to move to where the decisions are made.&amp;nbsp; Unfortunately I didn't heed the warnings.&amp;nbsp; Consulting is about&amp;nbsp;80% network and 80% reputation.&amp;nbsp; You could probably survive with either and thrive with both.&amp;nbsp; But neither...?&amp;nbsp; Right.&lt;/P&gt;
&lt;P&gt;Now implementation skills I have.&amp;nbsp; No problems there.&amp;nbsp; I can &lt;EM&gt;hook &amp; eye&lt;/EM&gt; systems together with the best of 'em.&amp;nbsp; I also have a budding application in "!livetopics".&amp;nbsp; If I could just choose between them I should be okay right?&amp;nbsp; Turns out there's a problem though.&lt;/P&gt;
&lt;P&gt;Because there are no klogging consultants in the UK, there are no pilot programs already in place.&amp;nbsp; Nobody needs implementation services if they aren't implementing things.&amp;nbsp; Rats.&amp;nbsp; Well then how about product?&lt;/P&gt;
&lt;P&gt;"!liveTopics" is a knowledge-logging application built on "!radio".&amp;nbsp;&amp;nbsp;But that makes it an application without a market (at least in the UK).&amp;nbsp; If there is no existing market and no consultants out there fostering a market that leaves a big hole where the customers should be.&amp;nbsp; Anyway we all now how difficult it is to be a software company post-1999.&lt;/P&gt;
&lt;P&gt;And last but not least: Where's the leaky pipe?&lt;/P&gt;
&lt;P&gt;I've referred a few times to Geoffrey Moore's &lt;A href="http://www.rklau.com/tins/2002/09/25.html#a540"&gt;leaky pipes&lt;/A&gt; metaphor.&amp;nbsp; That, in todays market, company's will only spend money to fix their pressing problems (their leaky pipes) and then only if it looks like the leak will get worse soon, and then only if the fix can pay for itself.&amp;nbsp; I'll also note in passing that Moore says that business by referral becomes even more important in a down market.&amp;nbsp; Nobody wants to trust a software company anymore.&lt;/P&gt;
&lt;P&gt;Hence my recent interest in framing klogging as the solution to a &lt;EM&gt;leaky pipe&lt;/EM&gt; kind of problem.&amp;nbsp; I believe that if this is possible then many of the other pieces might fit into place.&amp;nbsp; But so far I haven't found the a compelling pipe for which klogging will be the wrench.&amp;nbsp; It still all too "a better tomorrow."&lt;/P&gt;
&lt;P&gt;So, that's the problems.&amp;nbsp; The challenge is in 28-days or less to turn this around and create a compelling statement of services.&lt;/P&gt;
&lt;P&gt;All suggestions warmly welcomed!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000713.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>It's not just for MovableType</title>
      <pubDate>Wed, 16 Oct 2002 12:35:16 +0100</pubDate>
      <description>&lt;A href="http://www.theshiftedlibrarian.com/2002/10/15.html#a2951"&gt;A Different Way Of Looking At Blogs&lt;/A&gt;. 
&lt;P&gt;On the &lt;A href="http://www.info-arch.org/lists/sigia-l/"&gt;SIGIA-L mailing list&lt;/A&gt;, &lt;A href="http://poorbuthappy.com/ease"&gt;Peter Van Dijck&lt;/A&gt; pointed to something very cool.&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;"&lt;A href="http://pixelcharmer.com/fieldnotes/"&gt;Tanya Pixelcharmer's weblog&lt;/A&gt; as viewed through Facetmap: &lt;A href="http://facetmap.com/demo/browse.jsp?map=pixelcharmer"&gt;&lt;A href="http://facetmap.com/demo/browse.jsp?map=pixelcharmer"&gt;http://facetmap.com/demo/browse.jsp?map=pixelcharmer&lt;/A&gt;&lt;/A&gt;. Tanya exported her metadata as XFML (&lt;A href="http://xfml.org/"&gt;&lt;A href="http://xfml.org"&gt;http://xfml.org&lt;/A&gt;&lt;/A&gt;) using a template in Moveabletype, and imported it in facetmap."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I'm still wrapping my mind around this one, but it's an interesting alternative view of a blog. Kind of a cross between &lt;A href="http://www.novissio.com/Products/liveTopics/livetopics.html"&gt;liveTopics&lt;/A&gt; and &lt;A href="http://www.yahoo.com/"&gt;Yahoo&lt;/A&gt; with more format options.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://www.theshiftedlibrarian.com/"&gt;The Shifted Librarian&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; Radio users (with "!livetopics") get to play too:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://facetmap.com/demo/browse.jsp?map=curiouserandcuriouser"&gt;http://facetmap.com/demo/browse.jsp?map=curiouserandcuriouser&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;is a recent copy of my Radio weblog exported to XFML.&amp;nbsp; At the moment liveTopics aren't hierarchical so they all appear as a big glob, but I'm working on this.&lt;/P&gt;
&lt;P&gt;At the moment I define two facets that you can browse in.&amp;nbsp; The first, liveTopics, is all the topics I have manually added to my posts.&amp;nbsp; The second, Date of Publication, is automatically generated by the exporter.&amp;nbsp; I'll be adding other facets as I go (suggestions welcomed).&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000743.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/blogging.xml" ent:id="blogging" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/collaboration.xml" ent:id="collaboration" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge.xml" ent:id="knowledge" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/project-management.xml" ent:id="project-management" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopic 1.0.5 released</title>
      <pubDate>Fri, 18 Oct 2002 17:33:54 +0100</pubDate>
      <description>&lt;P&gt;Today I am releasing liveTopics version 1.0.5&lt;/P&gt;
&lt;P&gt;This is a minor upgrade and bugfix from version 1.0.3.&amp;nbsp;&amp;nbsp; The documentation in this release is slightly worse than for 1.0.3 in that it is now out of date.&amp;nbsp; Documentation will be a priority for the 1.1 release.&lt;/P&gt;&lt;FONT size=2&gt;
&lt;P&gt;If you do not have automatic updates enabled you will need to update manually. You do this my opening the Radio application (using the Open Radio option of the Radio icon in the system tray (or mac equivalent). Then from the Tools menu, choose the liveTopics submenu and from that "Update"&lt;/P&gt;
&lt;P&gt;The ZIP file of v1.0.5 is posted on the Novissio website.&lt;/P&gt;&lt;/FONT&gt;
&lt;P&gt;Whats new in this version:&lt;/P&gt;
&lt;P&gt;1) Tools.&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;The liveTopics page now has a Tools section with the following tools:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Topic Editor (basic info, rename and delete) 
&lt;LI&gt;Category Converter Wizard (turns categories into topics) 
&lt;LI&gt;Table of Contents Publisher (re-publish the Table of Contents via the web) 
&lt;LI&gt;XFML exporter (create an XFML export of your weblog suitable for facetmap.com and other sites)&lt;/LI&gt;&lt;/UL&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;2) Multi-word Topic Phrases&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;By enabling the preference &lt;A href="http://localhost:5335/liveTopics/preferences?page=toc"&gt;here&lt;/A&gt; you can enable the use of multi-word topic phrases in liveTopics.&lt;/P&gt;
&lt;P dir=ltr&gt;With this feature enabled you can use ' ' spaces to separate words in topics.&amp;nbsp; When entering topic phrases they should be surrounded using '"' (double-quote) character as in "a multiword topic phrase".&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;For more information and to see which bugs have been fixed, check &lt;A href="http://guests.atlassian.com/novissio/secure/IssueNavigator.jspa?reset=true&amp;pid=10000&amp;fixfor=10002"&gt;JIRA&lt;/A&gt;.&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000755.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/big-media.xml" ent:id="big-media" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics 1.1 in progress</title>
      <pubDate>Fri, 08 Nov 2002 20:33:10 +0000</pubDate>
      <description>I'm hard at work on liveTopics 1.1 this weekend.&amp;nbsp; This will be the first version to support a table of contents per category meaning that you will finally be able to&amp;nbsp;mix categories and topics the way nature intended.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000820.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/pax-americana.xml" ent:id="pax-americana" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics 1.1 close to release</title>
      <pubDate>Fri, 15 Nov 2002 00:18:21 +0000</pubDate>
      <description>&lt;P&gt;It looks like I might finally have squashed the remaining bugs in liveTopics 1.1, what started as your run of the mill complex update spiralled into an endless cycle of fiddly little bugs.&amp;nbsp; But it's starting to look good now.&amp;nbsp; I'm hoping to roll out to testers very soon.&lt;/P&gt;
&lt;P&gt;Between this and trying to come up with a decent pitch for business blogging I haven't been posting much.&amp;nbsp; I've been reading a lot though and making lots of new friends via &lt;A href="http://www.ryze.org/view.php?who=mowerm"&gt;Ryze&lt;/A&gt;.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000824.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/american-culture.xml" ent:id="american-culture" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>activeRenderer 1.3.1</title>
      <pubDate>Fri, 15 Nov 2002 15:44:55 +0000</pubDate>
      <description>&lt;P&gt;&lt;A href="http://radio.weblogs.com/0104487/2002/11/14.html#a480"&gt;activeFix for liveTopics&lt;/A&gt;. &lt;A title="meet Matt" href="http://www.ryze.org/view.php?who=mowerm"&gt;[img] &lt;/A&gt;Or is it liveFix for activeTopics ? :-) &lt;A href="http://radio.weblogs.com/0107808/"&gt;Matt&lt;/A&gt; and I quickly found out that the new 1.3 version of &lt;A href="http://radio.weblogs.com/0104487/outlines/aR/activeRenderer.html"&gt;activeRenderer&lt;/A&gt;, with its new 'page' wedges for HTML link attributes to outline nodes, was thoroughly breaking &lt;A href="http://www.novissio.com/Products/liveTopics/livetopics.html"&gt;liveTopics&lt;/A&gt;' indexes. The updated 1.3.1 version of activeRenderer fixes a couple of minor bugs, and handles HTML link attributes in a more liveTopics friendly way.&amp;nbsp;[&lt;A href="http://radio.weblogs.com/0104487/2002/11/14.html#a480" target=_blank&gt;read more&lt;/A&gt;] [&lt;A href="http://radio.weblogs.com/0104487/"&gt;s l a m&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; My thanks to Marc for quickly &amp; elegantly fixing this problem.&amp;nbsp; The new activeRenderer features are very cool so you can be sure that liveTopics will soon be exploiting them!&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000828.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/blogging.xml" ent:id="blogging" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/life.xml" ent:id="life" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/paolo-valdemarin.xml" ent:id="paolo-valdemarin" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Topic Maps: CMS is only the beginning</title>
      <pubDate>Thu, 21 Nov 2002 09:59:41 +0000</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.steptwo.com.au/columntwo/archives/000381.html"&gt;Topic maps in content management&lt;/A&gt;. Lars Marius Garshol recently e-mailed me, and pointed me his very interesting article on topic maps and content management. This talks about using an Integrated Topic Management System (ITMS) to provide a much more powerful management interface to the normal... [&lt;A href="http://www.steptwo.com.au/columntwo/"&gt;Column Two&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; I'm fundamentally a believer in topic maps even though I haven't really seen them in concrete action yet.&amp;nbsp; I just believe that they are too simple and elegant an idea to not work.&amp;nbsp; The nice thing is that with XTM and XFML beginning to take off we are sure to see more and more applications that do support topic maps.&lt;/P&gt;
&lt;P&gt;One thing in particular that interests me is that Alex Shapiro (of TouchGraph fame) has created a Personal Brain viewer.&amp;nbsp; This uses the new brain exporter to create a map that is browsable in a TouchGraph viewer.&amp;nbsp; It's very cool to be able to take the plex-style view of Personal Brain and switch to a TG style view.&amp;nbsp; If only they could be integrated somehow...&lt;/P&gt;
&lt;P&gt;For my own part liveTopics adds to the capability of Radio as a CMS by overlaying a topic based structure onto the content.&amp;nbsp; This will become more powerful when topics can themselves be structured, and when the postings from multiple weblogs can be related by content.&lt;/P&gt;
&lt;P&gt;Something that worries me though is a recent comment (I cannot remember the source) that weblogs+topics are just recreating threaded discussions.&amp;nbsp; I can't quite articulate yet what it is I don't like about this comment, but there is something here that bothers me.&amp;nbsp; (Note: I see nothing wrong with threaded discussion per-se, I think I am more bothered by the possible perception that blogs = another usenet somehow)&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000843.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics in RSS2.0</title>
      <pubDate>Wed, 27 Nov 2002 09:52:54 +0000</pubDate>
      <description>&lt;P&gt;Is &lt;A href="http://radio.weblogs.com/0107808/gems/aaa.xml"&gt;this&lt;/A&gt; the first &lt;A href="http://aggregator.userland.com/validator?url=http%3A%2F%2Fradio.weblogs.com%2F0107808%2Fgems%2Faaa.xml"&gt;valid RSS feed&lt;/A&gt; with topic metadata?&lt;/P&gt;
&lt;P&gt;Today I've finished the experimental RSS generator for Radio that exports the associated liveTopics with each post in the RSS feed.&amp;nbsp; At the moment topics are contained in a "liveTopics" XML namespace.&lt;/P&gt;
&lt;P&gt;This will enable a smart aggregator to use the topic's for filtering &amp; combining feeds together.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000862.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/creative-commons.xml" ent:id="creative-commons" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/livetopics.xml" ent:id="livetopics" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/metadata.xml" ent:id="metadata" 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/rss.xml" ent:id="rss" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/topics.xml" ent:id="topics" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics in RSS2.0 #2</title>
      <pubDate>Thu, 28 Nov 2002 15:55:44 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://radio.weblogs.com/0107808/2002/11/27.html#a566"&gt;Matt Mower's Knowledge Log - ( liveTopics, k-log, radio, blogging, RSS )&lt;/A&gt;: "&lt;EM&gt;This will enable a smart aggregator to use the topic's for filtering &amp; combining feeds together.&lt;/EM&gt;" + filtering is in the pipeline for myRadio, on dates, keywords, and now topics. will be tricky to devise a UI.&lt;BR&gt;+ filter a single feed, or multiple feeds. multiple feeds would require agreement on a common pool of topics, i think.&lt;BR&gt;+ Syndication, with meta-data, gathered by smart aggregators, has a lot of possibilities. It would be cool to hear more about usage scenarios. [&lt;A href="http://radio.weblogs.com/0100875/"&gt;Brain Off&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Mikel picks up on my post yesterday regarding adding topics to Radio RSS.&amp;nbsp; I've got a few things in mind for this, but I'm sure others will really lead the way.&amp;nbsp; Let's just address one point first.&lt;/P&gt;
&lt;P&gt;When trying to handle feeds from multiple blogs, inevitably, as Mikel points out, we will reach the situation where people using different words to mean the same topic.&amp;nbsp; This will be a problem, but hopefully not as a big of a problem as it could be.&amp;nbsp; It is for this reason that I have been tracking &lt;A href="http://xfml.org/"&gt;XFML&lt;/A&gt; so carefully.&amp;nbsp; With XFML we have the ability to say "A's topic&amp;nbsp;X is the same as B's topic Y".&amp;nbsp; liveTopics already does XFML.&lt;/P&gt;
&lt;P&gt;So I think the first and simplest usage scenario will be within the type of aggregators that we have now as a way of filtering a feed to get rid of posts we deem irrelevant.&amp;nbsp; This will allow us to subscribe to many, many more feeds since we don't have to weed out so much chaff.&amp;nbsp; Although I think we'll need to be careful as it may make it more difficult to experience serendipitous moments.&lt;/P&gt;
&lt;P&gt;The next scenario I can imagine is as a way of producing a consolidated "on-topic" feed from a number of other feeds.&amp;nbsp; Combined with technology to scrape RSS from sites and databases and with a little automagic to add topics where they don't exist this could be very powerful.&lt;/P&gt;
&lt;P&gt;My imagination runs out here, maybe someone else..?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000887.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/ent.xml" ent:id="ent" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>BlogChannels with liveTopics + RSS</title>
      <pubDate>Thu, 28 Nov 2002 20:06:46 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://radio.weblogs.com/0110772/2002/11/20.html#a580"&gt;BlogChannels for loosely joining webloggers?&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;Sebastien reports on a very cool project. BlogChannels could be a powerful tool... and it might save me a lot of manual work that I need to do for Seblogging. If people simply "pinged" a common channel I would not need to sift through all the stuff that is getting published on the individual Weblogs. This is especially the case with less focused Weblogs where only now and then a posts refers to educational applications of personal Webpublishing and Weblogging...&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://Seblogging.cognitivearchitects.com/"&gt;Seblogging News&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The BlogChannels idea presented here merges very neatly with the &lt;A href="http://radio.weblogs.com/0107808/2002/11/28.html#a577"&gt;work&lt;/A&gt; I am doing with liveTopics + RSS2.0 and one of the suggested applications of that work, i.e. consolidating multiple RSS feeds based upon topic information.&amp;nbsp; The nice thing is that this work can be easily duplicated for any blogging system.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000894.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/marketing.xml" ent:id="marketing" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics in RSS2.0 #3</title>
      <pubDate>Thu, 28 Nov 2002 20:43:06 +0000</pubDate>
      <description>My RSS2.0 feed is now live using a liveTopics namespace to add topic information to each post.&amp;nbsp; If your aggregator gets smart you could filter out all the stuff I say that you're not interested in....&amp;nbsp; err... hello?&amp;nbsp; Where did everyone go?</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000896.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/knowledge.xml" ent:id="knowledge" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics RSS, RDF and the Dublin Core</title>
      <pubDate>Fri, 29 Nov 2002 08:55:46 +0000</pubDate>
      <description>&lt;P&gt;liveTopics RSS2.0 feeds now use a vendor neutral XML namespace:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;xmlns:rsstopics=&lt;A href="http://purl.oclc.org/NET/rss-topics/"&gt;http://purl.oclc.org/NET/rss-topics/&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;which is currently pointed at &lt;A href="http://www.novissio.com/resources/rsstopics/"&gt;http://www.novissio.com/resources/rsstopics/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;So each &lt;item/&gt; now comes with an &lt;rsstopics:topic/&gt; definition for every topic it is associated with.&amp;nbsp; These &lt;topic&gt; tags will soon be pointing back to their ToC entries and optionally to their definition within the XFML version of the weblog.&lt;/P&gt;
&lt;P&gt;I have taken a quick look at the work done on the RSS1.0 taxonomy module with defines an RDF syntax for specifying topics and advises the use of Dublin Core metadata for adding information.&amp;nbsp; I'll certainly be persuing the use of DC tags but does anyone think I should be trying to re-use the RDF module &amp; syntax?&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000903.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>More on BlogChannels and topics</title>
      <pubDate>Fri, 29 Nov 2002 14:52:45 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://radio.weblogs.com/0110772/2002/11/20.html#a580"&gt;BlogChannels for loosely joining webloggers?&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;There's a dual way to look at blog channels. They provide a sociality-driven incentive for bloggers to apply metadata tags to their posts. By tagging X on a post you're in effect&amp;nbsp;hanging out a bit with the X crowd.&amp;nbsp; "Metadata has never been more fun!" &lt;/P&gt;
&lt;P dir=ltr&gt;Well, that's perhaps an exaggeration, but&amp;nbsp;I'm personally much more interested in metadata that&amp;nbsp;means something for&amp;nbsp;people other than me.&amp;nbsp;This is what I find most interesting in this scheme: metadata is shared - that's built into the design. The meaning of the shared term takes shape through the efforts of several people. Contrast this to what currently happens with individual blog categories, where we often have a hard time making sense of each other's categories.&lt;/P&gt;
&lt;P&gt;UNQUOTE [&lt;A href="http://radio.weblogs.com/0110772/"&gt;Seb's Open Research&lt;/A&gt;] [&lt;A href="http://radio.weblogs.com/0107846/categories/brainToBrain/"&gt;Al Macintyre: Brain to Brain&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Al groks it.&amp;nbsp; Adding metadata &lt;EM&gt;is&lt;/EM&gt; a way of self-selecting the crowd you want to hang out with.&lt;/P&gt;
&lt;P&gt;And the problem of differences in metadata can be overcome by building shared taxonomy (e.g. using an XFML map) to relate your topics to each other.&amp;nbsp; By building it out in the open you encourage other people to adopt the same terminology (this is what liveTopics topic rolls will be all about).&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000920.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <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/k-collector.xml" ent:id="k-collector" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Timeless weblogs</title>
      <pubDate>Sun, 15 Dec 2002 21:47:38 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;The other outline-related idea that I never got around to implementing, but do know how to implement (I think) is what I &lt;A href="http://www.google.com/search?as_q=timeless&amp;num=10&amp;hl=en&amp;ie=UTF-8&amp;oe=UTF-8&amp;btnG=Google+Search&amp;as_epq=&amp;as_oq=&amp;as_eq=&amp;lr=&amp;as_ft=i&amp;as_filetype=&amp;as_qdr=all&amp;as_occt=any&amp;as_dt=i&amp;as_sitesearch=scriptingnews.userland.com&amp;safe=off"&gt;called&lt;/A&gt; "timeless weblogs". Basically you'd route a weblog post to a section of an OPML directory, as described above, using the &lt;CATEGORY&gt;&lt;A href="http://backend.userland.com/rss#ltcategorygtSubelementOfLtitemgt"&gt;element&lt;/A&gt; that's been in RSS since 0.92. Then it would appear in a news box on that category, so you'd get persistent links on the left hand side, and new bits that are not permanent, in the news box. As with all these things, if you have an idea, the time may not be right. Maybe it's right now for these ideas. Just a Sunday morning pondering. [&lt;A href="http://www.scripting.com/"&gt;Scripting News&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;For "timeless weblogs" read "topics".&amp;nbsp; &lt;FONT color=maroon&gt;&lt;EM&gt;liveTopics&lt;/EM&gt;&lt;/FONT&gt; that is :-)&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001000.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Testing RSS liveTopics</title>
      <pubDate>Sun, 15 Dec 2002 22:59:04 +0000</pubDate>
      <description>Test RSS topics.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001002.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Nose back to the grindstone</title>
      <pubDate>Mon, 30 Dec 2002 20:04:39 +0000</pubDate>
      <description>The christmas RSS backlog is now reduced to managable proportions.&amp;nbsp; Back to work on the liveTopics user guide!</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001020.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Current progress on liveTopics 1.1</title>
      <pubDate>Thu, 02 Jan 2003 16:22:44 +0000</pubDate>
      <description>&lt;P&gt;liveTopics 1.1 has been further delayed.&amp;nbsp; Unfortunately the delay is not entirely due to my inability to finish the user guide.&amp;nbsp; Well it is, but it's not quite that simple.&amp;nbsp; Allow me to explain:&lt;/P&gt;
&lt;P&gt;I've gotten to the stage of writing the part about&amp;nbsp;how you configure the product.&amp;nbsp; At this point I have realised that the configuration process is a mess and needs fixing.&amp;nbsp; It's too complicated and basically too broken as it stands.&lt;/P&gt;
&lt;P&gt;So I'm going back to fix how preferences are handled once and for all.&amp;nbsp; This should lead to a better product and, hopefully, one that is easier for me to document!&lt;/P&gt;
&lt;P&gt;With luck it will only introduce a small delay and I can confidently state that liveTopics 1.1 &lt;STRONG&gt;will&lt;/STRONG&gt; be released in 2003!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001030.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:cloud>
    </item>
    <item>
      <title>liveTopics configuration</title>
      <pubDate>Sun, 12 Jan 2003 18:09:23 +0000</pubDate>
      <description>&lt;P&gt;As a small demonstration that progress towards liveTopics version 1.1 is being made I've just put up a &lt;A href="http://radio.weblogs.com/0107808/gems/ltcap.jpg"&gt;screenshot&lt;/A&gt; of the new status &amp; configuration screen.&lt;/P&gt;
&lt;P&gt;This is a radical overhaul of the interface both in the current release 1.06 and that I initially developed for 1.1.&amp;nbsp; I've put everything on a single screen and tried to make it as simple as possible.&lt;/P&gt;
&lt;P&gt;Everything got a lot more complicated when I started to have per-category preferences and, rather than continue with the grotty hack I had in place (which was proving incredibly hard to document, and wouldn't have worked properly) I decided to start with a clean slate.&lt;/P&gt;
&lt;P&gt;All feedback is welcome.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001062.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>The Topic Exchange</title>
      <pubDate>Tue, 14 Jan 2003 09:57:10 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://blogs.salon.com/0000002/2003/1/14/#200301141"&gt;New and improved&lt;/A&gt;. Thought I'd mention something new I've been hacking on for the last few evenings. It's not all done yet, but people are e-mailing me about it so here's a bit of an introduction:&lt;BR&gt;&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;A href="http://topicexchange.com/"&gt;The Internet Topic Exchange&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;It's the first (as far as I know) real-life implementation of &lt;A href="http://www.myelin.co.nz/cgi-bin/wcswiki.pl?RidiculouslyEasyGroupForming"&gt;Ridiculously Easy Group Forming&lt;/A&gt;. Basically, it lets you create sites like &lt;A href="http://www.highcontext.com/kmpings/"&gt;KMPings&lt;/A&gt; just by filling out a &lt;A href="http://topicexchange.com/new"&gt;form&lt;/A&gt;.&lt;BR&gt;&lt;BR&gt;Once you've created one, you can send &lt;A href="http://www.movabletype.org/trackback/"&gt;TrackBack&lt;/A&gt; pings to it, and see them &lt;A href="http://topicexchange.com/t/test/"&gt;like so&lt;/A&gt;. There's also &lt;A href="http://topicexchange.com/t/test/rss"&gt;RSS&lt;/A&gt; for the aggregator junkies.&lt;BR&gt;&lt;BR&gt;With any luck &lt;A href="http://radio.weblogs.com/0107808/"&gt;Matt Mower&lt;/A&gt; will be supporting it with his &lt;A href="http://www.novissio.com/products/liveTopics/liveTopics.html"&gt;LiveTopics&lt;/A&gt; tool, so it'll be trivial to use from &lt;A href="http://radio.userland.com/"&gt;Radio&lt;/A&gt; as well.&lt;BR&gt;&lt;BR&gt;Any suggestions / feature requests? &lt;/P&gt;
&lt;P&gt;&lt;A title="Click here to comment on this post." href="http://rcs.salon.com/rcsComments/comments?u=2&amp;p=200301141&amp;link=http://blogs.salon.com/0000002/2003/1/14/#200301141"&gt;Comment&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://blogs.salon.com/0000002/"&gt;Second p0st&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Indeed I will be.&amp;nbsp; I hacked in the basic support for the configuration of this feature last night (since I was working on preferences code anyway).&amp;nbsp; Adding the ping code as another publishing activity should be trivial.&lt;/P&gt;
&lt;P&gt;What Phil has done is to implement a very simple, elegant, solution along the path of the BlogPlex idea I've been working towards.&amp;nbsp; With the Topic Exchange, it will be simple for users to cluster around topics simply by using them.&lt;/P&gt;
&lt;P&gt;What might be interesting is to combine this with the idea of synonyms (from XFML) so that even when people don't use exactly the same topic name, if they are talking about the same thing,&amp;nbsp;they can still cluster with everyone else!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001065.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/lawrence-lessig.xml" ent:id="lawrence-lessig" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Testing liveTopics 1.1.1</title>
      <pubDate>Wed, 15 Jan 2003 12:59:26 +0000</pubDate>
      <description>&lt;P&gt;I've spent the last two days reworking some of the innards of liveTopics.&amp;nbsp; First, I've implemented a completely new preferences management system, and, second, I've removed a great deal of the cruft that has accumulated as liveTopics has grown from a quick and grotty hack into a big and tangled hack.&lt;/P&gt;
&lt;P&gt;This is kind of a test to see whether things are still working in my blog.&lt;/P&gt;
&lt;P&gt;I've also pushed the version up to 1.1.1 for reasons which are probably not too interesting.&lt;/P&gt;
&lt;P&gt;&lt;FONT color=red&gt;Okay there are clearly problems...&amp;nbsp; &lt;grrr&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Well of course it would have helped if I had remember to reset the new preferences....&lt;/P&gt;
&lt;P&gt;That fixes the topic links, unfortunately the TOC is not being updated now...&lt;/P&gt;
&lt;P&gt;Try this.&amp;nbsp; Nope, how about that.&amp;nbsp; The other?&lt;/P&gt;
&lt;P&gt;Right with a bit of luck the ToC generator is fixed.&amp;nbsp; Now to try and ping the Topic Exchange ;-)&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001070.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-collector.xml" ent:id="k-collector" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Testing topic exchange</title>
      <pubDate>Wed, 15 Jan 2003 18:15:01 +0000</pubDate>
      <description>&lt;P&gt;If this test works then liveTopics will have automatically pinged the topics associated with this post at &lt;A href="http://topicexchange.com/"&gt;Topic Exchange&lt;/A&gt;.&amp;nbsp; The evidence will be &lt;A href="http://topicexchange.com/t/liveTopics/"&gt;here&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Okay, slight hiccup -- let's try that again...&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001074.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Plans and licenses</title>
      <pubDate>Wed, 15 Jan 2003 23:16:30 +0000</pubDate>
      <description>&lt;P&gt;After all the pain I went through last year I can't actually believe I am doing this, however, I am thinking of changing the license for liveTopics from my custom license (the &lt;A href="http://www.novissio.com/Products/liveTopics/liveTopics_Software_License_Ag/livetopics_software_license_ag.html"&gt;LSLA&lt;/A&gt;) to use a &lt;A href="http://www.creativecommons.org/"&gt;Creative Commons&lt;/A&gt; license.&lt;/P&gt;
&lt;P&gt;My current plans are to release two editions of liveTopics tentatively dubbed the &lt;FONT color=maroon&gt;Personal&lt;/FONT&gt; and &lt;FONT color=maroon&gt;Collaborative&lt;/FONT&gt; editions.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;liveTopics Personal Edition&lt;/EM&gt; (PE) will be basically continue to be&amp;nbsp;free for non-commercial use as liveTopics is now.&amp;nbsp; Of the license available I think the:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://creativecommons.org/licenses/by-nc-sa/1.0"&gt;Attribution-NonCommercial-ShareAlike 1.0&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;seems closest to the spirit of the LSLA.&amp;nbsp; liveTopics PE will include all of the Table of Contents &amp; weblog based features that most people are using now, but it will not include any of the topic mapping functionality.&lt;/P&gt;
&lt;P dir=ltr&gt;&lt;EM&gt;liveTopics Collaborative Edition&lt;/EM&gt; (CE) will include the ability to create topic maps (in&amp;nbsp;both&amp;nbsp;&lt;A href="http://www.topicmaps.org/xtm/1.0/"&gt;XTM&lt;/A&gt; and &lt;A href="http://xfml.org/"&gt;XFML&lt;/A&gt;&amp;nbsp;formats), the ability to do trackback pings on topics (ala Phil Pearsons &lt;A href="http://www.topicexchange.com/"&gt;TopicExchange&lt;/A&gt;), and be able to output topics in RSS2.0 to enable smart aggregators.&amp;nbsp; liveTopics CE will support commerical use.&lt;/P&gt;
&lt;P dir=ltr&gt;I am considering a price tag of $65 (USD) / £40 (UKP)&amp;nbsp;for a CE license.&lt;/P&gt;
&lt;P dir=ltr&gt;I'd be interested in any and all feedback on these plans.&amp;nbsp; They are by no means definite (other than that all of those features will be available in some combination, somehow).&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001076.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>RSS topics in the mix</title>
      <pubDate>Tue, 21 Jan 2003 18:17:40 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://groups.yahoo.com/group/radio-dev/message/7369"&gt;Dave Winer&lt;/A&gt;. Callbacks for RSS-writing released [&lt;A href="http://groups.yahoo.com/group/radio-dev"&gt;radio-dev&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;This is good stuff.&amp;nbsp; liveTopics was using my own witches brew of code to inject topic information into the RSS feed.&amp;nbsp; Now it can do it with a proper set of callbacks.&amp;nbsp; And this will work across all categories as well.&amp;nbsp; Neat, thank you Dave.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001083.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/java.xml" ent:id="java" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Catch up...</title>
      <pubDate>Fri, 14 Feb 2003 09:53:57 +0000</pubDate>
      <description>&lt;P&gt;Just catching up...&lt;/P&gt;
&lt;P&gt;Had drinks with &lt;A href="http://www.rklau.com/tins/"&gt;Rick&lt;/A&gt; and &lt;A href="http://www.surveyanalysis.com/"&gt;Roger&lt;/A&gt; on Wednesday night in central London.&amp;nbsp; I hadn't seen either of them in quite a while so it was good to catch up.&amp;nbsp; Add &lt;A href="http://paolo.evectors.it/"&gt;Paolo&lt;/A&gt; to the mix and i've had a very interesting week!&lt;/P&gt;
&lt;P&gt;Yesterday was spent getting the liveTopics release together.&amp;nbsp; It was quite frustrating but I think I should have it done by this afternoon.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001156.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/k-collector.xml" ent:id="k-collector" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics 1.1.3</title>
      <pubDate>Wed, 19 Mar 2003 20:30:00 +0000</pubDate>
      <description>&lt;P&gt;I hope to give you guys liveTopics 1.1.3 tomorrow which inclues basic topic types functionality.&lt;/P&gt;
&lt;P&gt;This will allow you to edit existing topics and specify a type (fixed at the moment to generic, person, project, place &amp; time).&amp;nbsp; These types will then be exposed via the RSS feed.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001309.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/george-bush.xml" ent:id="george-bush" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Topic Rolls near reality</title>
      <pubDate>Thu, 27 Mar 2003 23:38:44 +0000</pubDate>
      <description>&lt;P&gt;Some while ago I talked about the facility for users to share topics with each other.&amp;nbsp; I was just beginning to experiment with topics and blogging and, at the time, was thinking of an ad hoc P2P mechanism by which users could&amp;nbsp;ensure they were talking about the same thing by using the same topics.&amp;nbsp; I called this concept a topicroll playing on the theme of the blogroll.&lt;/P&gt;
&lt;P&gt;More recently Paolo and I have been working on making use of topics to create a superior &lt;FONT color=maroon&gt;Action Journalling&lt;/FONT&gt; environment.&amp;nbsp; &lt;A href="http://paolo.evectors.it/"&gt;Paolo&lt;/A&gt; has also been involved in the &lt;A href="http://www.bookcafe.net/blog/aggregator/"&gt;Italian Blog Aggregator&lt;/A&gt; project about which he has written on several occasions.&amp;nbsp; These efforts have begun to dovetail and I wanted to document some of what we are doing.&lt;/P&gt;
&lt;P&gt;For a while now liveTopics has provided the ability for Radio users to associate multiple topics with their posts.&amp;nbsp; This allows for fine-grained, ad hoc, associations between posts in a much more flexible way than categories allow.&amp;nbsp; Release 1.1.3 (due RSN) adds also the concept of &lt;FONT color=darkblue&gt;topic types&lt;/FONT&gt; and these are central to our efforts.&lt;/P&gt;
&lt;P&gt;liveTopics &lt;FONT color=darkblue&gt;types &lt;/FONT&gt;are a way of classifying topics into functional categories.&amp;nbsp; For example the default types created by liveTopics are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;generic 
&lt;LI&gt;person 
&lt;LI&gt;project 
&lt;LI&gt;place 
&lt;LI&gt;time&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Each topic can belong to only one type (which defaults to generic).&amp;nbsp; Now my topic &lt;A href="http://radio.weblogs.com/0107808/topics/topicsP.html#paolo"&gt;Paolo&lt;/A&gt; can be classified as being a &lt;EM&gt;person topic&lt;/EM&gt;.&amp;nbsp; Now all topics are not equal and our software can start to provide useful interfaces based upon topic information.&lt;/P&gt;
&lt;P&gt;Systems such as the Italian Blog Aggregator may want to define a control language for topics rather than allowing users to make up their own.&amp;nbsp; Even if it does not wish to control the topics, it may be useful if users can pre-fill their topic list with system defined topics.&amp;nbsp; That's what the topicroll is all about.&amp;nbsp; Now we're going to implement it.&lt;/P&gt;
&lt;P&gt;To begin with we have choosen to use the &lt;A href="http://www.opml.org/spec"&gt;OPML&lt;/A&gt; format for the topic roll (later on we will probably implement them in &lt;A href="http://www.topicmaps.org/xtm/1.0/"&gt;XTM&lt;/A&gt; as well).&amp;nbsp;&amp;nbsp;Whilst OPML is not a semantically ideal language for describing a topic roll it has&amp;nbsp;a number of advantage for us right now:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;It's simple: It basically has only 1 tag &lt;outline&gt; so it's pretty easy to get along with 
&lt;LI&gt;It's a standard: OPML is already used &amp; understood around the world, we're not inventing it ourselves 
&lt;LI&gt;There are tools: In principle you should be able to create a topic roll in any OPML editor and load it into liveTopics and vice versa&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;As an example you can see my current &lt;A href="http://radio.weblogs.com/0107808/topics/resources/topicRoll.opml"&gt;topicroll&lt;/A&gt; for yourself (although I notice that Radio doesn't seem to make anything of it, I wonder if my OPML is bad).&lt;/P&gt;
&lt;P&gt;[&lt;FONT color=darkblue&gt;28/03&lt;/FONT&gt;: With a little help from Paolo the topicRoll OPML is now fixed and the outline works in Radio!]&lt;/P&gt;
&lt;P&gt;The next step is to allow liveTopics to import topicrolls from other locations.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001331.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/blogging.xml" ent:id="blogging" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/k-logs.xml" ent:id="k-logs" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>MarcB hits town</title>
      <pubDate>Tue, 01 Apr 2003 11:38:08 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://radio.weblogs.com/0104487/"&gt;Marc Barrot&lt;/A&gt; is in town and came to visit last night.&amp;nbsp; We spent a good chunk of the evening drinking red wine &amp; chatting about the war (like you do).&amp;nbsp; Then Marc showed me the progress he's made with WebOutliner and boy is it impressive (you'll just have to wait and see).&amp;nbsp; He's also taught me some neat tricks with Javascript &amp; DOM which radically improve the liveTopics interface, expect these very soon.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001345.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/esf.xml" ent:id="esf" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/event-share-framework.xml" ent:id="event-share-framework" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/k-collector.xml" ent:id="k-collector" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/topic-mapping.xml" ent:id="topic-mapping" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/xfml.xml" ent:id="xfml" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Mozilla and liveTopics</title>
      <pubDate>Wed, 02 Apr 2003 19:40:34 +0100</pubDate>
      <description>&lt;P&gt;I don't use Mozilla as my day-to-day browser.&amp;nbsp; Over the last couple of years I have become very dependent upon MS IE.&amp;nbsp; IE may be a terribly irritating browser at times but it's still ahead of Mozilla on Windows and the WYSIWYG editor is a major plus when editing weblog posts.&lt;/P&gt;
&lt;P&gt;However I have to take my hat off to the Mozilla developers for providing a vastly superior environment for writing web applications.&amp;nbsp; Over the last couple of days I have been delving into the DOM and using JavaScript+DOM to create a dynamic interface for liveTopics.&amp;nbsp; IE just sucks in this respect.&amp;nbsp; It's error messages are hard to find, unhelpful or just plain wrong.&amp;nbsp; Using the Mozilla console &amp; DOM inspector have just made things much easier.&amp;nbsp; Now if I could just figure out the debugger...&lt;/P&gt;
&lt;P&gt;One thing that does puzzle me though is why the built in View Source application:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;doesn't show line numbers 
&lt;LI&gt;doesn't have a jump-to-line-n command&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Both seem like pretty obvious functionality to me.&lt;/P&gt;
&lt;P&gt;So, what&amp;nbsp;is this all in aid of?&amp;nbsp; Well &lt;A href="http://radio.weblogs.com/0104487/"&gt;Marc&lt;/A&gt; wowed me with the possibilities available with DOM &amp; JS in today's browser (I did most of my HTML &amp; JavaScript coding over 3 years ago) and I realised that I could totally overhaul the part of the liveTopics interface that needed it most.&lt;/P&gt;
&lt;P&gt;Here are some screenshots to give you an idea where I am going with this.&lt;/P&gt;
&lt;P&gt;&lt;%softShadow( "http://matt.blogs.it/images/liveTopics/topicManager1.jpg" )%&gt;The old &lt;I&gt;suggest topics&lt;/I&gt; interface is gone, long live the topic manager.&amp;nbsp; You'll notice that this interface displays the &lt;STRONG&gt;topic types&lt;/STRONG&gt; available in my weblog.&lt;/P&gt;
&lt;P&gt;&lt;%softShadow( "http://matt.blogs.it/images/liveTopics/topicManager2.jpg" )%&gt;There are no suggested topics shown in this shot but they would appear as regular checkbox items. Here I have popped open one of the types to show the topics I can select from it. All thanks to the magic of activeRenderer.&lt;/P&gt;
&lt;P&gt;&lt;%softShadow( "http://matt.blogs.it/images/liveTopics/topicManager3.jpg" )%&gt;Heres the magic. Click + and add a new topic. You can also say what type it should belong to.&lt;/P&gt;
&lt;P&gt;&lt;%softShadow( "http://matt.blogs.it/images/liveTopics/topicManager4.jpg" )%&gt;The interface is totally dynamic.&lt;/P&gt;
&lt;P&gt;There are a few more days work to get this to a point where it is usable.&amp;nbsp; I hope to release 1.1.3 to interested parties (Roland?) at the weekend.&amp;nbsp; Oh and of course this release also contains RSS+topics and Topic Types!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001348.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Exploring topics in RSS2.0</title>
      <pubDate>Sat, 05 Apr 2003 10:38:33 +0100</pubDate>
      <description>&lt;P&gt;I've been doing some thinking about how to encode topic information into &lt;STRONG&gt;RSS2.0&lt;/STRONG&gt; feeds.&amp;nbsp; As a simple test of the Radio callback facility I have &lt;A href="http://matt.blogs.it/rss.xml"&gt;implemented&lt;/A&gt; a very simplistic protocol.&amp;nbsp; Within each &lt;item&gt; is a tag&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt; &lt;FONT color=maroon&gt;id&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;topic_id&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt; &lt;FONT color=maroon&gt;type&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;topic-type&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt; &lt;FONT color=maroon&gt;source&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;url&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;STRONG&gt;topic name&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;for each topic associated with the item (post).&amp;nbsp; A concrete example (using the rsstopics namespace):&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&lt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;FONT color=#990000&gt;&lt;SPAN class=t&gt;rsstopics:topic&lt;/SPAN&gt;&lt;SPAN class=t&gt; rsstopics:id&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;="&lt;/FONT&gt;&lt;/SPAN&gt;&lt;B&gt;the_state&lt;/B&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;"&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=t&gt;&lt;FONT color=#990000&gt; rsstopics:source&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;="&lt;/FONT&gt;&lt;/SPAN&gt;&lt;B&gt;http://matt.blogs.it/topics/topicsT.html#the_state&lt;/B&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;"&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=t&gt;&lt;FONT color=#990000&gt; rsstopics:type&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;="&lt;/FONT&gt;&lt;/SPAN&gt;&lt;B&gt;generic&lt;/B&gt;&lt;FONT color=#0000ff&gt;&lt;SPAN class=m&gt;"&lt;/SPAN&gt;&lt;SPAN class=m&gt;&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN class=tx&gt;&lt;STRONG&gt;the state&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&lt;/&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=t&gt;&lt;FONT color=#990000&gt;rsstopics:topic&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;Whilst this does have the advantage that it's simple and direct it's also a bit silly to invent a new format for topic information when we have two &lt;EM&gt;standard&lt;/EM&gt; culprits available already:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL dir=ltr&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;SPAN class=m&gt;&lt;A href="http://www.w3.org/TR/rdf-primer/"&gt;Resource Description Framework (RDF)&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;LI&gt;
&lt;DIV&gt;&lt;SPAN class=m&gt;&lt;A href="http://www.topicmaps.org/xtm/1.0/"&gt;XML Topic Maps (XTM)&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;RDF is a general format for describing resources.&amp;nbsp; A resource in RDF terms is anything which can be uniquely identified by a URI.&amp;nbsp; An RDF statement (utilizing &lt;A href="http://dublincore.org/"&gt;Dublin Core&lt;/A&gt; metadata) that asserts me as the owner of my weblog might look something like:&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:Description rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;http://matt.blogs.it&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;dc:Creator&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;Matt Mower&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;dc:Creator&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:Description&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;If you cut away the syntactic fluff what this says is:&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;STRONG&gt;Matt Mower&lt;/STRONG&gt; is the &lt;STRONG&gt;Creator&lt;/STRONG&gt; of &lt;A href="http://matt.blogs.it/"&gt;http://matt.blogs.it&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;Referring back to the problem at hand, describing what a post (expressed as an RSS item) is about we could come up with something like:&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;item&lt;/FONT&gt; &lt;FONT color=maroon&gt;rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;permalink&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt;&lt;FONT color=#000000&gt; &lt;/FONT&gt;&lt;FONT color=maroon&gt;id&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;STRONG&gt;topic_id&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt;&lt;FONT color=#000000&gt; &lt;/FONT&gt;&lt;FONT color=maroon&gt;type&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;STRONG&gt;topic-type&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt;&lt;FONT color=#000000&gt; &lt;/FONT&gt;&lt;FONT color=maroon&gt;source&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;STRONG&gt;url&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;STRONG&gt;topic name&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&lt;BR&gt;&lt;/&lt;FONT color=maroon&gt;item&lt;/FONT&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;Which is more or less exactly where we started -- using RDF hasn't altered the solution but it has added some framework around it (in this case adding rdf:about to signal the presence of RDF data within the item).&amp;nbsp; However we can go a step further.&amp;nbsp; A useful &lt;A href="http://www.xml.com/pub/a/2001/05/02/semanticwebsite.html"&gt;article&lt;/A&gt; by &lt;A href="http://www.xml.com/pub/au/74"&gt;Eric van der Vlist&lt;/A&gt; discusses this very subject and refers to the &lt;STRONG&gt;RSS1.0&lt;/STRONG&gt; taxonomy module.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;Somewhat counter to what you would expect &lt;A href="http://backend.userland.com/rss"&gt;RSS2.0&lt;/A&gt; does not follow on from &lt;A href="http://www.purl.org/rss/1.0/"&gt;RSS1.0&lt;/A&gt;, nor does RSS1.0 follow on from the popular RSS0.9x formats.&amp;nbsp; RSS1.0 is, depending upon your point of view, a step forward or an aberation.&amp;nbsp; RSS1.0 uses a modular set of RDF based tags to describe items in the RSS feed.&amp;nbsp; One such module is the &lt;A href="http://www.purl.org/rss/1.0/modules/taxonomy/"&gt;Taxonomy module&lt;/A&gt; which is intended to allow classification of RSS channels &amp; items.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;Using the taxonomy module you create something like:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr style="MARGIN-RIGHT: 0px"&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;item rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;permalink&lt;/STRONG&gt;"&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:topics&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:Bag&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:li resource&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;topic-uri-1&lt;/STRONG&gt;&lt;FONT color=blue&gt;"/&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:li resource&lt;/FONT&gt;="&lt;STRONG&gt;topic-uri-2&lt;/STRONG&gt;&lt;FONT color=blue&gt;"/&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;rdf:Bag&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:topics&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;item&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr style="MARGIN-RIGHT: 0px"&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;Here the &lt;topics&gt; element contains a list (using the RDF defined Bag - or unorderer list -&amp;nbsp;container element) of resources indicating topics that describe the item.&amp;nbsp;&amp;nbsp;Each resource then has a &lt;topic&gt;&amp;nbsp;element that describes the topic.&amp;nbsp; It&amp;nbsp; might look something like:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:topic rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;http://matt.blogs.it/topics/topicsT.html#the_state&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:link&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;http://matt.blogs.it/topics/topicsT.html#the_state&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:link&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rsstopics:type&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;generic&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;rsstopics:type&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;BR&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;dc:title&lt;/FONT&gt;&gt;&lt;STRONG&gt;The State&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;dc:title&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;BR&gt;&lt;/FONT&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;taxo:topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;Although it's a jumble of RDF, the RSS1.0 taxonomy module, Dublic&amp;nbsp;Core,&amp;nbsp;and, a custom rsstopics schema this says exactly the same thing as the original:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;&lt;FONT color=#0000ff&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt; &lt;FONT color=maroon&gt;id&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;topic_id&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt; &lt;FONT color=maroon&gt;type&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;topic-type&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&lt;/FONT&gt; &lt;FONT color=maroon&gt;source&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;url&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;STRONG&gt;topic name&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;SPAN class=m&gt;&lt;SPAN class=m&gt;
&lt;P dir=ltr&gt;But do we have to deal with such an&amp;nbsp;ugly mess?&amp;nbsp;&amp;nbsp;Perhaps not.&amp;nbsp; Our original choices&amp;nbsp;included the XML Topic Maps format.&amp;nbsp;&amp;nbsp;This is a complete specification for exchanging topic information.&amp;nbsp; An example of a topic in XTM format might look something like:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P dir=ltr&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt; &lt;FONT color=maroon&gt;id&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;the_state&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;instanceOf&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;topicRef&lt;/FONT&gt; &lt;FONT color=maroon&gt;xlink:href&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;http://www.purl.org/rss-topics/rss-topics#generic&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;instanceOf&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;baseName&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;baseNameString&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;The State&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;baseNameString&lt;/FONT&gt;&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;occurence&lt;/FONT&gt; &lt;FONT color=maroon&gt;id&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;the-state-item&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;instanceOf&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;topicRef&lt;/FONT&gt; &lt;FONT color=maroon&gt;xlink:href&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;http://www.purl.org/rss-topics/rss-topics#story&lt;/STRONG&gt;"&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;instanceOf&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;resourceRef&lt;/FONT&gt; &lt;FONT color=maroon&gt;xlink:href&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;&lt;permalink-uri&gt;&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;occurence&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;Again this encodes the same information, using&amp;nbsp;a standard format and only one required namespace (that of XTM itself).&amp;nbsp;&amp;nbsp;A URI such as &lt;A href="http://www.purl.org/rss-topics/rss-topics#generic"&gt;http://www.purl.org/rss-topics/rss-topics#generic&lt;/A&gt; points at a topic in another map (in this case a topic&amp;nbsp;describing the topic-type &lt;EM&gt;generic&lt;/EM&gt;).&lt;/P&gt;
&lt;P dir=ltr&gt;The use of XTM comes with a number of advantages with the main one being that there are an increasing number of tools available to process &amp; manipulate it (for example, see &lt;A href="http://www.topicmap.com/topicmap/tools.html"&gt;topicmap.com&lt;/A&gt;).&amp;nbsp; However there also a number of problems with this representation when you attempt to embed it within another XML format such as RSS. &lt;/P&gt;
&lt;UL dir=ltr&gt;
&lt;LI&gt;
&lt;DIV&gt;It's not clear whether an XTM fragment such as this is valid when used in this way&lt;/DIV&gt;
&lt;LI&gt;
&lt;DIV&gt;Each time a topic is used we will be duplicating it's details, bloating the markup &amp; potentially creating invalid entries&lt;/DIV&gt;
&lt;LI&gt;
&lt;DIV&gt;The &lt;occurence&gt; relation within the &lt;topic&gt; element is technically redundant.&amp;nbsp;&amp;nbsp;The enclosing &lt;item&gt; indicates the occurrence.&amp;nbsp; &lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;One way to avoid these problems would be to embed the topics within the RSS &lt;channel&gt; definition and refer to them from each &lt;item&gt;.&amp;nbsp; However we still need a way to refer to the topic and XTM doesn't provide this.&amp;nbsp; If we had a good way to reference topics then we could either embed mini topic map within the RSS file, or just have the &lt;topicmap&gt; in an external file and point to it.&amp;nbsp; What could we use?&amp;nbsp; One possibility is RDF.&lt;/P&gt;
&lt;P&gt;Using a combination of RDF and XTM would mean something like:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;item&lt;/FONT&gt; &lt;FONT color=maroon&gt;rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;&lt;permalink-uri&gt;&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;rsstopics:topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;http://www.example.org/myTopicMap.xtm#topic-id&lt;/STRONG&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;rsstopics:topic&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;!-- XTM in an external map --&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=blue&gt;&lt;/&lt;/FONT&gt;&lt;FONT color=maroon&gt;item&lt;/FONT&gt;&lt;FONT color=blue&gt;&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;or&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=blue&gt;&lt;&lt;/FONT&gt;&lt;FONT color=maroon&gt;item&lt;/FONT&gt; &lt;FONT color=maroon&gt;rdf:about&lt;/FONT&gt;&lt;FONT color=blue&gt;="&lt;/FONT&gt;&lt;STRONG&gt;&lt;permalink-uri&gt;&lt;/STRONG&gt;&lt;FONT color=blue&gt;"&gt;&lt;/FONT&gt;&lt;BR&gt;&lt;FONT color=#0000ff&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;&lt;FONT color=maroon&gt;rsstopics:topic&lt;/FONT&gt;&gt;&lt;/FONT&gt;&lt;STRONG&gt;#topic-id&lt;/STRONG&gt;&lt;FONT color=#0000ff&gt;&lt;/&lt;FONT color=maroon&gt;rsstopics:topic&lt;/FONT&gt;&gt;&amp;nbsp; &lt;!-- XTM element inline in the RSS --&gt;&lt;BR&gt;&lt;/&lt;FONT color=maroon&gt;item&lt;/FONT&gt;&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;In this example the item now refers to an XTM defined&amp;nbsp;topic either elsewhere in the RSS feed (contained within a valid &lt;topicmap&gt; element)&amp;nbsp;or within an external topic map.&amp;nbsp; The referenced &lt;topic&gt; element can further describe the topic (names, types and so on)&amp;nbsp;using all the expressiveness of XTM.&amp;nbsp; It's also efficient since there is no duplicated information within the feed.&lt;/P&gt;
&lt;P&gt;I have described approaches using RDF, XTM and a hybrid of the two.&amp;nbsp; Each has advantages and disadvantages although I believe the hybrid makes the best use of both formats.&lt;/P&gt;
&lt;P&gt;I'd welcome comments and or opinions from interested parties.&lt;/P&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001351.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/collaboration.xml" ent:id="collaboration" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/communication.xml" ent:id="communication" 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>Topic Rolls, Controlled vocabulary and the ITE</title>
      <pubDate>Mon, 07 Apr 2003 16:51:49 +0100</pubDate>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="http://matt.blogs.it/2003/03/27.html#a836"&gt;Topic Rolls near reality&lt;/A&gt;. &lt;/P&gt;
&lt;BLOCKQUOTE cite=http://matt.blogs.it/2003/03/27.html#a836&gt;
&lt;P&gt;The next step is to allow liveTopics to import topicrolls from other locations. [&lt;A href="http://radio.weblogs.com/0107808/"&gt;Matt Mower&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Matt expands his work on topic information for Weblog entries. He adds another hierarchical layer by introducing "topic types". This basically allows you to group your containers (topics) into another layer of containers (topic types), thus adding more modelling power to one's own topic structure. Without knowing what really is going on in Italy I would be very cautious with attempts to "define a control language for topics rather than allowing users to make up their own." This is where most projects in this are seem to go the wrong way. At some point someone steps in and wants to take control instead of developing tools that would allow the negotiation of shared topic meanings... [&lt;A href="http://Seblogging.cognitivearchitects.com/SebastianFiedler"&gt;Sebastian Fiedler&lt;/A&gt;]&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://Seblogging.cognitivearchitects.com/"&gt;Seblogging News&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Since Paolo's currently out of &lt;A href="http://paolo.evectors.it/2003/04/07.html#a1559"&gt;range&lt;/A&gt; I guess I should add something here.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.bookcafe.net/blog/aggregator/"&gt;Blog Notes&lt;/A&gt;&amp;nbsp;(Giuseppe Granieri's blog aggegrator project) is a structured news feed &lt;EM&gt;viewer&lt;/EM&gt;.&amp;nbsp; It allows you to&amp;nbsp;attach certain pre-defined topics to a post to indicate such things as:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;the post is an&amp;nbsp;ironic comment&lt;/LI&gt;
&lt;LI&gt;the post is about politics&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;In order to keep the structure under control the range of topics must necessarily be restricted.&amp;nbsp; So in essence the range of topics in Blog Notes forms a controlled vocabulary and liveTopics will, to some extent, support this.&lt;/P&gt;
&lt;P&gt;However that won't mean that people will be unable to create their own topics or interact with other applications that do permit is such as Phil Pearson's &lt;A href="http://topicexchange.com/"&gt;Internet Topic Exchange&lt;/A&gt;.&amp;nbsp;&amp;nbsp;As a sidenote I am very conscious that the work in integrating liveTopics and&amp;nbsp;TopicExchange&amp;nbsp;never got finished.&amp;nbsp; I have it in mind to get in touch with Phil again and see where we are with the outstanding issues.&amp;nbsp; (Phil if you see this and have a moment, please ping me via IM).&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001363.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/ideas.xml" ent:id="ideas" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/linkedin.xml" ent:id="linkedin" 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>Pepping up liveTopics performance</title>
      <pubDate>Mon, 07 Apr 2003 20:40:01 +0100</pubDate>
      <description>&lt;P&gt;I knew that Radio's outline were slow but...&lt;/P&gt;
&lt;P&gt;Internally liveTopics uses Radio's outlines quite a lot.&amp;nbsp; When you are outputting outlines for activeRenderer it seems quite convenient to use Radio's built-in support them as a type.&amp;nbsp; But as my topics database has grown, liveTopics has begun to groan.&amp;nbsp; And this on a pretty zippy P4 1.6GHz, I can only imagine what it must be like for some people out there with somewhat slower machines (Marc?)&lt;/P&gt;
&lt;P&gt;So I took a first cut a few minutes ago at re-writing the liveTopics outline generator and did a little benchmarking.&amp;nbsp; At the moment it takes the Radio outline based generator &lt;FONT color=darkblue&gt;64 seconds&lt;/FONT&gt; to generate the XML for my topic &lt;FONT color=maroon&gt;liveTopics&lt;/FONT&gt; which is the largest topic in my database at 82 posts. By contrast it takes my hand-rolled OPML generator just &lt;FONT color=darkblue&gt;2 seconds&lt;/FONT&gt; to do the same work!&lt;/P&gt;
&lt;P&gt;It will take a little bit of time to replace the current generator properly but I anticipate the performance difference will be startling.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001365.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics go fast now</title>
      <pubDate>Mon, 07 Apr 2003 22:27:26 +0100</pubDate>
      <description>&lt;P&gt;I'm actually pretty pleased with this.&lt;/P&gt;
&lt;P&gt;I wrote a new Table of Contents driver for liveTopics which uses the new OPML generator.&lt;/P&gt;
&lt;P&gt;Now, fully regenerating my table of contents (the whole 239 topics A..Z of it) takes 49 seconds start to finish!&lt;/P&gt;
&lt;P&gt;This was a task that took well in excess of 16 minutes (not counting upstreaming) last time I tried it.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001367.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/complexity-theory.xml" ent:id="complexity-theory" 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/knowledge-management.xml" ent:id="knowledge-management" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/organisational-complexity.xml" ent:id="organisational-complexity" ent:classification="user"/>
      </ent:cloud>
    </item>
    <item>
      <title>Announcing: ENT v1.0 Easy News Topics for RSS2.0</title>
      <pubDate>Fri, 11 Apr 2003 13:59:53 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://www.purl.org/NET/ENT/1.0/"&gt;&lt;IMG alt="Easy News Topics" src="http://matt.blogs.it/specs/ENT/1.0/ENT10.gif" border=0&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://paolo.evectors.it/2003/04/11.html#a1567"&gt;Paolo&lt;/A&gt; and I are pleased to announce the release of the first public draft of the &lt;A href="http://www.purl.org/NET/ENT/1.0/"&gt;Easy News Topics (ENT) specification&lt;/A&gt;.&amp;nbsp; ENT1.0 is an RSS2.0 module designed to make it really easy to incorporate topics into RSS feeds.&amp;nbsp; Why would you want to do that?&amp;nbsp; Because it will help to enable a raft of new, smarter, aggregator products.&lt;/P&gt;
&lt;P&gt;RSS has become very important to a lot of us and we are starting to see its penetration into the business world as well.&amp;nbsp; We think that integrating topics will help aggregators applications to scale to meet the future needs of users as well as delivering some very powerful applications.&amp;nbsp; I've spoken before about the kinds of thing I want my aggregator to do:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;group posts from many feeds by interest. 
&lt;LI&gt;filtering posts I don't want to see 
&lt;LI&gt;scoring &amp; promote posts 
&lt;LI&gt;recombine different&amp;nbsp;feeds dynamically.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I hope that ENT might help bring all these things&amp;nbsp;a little closer.&amp;nbsp; We also see a role for classification in bringing new ways to order, view, and, search&amp;nbsp;weblog data.&lt;/P&gt;
&lt;P&gt;We are offering ENT1.0 to the community (under a &lt;A href="http://creativecommons.org/licenses/by-sa/1.0/"&gt;Creative Commons License&lt;/A&gt;) in the hope that we can foster these applications and many more, that we haven't even begun to think of yet.&lt;/P&gt;
&lt;P&gt;I will soon be releasing to the public the next&amp;nbsp;version of liveTopics which will be ENT compliant.&amp;nbsp; At that point any Radio user will be able to easily add topic metadata to their RSS feed.&amp;nbsp; We hope&amp;nbsp;that there will soon be many applications available to make&amp;nbsp;use of it.&lt;/P&gt;
&lt;P&gt;We look forward to your comments.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001376.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>liveTopics 1.1.3 beta test</title>
      <pubDate>Tue, 15 Apr 2003 21:37:04 +0100</pubDate>
      <description>I've created a &lt;A href="http://linux.evectors.it/wiki/liveTopics/wiki.pl?BetaTesters"&gt;page&lt;/A&gt; for people interested in beta testing liveTopics 1.1.3, please go add yourself if you want to get involved.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001391.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>MyRadio gets ENT</title>
      <pubDate>Mon, 21 Apr 2003 09:45:18 +0100</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://radio.weblogs.com/0100875/2003/04/17.html#a932"&gt;myRadio supports ENT 1.0&lt;/A&gt;. &lt;NOBR&gt;&lt;FONT size=+2&gt;My&lt;/FONT&gt;&lt;IMG src="http://radio.weblogs.com/0100875/images/radioBadge.gif"&gt;&lt;/NOBR&gt; supports &lt;A href="http://matt.blogs.it/specs/ENT/1.0/"&gt;&lt;IMG src="http://matt.blogs.it/specs/ENT/1.0/ENT10-small.gif" border=0&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Announcing the release of &lt;A href="http://matt.blogs.it/specs/ENT/1.0/ENT10-small.gif"&gt;ENT 1.0&lt;/A&gt; (Easy News Topics) support in &lt;A href="http://radio.weblogs.com/0100875/outlines/myRadio/"&gt;myRadio&lt;/A&gt;. One of the stated goals of ENT is to "represent topics sufficiently that they be useful in enabling smart aggregators (e.g. filtering, recombining feeds, etc...)". RSS+ENT feeds can be filtered in myRadio, by selecting topics of interest.
&lt;P&gt;Available topics for a feed are those seen by the aggregator, in the RSS feed. That list will grow in time. Later, myRadio will support topicRolls for this purpose. Future features may also include recombining feeds according to topic.
&lt;P&gt;Update myRadio.root in RU, or download the latest &lt;A href="http://radio.weblogs.com/0100875/gems/myRadio.root"&gt;here&lt;/A&gt;. Configure using the "Edit Topics" link in the myRadio navigation bar. Please contact me with any feedback, suggestions, and bug reports.
&lt;P&gt;Currently, the only known feeds supporting ENT 1.0 are &lt;A href="http://matt.blogs.it/rss.xml"&gt;Curiouser and curiouser&lt;/A&gt; and &lt;A href="http://topicexchange.com/rss"&gt;Topic Exchange&lt;/A&gt;. ENT enabled feeds should increase greatly when liveTopics 1.3.3 is released. [&lt;A href="http://radio.weblogs.com/0100875/"&gt;Brain Off&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Fantastic news.&amp;nbsp; Well done Mikel.
&lt;P&gt;This will be the first application in the hands of users that will let them get the benefit of topics in their feeds.&amp;nbsp; liveTopics 1.1.3 is in beta at the moment and should be available soon.&amp;nbsp; Once that happens there will be a small cluster of feeds that do support ENT.&amp;nbsp; But we need to do more.
&lt;P&gt;Specifically we need to find a way to get at the hordes of MovableType users and get them in the game.
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00001411.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/microsoft-windows.xml" ent:id="microsoft-windows" 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/00001457.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:href="http://matt.blogs.it/topics/danny-ayers.xml" ent:id="danny-ayers" 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/marc-canter.xml" ent:id="marc-canter" ent:classification="user"/>
        <ent:topic ent:href="http://matt.blogs.it/topics/rss-1.0.xml" ent:id="rss-1.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>Not so ancient history</title>
      <pubDate>Sat, 22 Oct 2005 10:36:07 +0100</pubDate>
      <description>&lt;p&gt;Todd Higgins asks me: &lt;a href="http://radio.weblogs.com/0101495/2005/10/21.html#a4"&gt;Is liveTopics still available?&lt;/a&gt;  The answer is: yes and no.&lt;/p&gt;
&lt;p&gt;Back in August I had dinner with &lt;a href="http://radio.weblogs.com/0104487/"&gt;Marc Barrot&lt;/a&gt; and he asked me the same question.  At that time I gave him an email putting the liveTopics code under the &lt;a href="http://www.opensource.org/licenses/mit-license.php"&gt;MIT License&lt;/a&gt; and gave him my blessing to do what he liked with it.  My single caveat was that I didn't want to have to support it.&lt;/p&gt;
&lt;p&gt;The complication to this is that, along the way, I have lost the last distribution file.  It may be on a backup CD somewhere but I'm not hopeful.  I have a few root files of uncertain provenance (works in progress) but nothing else.  Maybe Marc himself as a copy, or perhaps &lt;a href="http://blog.mathemagenic.com/"&gt;Lilia&lt;/a&gt; does?&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00003055.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:53
	</div>
</div>
</div>
</body>
</html>
