<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:ent="http://www.purl.org/NET/ENT/1.0/" version="2.0">
  <channel>
    <title>Curiouser and Curiouser! on software</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic software</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>Software for Information Professionals</title>
      <pubDate>Sun, 07 Jul 2002 12:39:02 +0100</pubDate>
      <description>&lt;P&gt;I'm on the look out for software that improves my lot as an information producer/consumer.&amp;nbsp; I came across &lt;A href="http://argus-acia.com/strange_connections/current_article.html"&gt;this article&lt;/A&gt;&amp;nbsp;by Peter Morville which talks about software for Information Architects.&lt;/P&gt;
&lt;P&gt;He identifies the following categories of tool:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Automated Classification&lt;/LI&gt;
&lt;LI&gt;Automated Category Generation&lt;/LI&gt;
&lt;LI&gt;Search Engines&lt;/LI&gt;
&lt;LI&gt;Thesaurus Management&lt;/LI&gt;
&lt;LI&gt;Collaborative Filtering&lt;/LI&gt;
&lt;LI&gt;Portal Solutions&lt;/LI&gt;
&lt;LI&gt;Content Management&lt;/LI&gt;
&lt;LI&gt;Analytics&lt;/LI&gt;
&lt;LI&gt;Database Management&lt;/LI&gt;
&lt;LI&gt;Information Architecture Productivity&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;(Note some of the tool urls are now dead.&amp;nbsp; This article was written in 2001)&lt;/P&gt;
&lt;P&gt;As an individual I'm more interested in personal solutions than enterprise solutions.&amp;nbsp; This means that I like tools like Copernic Summarizer and Personal Brain which put me in the driving seat.&amp;nbsp; But I hope to have my own servers soon so I'll be interested in bigger solutions too.&lt;/P&gt;
&lt;P&gt;Do you have a tool that you swear by?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000169.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="warblogging" ent:classification="user" ent:href="http://matt.blogs.it/topics/warblogging.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Rich seams of text</title>
      <pubDate>Sun, 07 Jul 2002 12:58:40 +0100</pubDate>
      <description>Tools for mining text from the &lt;A href="http://dmoz.org/Reference/Knowledge_Management/Knowledge_Discovery/Text_Mining/"&gt;OpenDirectory&lt;/A&gt;.</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000171.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="blogging" ent:classification="user" ent:href="http://matt.blogs.it/topics/blogging.xml"/>
        <ent:topic ent:id="community" ent:classification="user" ent:href="http://matt.blogs.it/topics/community.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Why Radio?</title>
      <pubDate>Tue, 16 Jul 2002 22:13:04 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0108194/2002/07/16.html#a132"&gt;Hmm... Ya think?&lt;/A&gt;. See I think that all the cute little features that are being added to Radio are going to "in a few years time" bog it down terribly. However MT is a wad of perl code, which means it can be a point of departure for whatever anyone wants to do with it, without having to learn a proprietary "less than impeccably documented" scripting language (grumble grumble.)
&lt;P&gt;However, initial ramp-up with radio can't be beat (to say nothing of the 40m of cloud space), so here I am.
&lt;P&gt;I like radio alot, but I have to say the more compelling reason to use it over other blogging software is ease of setup &amp; the year of service that comes with using radio.
&lt;P&gt;As a developer, I've given up on trying to do really neat things with radio. It's just too hard to track down the documentation. [&lt;A href="http://radio.weblogs.com/0108194/"&gt;The Universal Church Of Cosmic Uncertainty&lt;/A&gt;]
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;»&lt;/FONT&gt; I think there are two different issues at play here: &lt;FONT color=purple&gt;language&lt;/FONT&gt; and &lt;FONT color=purple&gt;platform&lt;/FONT&gt;.
&lt;P&gt;Is MT a&amp;nbsp;better blogging system than Radio because it is a wad of Perl code rather than a wad of Usertalk code?&amp;nbsp; I'm not sure but I guess so if only because of Perls popularity.&amp;nbsp; Neither would be my first choice for writing a complex application but both are adequate to the task.
&lt;P&gt;But the important issue for me is the platform.&amp;nbsp; I would class MT as an application and Radio (along with Frontier)&amp;nbsp;as a platform.&amp;nbsp;&amp;nbsp;In particular an ideal platform for delivering groupware applications.&amp;nbsp; 
&lt;P&gt;Here's an example from my experience:&amp;nbsp; About 5 years ago att UNL we were looking for a learning mangament system for lecturers to use to construct &amp; deliver on-line courses.&amp;nbsp; A question which stymied most vendors we spoke to was:
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;"How do you handle a lecturer who wants to update his module whilst on a cycling holiday in the south of france?"&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;For the most part they had no answer to the disconnected scenario and had to bluff or fall back to legacy software "Oh they can edit stuff in Word and then C&amp;P when they get back."&amp;nbsp; Right...
&lt;P dir=ltr&gt;I can imagine constructing some very novel solutions to this kind of scenario with a combination of Radio &amp; Frontier.&amp;nbsp; I can imagine some novel applications for k-logging too.
&lt;P dir=ltr&gt;It's the flexibility and power of the platform that I'm betting on.
&lt;P dir=ltr&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000223.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="business" ent:classification="user" ent:href="http://matt.blogs.it/topics/business.xml"/>
        <ent:topic ent:id="culture" ent:classification="user" ent:href="http://matt.blogs.it/topics/culture.xml"/>
      </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/00000291.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="rss" ent:classification="user" ent:href="http://matt.blogs.it/topics/rss.xml"/>
      </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/00000292.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="dns" ent:classification="user" ent:href="http://matt.blogs.it/topics/dns.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Making a living selling Open Source software</title>
      <pubDate>Tue, 20 Aug 2002 13:03:26 +0100</pubDate>
      <description>&lt;P&gt;Okay I'm reading &lt;A href="http://www.opensource.org/advocacy/case_for_business.php"&gt;stuff&lt;/A&gt; about how to make a living "selling" open source software (free software as &lt;A href="http://www.gnu.org/philosophy/free-software-for-freedom.html"&gt;GNU would have it&lt;/A&gt;).&amp;nbsp; It seems that the model held up by most people is &lt;A href="http://www.redhat.com/"&gt;Red Hat&lt;/A&gt; who sell Linux.&amp;nbsp; A brief look at their web page indicates that professional services is a big part of their business.&lt;/P&gt;
&lt;P&gt;Does anyone have a view on this model?&amp;nbsp; How about "selling" a much smaller, less commoditized product, in the KM marketplace?&amp;nbsp; I'm not sure...&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/00000293.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="blogging" ent:classification="user" ent:href="http://matt.blogs.it/topics/blogging.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>More on licensing, closer to a decision</title>
      <pubDate>Tue, 20 Aug 2002 14:41:26 +0100</pubDate>
      <description>&lt;P&gt;Okay I've just read the first document that is really convincing.&amp;nbsp; It's by the guys behind Zope and discusses in detail their reasons for going open source.&amp;nbsp; This is the first concrete business-plan backed reasoning I've come across and it makes for compelling reading.&amp;nbsp; Just need to go check that Zope are still in business!&lt;/P&gt;
&lt;P&gt;Here are the important points:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Going open source will increase our user base by a factor of 100 within three months. Wider brand and stronger identity leads to more consulting and increased valuation on our company.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Open source gives rock solid, battle-tested, bulletproof software on more platforms and with more capabilities than closed source, thus increasing the value of our consulting.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;&lt;FONT color=red&gt;Fostering a community creates an army of messengers, which is pretty effective marketing.&lt;/FONT&gt;&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;&lt;FONT color=red&gt;This is not the last innovation we'll make.&lt;/FONT&gt;&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;&lt;FONT color=red&gt;In the status quo, the value of packaging the software as a product would approach zero, as we had zero market penetration. What is the value of a killer product with few users? The cost to enter the established web application server market was going to be prohibitive.&lt;/FONT&gt;&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;The investment grows us into a larger, more profitable company, one that can make a credible push to create a platform via open source. Since our consulting is only on the platform, a strong platform is imperative.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Open source makes the value of our ideas more apparent, thus the perceived value of the company is apparent.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Our architecture is "safer" for consulting customers. With thousands of people using it, the software is far less marginal. The customer is able to fix things themselves or reasonably find someone to do it for them. Finally, the software will "exist forever".&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Dramatically increasing the base of users and sites using it gives us a tremendous boost in "legitimacy".&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;&lt;FONT color=red&gt;The exit plan isn't about the golden eggs (the intellectual property) laid last year. It is about the golden goose and tomorrow's golden eggs. The shelf life of eggs these days is shrinking dramatically, and the value of an egg that no one knows about is tiny. Give the eggs away as a testament to the value of the goose and a prediction of eggs to come.&lt;/FONT&gt;&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;The community can work with us to dramatically increase the pace of innovation and responsiveness to new technical trends, such as XML and WebDAV.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;Ride the coattails of the nascent Open Source community and its established channels such as RedHat. OSS has a certain buzz that is greater than its real customer-closing value, but this buzz is getting hot. Moving aggressively towards Open Source can make us a category killer for the web application server market segment.&lt;/P&gt;
&lt;LI&gt;
&lt;P&gt;&lt;FONT color=red&gt;We believe like hell in what we're doing. Others believe in us as well. We should follow our instincts.&lt;/FONT&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Some of these issues are obviously more important to a company having taken investment with it's eye on a future IPO but I think they are all good, important points.&amp;nbsp; Those that seem most applicable (and inherently good) to me I've marked in red.&amp;nbsp;&amp;nbsp; They seem very persuasive.&lt;/P&gt;
&lt;P&gt;One implication is that the direction of my company will be entirely towards VAR services &amp; consulting.&amp;nbsp; I shall be abandoning the idea of making money from software licenses (for my own software).&lt;/P&gt;
&lt;P&gt;Something to think about...&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000298.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="shrub" ent:classification="user" ent:href="http://matt.blogs.it/topics/shrub.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>The real argument is e-gov should be open</title>
      <pubDate>Tue, 20 Aug 2002 22:53:14 +0100</pubDate>
      <description>&lt;P&gt;In the former case its patents and proprietary file formats, in the latter case its misuse of the law. Where is the integrity in either case? So, lets use software written by developers who show each other respect and integrity, by developers who wouldnt lock down our choice and our data by legialation or non-openness. It isnt commercial vs. open source, but rather, closed against open. The Intellectual Property (and Thought) police against the common man. Lets not lose perspective! [&lt;A href="http://tig.nareau.com/"&gt;TIG's Corner&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; Hmmm... I'm not sure that a law that specifies that governments have to use open source software is "misuse of the law".&amp;nbsp; You may find it not to your liking, you may not agree with it, but I don't see how it's a misuse.&amp;nbsp; Also I think it's very hard to legislate respect.&lt;/P&gt;
&lt;P&gt;I do agree that the real argument should be about open vs. closed (read proprietary).&amp;nbsp; &lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000306.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="effectiveness" ent:classification="user" ent:href="http://matt.blogs.it/topics/effectiveness.xml"/>
        <ent:topic ent:id="learning" ent:classification="user" ent:href="http://matt.blogs.it/topics/learning.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Licensing: My brain hurts</title>
      <pubDate>Thu, 29 Aug 2002 14:28:28 +0100</pubDate>
      <description>&lt;P&gt;Here's something I don't understand:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;FONT color=red&gt;My rights as the author and copyright holder of a piece of software I have written.&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I just don't understand them.&amp;nbsp; And, hence, I do not understand what I may or may not be giving away.&amp;nbsp; Example: If I publish a program under the GPL am I still the owner of the software?&amp;nbsp; In what sense?&lt;/P&gt;
&lt;P&gt;I've had conflicting opinions about the merits of going open source for my liveTopics program.&amp;nbsp; Before I make a final decision I want to really understand what I am doing either way and what I am, potentially, giving up.&lt;/P&gt;
&lt;P&gt;Example scenario:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;liveTopics 1.0 is published as an open source program under the GPL.&amp;nbsp;&amp;nbsp; For whatever reason though the project does not thrive.&amp;nbsp; In the mean time I see commercial possibilities for the project with further significant development effort.&amp;nbsp; I create version 2.0 of liveTopics.&lt;/P&gt;
&lt;P&gt;Am I bound by my own license to release it under the GPL?&amp;nbsp; Or do I have the right, as the owner, to decide I want to use a different license?&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I'd really love someone to help me answer these kind of questions, it's frazzling my brain trying to understand this stuff.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000344.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="business" ent:classification="user" ent:href="http://matt.blogs.it/topics/business.xml"/>
        <ent:topic ent:id="k-log" ent:classification="user" ent:href="http://matt.blogs.it/topics/k-log.xml"/>
        <ent:topic ent:id="leaky-pipes" ent:classification="user" ent:href="http://matt.blogs.it/topics/leaky-pipes.xml"/>
        <ent:topic ent:id="livetopics" ent:classification="user" ent:href="http://matt.blogs.it/topics/livetopics.xml"/>
        <ent:topic ent:id="software" ent:classification="user" ent:href="http://matt.blogs.it/topics/software.xml"/>
        <ent:topic ent:id="strategy" ent:classification="user" ent:href="http://matt.blogs.it/topics/strategy.xml"/>
        <ent:topic ent:id="trust" ent:classification="user" ent:href="http://matt.blogs.it/topics/trust.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Copyright expiry can work</title>
      <pubDate>Fri, 30 Aug 2002 11:01:14 +0100</pubDate>
      <description>&lt;P&gt;&lt;A href="http://scriptingnews.userland.com/moresSource"&gt;Dave Winer on releasing MORE's source&lt;/A&gt;. (SOURCE:&lt;A href="http://www.scripting.com/"&gt;Scripting News&lt;/A&gt;)-&lt;I&gt;OK, this makes sense now. I agree the system wouldn't work. Thanks Dave!&lt;/I&gt;&lt;BR&gt;&lt;QUOTE&gt;&lt;BR&gt;Maybe this simplified story will shed some light on the realities of software development. Had we been forced to release the source, I don't think we could have sold our investors on taking a chance on us, or realized the great return we got from the Symantec deal, and gone on to develop more software. The system you describe just wouldn't work, you wouldn't get any of it. Basically, I would love it if the source for MORE were released. I think it would be a humantarian contribution of the first order, but it's not mine to make. &lt;BR&gt;&lt;/QUOTE&gt;[&lt;A href="http://www.rolandTanglao.com/"&gt;Roland Tanglao's 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; Okay I wasn't going to jump in on this but I think Dave may have misunderstood Lessig's proposal.&amp;nbsp; I think 10 year copyright expiry could work.&lt;/P&gt;
&lt;P&gt;This is what I understand from &lt;A href="http://cyberlaw.stanford.edu/lessig/blog/archives/cooper.html"&gt;Larry Lessig's&lt;/A&gt; proposal about copyright expiry after 10 years:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;The source code would be de-escrowed after 10 years.&amp;nbsp; But only the source code whose copyright has expired.&amp;nbsp; By publishing a new version (e.g. Version 2)&amp;nbsp;of the software you establish a new copyright &lt;EM&gt;checkpoint&lt;/EM&gt;.&amp;nbsp; Your version 2 doesn't get de-escrowed for 10 more years after it is released.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;So here are my reasons:&lt;/P&gt;
&lt;OL dir=ltr&gt;
&lt;LI&gt;
&lt;DIV&gt;I do not think that the possession of a 10 year old version of the software is going to put you in a competitve position against the holder of the latest &amp; greatest source code.&amp;nbsp; It would be like trying to market Windows 3.0 against Windows XP.&lt;/DIV&gt;&lt;/LI&gt;
&lt;LI&gt;
&lt;DIV&gt;If investors had the choice between a company who kept the source code proprietary forever and one who had to publish after 10 years then I agree, they would pick the former.&amp;nbsp; But this will be a level playing field.&amp;nbsp; Everyone will have to publish their source code after 10 years.&amp;nbsp; It won't be an issue.&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Of course maybe I've misunderstood Lessig..?&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000345.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="tools" ent:classification="user" ent:href="http://matt.blogs.it/topics/tools.xml"/>
      </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/00000382.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>What a crock of shit</title>
      <pubDate>Thu, 26 Sep 2002 14:57:23 +0100</pubDate>
      <description>&lt;P&gt;So, ever since I installed Service Pack 1 for Windows XP&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Outlook 2002 runs painfully slowly.&amp;nbsp; Where it used to be fine, now it takes 4-5 seconds after I click a message before it appears in the preview pane.&amp;nbsp; Clicking multiple messages to delete spam also takes 2-3 seconds each. 
&lt;LI&gt;My start bar menus now flicker.&amp;nbsp; Even when the mouse is stationary I can see it flickering like it's constantly redrawing the menu. 
&lt;LI&gt;Same thing for all my context menus.. Bah!
&lt;LI&gt;My QuickCam software crashes and I can't undock any more because "Your camera cannot be stopped.&amp;nbsp; Please try later"&amp;nbsp; Yeah, right.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;So the net result of my upgrade?&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;I have a new, more invasive license 
&lt;LI&gt;I have a machine that is slower and less reliable&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Well thanks for &lt;EM&gt;fucking nothing&lt;/EM&gt; you &lt;FONT color=red&gt;M$crosoft shitheads&lt;/FONT&gt;.&lt;/P&gt;
&lt;P&gt;I declare XP1 to be spam!&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000427.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="pigopoly" ent:classification="user" ent:href="http://matt.blogs.it/topics/pigopoly.xml"/>
        <ent:topic ent:id="tv" ent:classification="user" ent:href="http://matt.blogs.it/topics/tv.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Software tools for information overload</title>
      <pubDate>Fri, 04 Oct 2002 12:40:23 +0100</pubDate>
      <description>&lt;A href="http://radio.weblogs.com/0108194/2002/10/03.html#a409"&gt;Tinderbox, Mind Map Pro, and Inspiration 7 overview (v0.1)&lt;/A&gt;. 
&lt;BLOCKQUOTE&gt;&lt;/BLOCKQUOTE&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;&lt;FONT color=red&gt;»&lt;/FONT&gt; Mike's review of Tinerbox, Mind Map Pro and Inspiration is too long to repost here but is a fascinating insight into three interesting pieces of software.&lt;/P&gt;
&lt;P&gt;I have been interested in&amp;nbsp;&lt;A href="http://www.eastgate.com/Tinderbox/"&gt;Tinderbox&lt;/A&gt; for some time.&amp;nbsp; It was through Tinderbox that I got into weblogging in the first place and I wait with anticipation for the Window port to come out.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000442.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="intranets" ent:classification="user" ent:href="http://matt.blogs.it/topics/intranets.xml"/>
      </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/00000477.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Anthracite Software</title>
      <pubDate>Fri, 25 Oct 2002 12:27:35 +0100</pubDate>
      <description>&lt;A href="http://www.docuverse.com/blog/donpark/2002/10/25.html#a109"&gt;My Response to Larry Lessig&lt;/A&gt;. 
&lt;P dir=ltr&gt;Documents about Chandler&amp;nbsp;talks about various "killer features".&amp;nbsp;&amp;nbsp;Killer features are intended to kill something.&amp;nbsp;&amp;nbsp;If Chandler kills Outlook, we'll have&amp;nbsp;Chandler where we used to have Outlook.&amp;nbsp; Nothing really changed except now no one is making a dime instead of the Bully making all the money.&amp;nbsp; The consumers will love it of course and learn to take free software as the norm.&amp;nbsp; How dare you charge money for what should be free?&amp;nbsp; The service sector will eventually get nothing in return because consumer software will be so easy to use and customize that they won't need any help.&amp;nbsp; The book industry will live a little longer.&amp;nbsp; No wonder Tim O'Reilly is so strongly pushing open source and free software.&amp;nbsp;&amp;nbsp;How about free books too Tim?&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://www.docuverse.com/blog/donpark/"&gt;Don Park's Blog&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; This argument seems to boil down to:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;Does the software industry have a &lt;STRONG&gt;right&lt;/STRONG&gt; to survive?&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I would argue that it does not, and that it should survive only so long as it serves a purpose.&lt;/P&gt;
&lt;P&gt;Now, obviously, as someone with a background (albeit not such a long one as Don) in software development this is a sore point for me.&amp;nbsp; I too would like to make money from the things I create.&amp;nbsp; Would I relish the idea of a group of open source developers blowing my business model by undercutting me?&amp;nbsp; No, of course not.&amp;nbsp; Will it happen?&amp;nbsp; Yes, eventually I believe it will.&amp;nbsp; I just have to be ready for that.&lt;/P&gt;
&lt;P&gt;I think that what we are seeing is the beginning of the end of software as a production business.&amp;nbsp; Any attempts we make to shore up the traditional software industry will be no more than protectionism and about as effective as government attempts to shore up coal and steel when it was undercut by cheap foreign imports.&lt;/P&gt;
&lt;P&gt;In the future those who develop software will do so because of a love of the craft (and true craftsmen may still be able to sell what they product in niche markets) or because they can sell services on top of that software.&lt;/P&gt;
&lt;P&gt;That's what I think right now.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000506.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="politics" ent:classification="user" ent:href="http://matt.blogs.it/topics/politics.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Microsoft Blogger</title>
      <pubDate>Fri, 01 Nov 2002 15:26:17 +0000</pubDate>
      <description>&lt;P&gt;Anil Dash: &lt;A href="http://www.dashes.com/magazine/backissues/microsofts_weblog_software.php"&gt;Microsoft's Weblog Software&lt;/A&gt;. [&lt;A href="http://www.scripting.com/"&gt;Scripting News&lt;/A&gt;]&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;» The only thing wrong with this is that Microsoft won't use the words 'weblog', 'blog', 'weblogger', etc...&amp;nbsp; They wouldn't use such old tired terminology when they could invent new and improved (and trademarked) terminology of their own!&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000523.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="software" ent:classification="user" ent:href="http://matt.blogs.it/topics/software.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Another IDEA convert</title>
      <pubDate>Sun, 08 Dec 2002 10:24:57 +0000</pubDate>
      <description>&lt;P&gt;When &lt;A href="http://www.intellij.com/"&gt;IDEA&lt;/A&gt; v3.0 was released recently I thought I would evaluate it again and I'm glad I did.&amp;nbsp; This is a good software.&lt;/P&gt;
&lt;P&gt;I've used every version of JBuilder and seen it mature from a piece of crap, to a great IDE, and on to a&amp;nbsp;rather swollen mess.&amp;nbsp; I don't think the IDE part of JBuilder has improved much in the last few releases, Borland have choosen to concentrate on other areas.&amp;nbsp;IDEA on the other hand is impressive.&amp;nbsp; It works very smoothly, it's features are intelligent (like folding that works,&amp;nbsp;and fantastic code completion).&amp;nbsp; It also has the best refactoring support I've seen so far.&amp;nbsp; As a coders tool IDEA looks &lt;EM&gt;very&lt;/EM&gt; good.&lt;/P&gt;
&lt;P&gt;About the only significant downside for me is the lack of a GUI builder.&amp;nbsp;I guess if you're only doing J2EE based (I'm not qualified to evaluate the J2EE support) that's not a problem.&amp;nbsp; For me, it is.&amp;nbsp; I don't particularly like the JBuilder GUI designer or the code it creates, but it is better than nothing.&lt;/P&gt;
&lt;P&gt;So, in short, IDEA goes on the wish list.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000618.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Hiring a KM system, the old fashioned way</title>
      <pubDate>Thu, 02 Jan 2003 15:33:34 +0000</pubDate>
      <description>&lt;P&gt;I read a lot about calculating ROI for Knowledge Management.&amp;nbsp; I also hear a fair amount about problems with doing so.&amp;nbsp; I think this is because:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;the value of knowledge&amp;nbsp;is, in general,&amp;nbsp;not well understood, e.g. how much is a new product worth? (it's particularly difficult when considering the risks involved with developing new knowledge and the opportunity cost in exploiting it) 
&lt;LI&gt;the relative value of different &lt;EM&gt;chunks&lt;/EM&gt; of knowledge can be hard to estimate 
&lt;LI&gt;it's often hard to know what impact a KM system has had in capturing or&amp;nbsp;leveraging knowledge, particularly before the fact 
&lt;LI&gt;knowledge is so tightly interwoven into the fabric of what we do that it can be hard to make sensible comparisons&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;In many ways I am inclined to think of ROI as a red-herring.&amp;nbsp; Here's my theory:&lt;/P&gt;
&lt;P&gt;At some point, somewhere, some accountant said: "Hey! We're spending all this money on IT equipment, but what does it ever do for us?"&amp;nbsp;Then some clever person with a background in selling plant equipment or something said "let's use a funky calculation to make it seem like it saves lots of money."&amp;nbsp; And they did, and, fortunately, nobody ever went back to check the figures.&amp;nbsp; This quickly became the industry norm because the purchasing process was now so much easier "Look, the ROI numbers are great!"&amp;nbsp; Then came the great budget squeeze, the sky fell and everyone is wondering how to justify spending.&amp;nbsp; Suddenly we're stuck with ROI and we don't really know what it means.&lt;/P&gt;
&lt;P&gt;I'm not saying that ROI is specifically bad, just that it may not be applicable in all cases and that coming up with some arbitrary way of calculating things to satisfy the bean counters seems a poor justification for using, or not using, a knowledge management approach.&lt;/P&gt;
&lt;P&gt;But is there another way?&lt;/P&gt;
&lt;P&gt;I think so.&lt;/P&gt;
&lt;P&gt;I believe that knowledge is a fundamental aspect of our work.&amp;nbsp; If it wasn't then why would you bother with interviewing to fill new positions? With job specs?&amp;nbsp; With resumes?&amp;nbsp; If knowledge wasn't important then the first&amp;nbsp;joe off the streets could fill any position (the goal of any turnkey business).&lt;/P&gt;
&lt;P&gt;So when you hire a new member of staff you are really buying &lt;FONT color=maroon&gt;packaged knowledge &lt;/FONT&gt;&lt;EM&gt;off the shelf&lt;/EM&gt;.&amp;nbsp; Recruitment agents are really nothing more than knowledge shops! (And like all shops the service and quality of the product may vary).&lt;/P&gt;
&lt;P&gt;But when you hire new staff members do you ask "What's the ROI on this position?"&amp;nbsp; Well I guess you might, but I think it is more usual to work a different way around:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;"We need to do X.&amp;nbsp; Hmm... we don't have anyone available.&amp;nbsp; Okay let's hire someone.&amp;nbsp; What's the market value of those skills?&amp;nbsp; We can't afford that!! Oh, alright then..."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;and so on.&amp;nbsp; A job description gets posted, resumes are sorted, interviews are held, someone is appointed.&amp;nbsp; Usually on a 3 or 6 month probation period.&amp;nbsp; At that point you decide whether to keep them (the need is being fulfilled) or let them go (their not right for the job, or the situation has changed).&lt;/P&gt;
&lt;P&gt;The key point for me is that the determination is not &lt;FONT color=maroon&gt;what is the ROI on this person&lt;/FONT&gt; but &lt;FONT color=maroon&gt;does the need get fulfilled at a price we can justify&lt;/FONT&gt;.&amp;nbsp; It's more about needs &amp; their fulfillment than it is about costs &amp; investment.&lt;/P&gt;
&lt;P&gt;And so, I think, it should be for knowledge management.&amp;nbsp; I believe companies would be more successful if they took the approach that buying a KM package was more like hiring a new employee or two&amp;nbsp;(the capital costs are likely not dissimilar for SME's).&lt;/P&gt;
&lt;P&gt;Start with an understanding of &lt;FONT color=red&gt;what the needs are that must be fulfilled&lt;/FONT&gt;.&amp;nbsp; Ask how much it's worth to you to fulfill those needs.&amp;nbsp; Get the software on probation.&amp;nbsp; Run with it.&amp;nbsp; Then buy it, or go back to the market.&lt;/P&gt;
&lt;P&gt;I think you will find that, by the time you have a firm understanding of what your knowledge needs are, you will more than understand where the ROI comes from (even if your calculator displays it as "a suffusion of yellow!")&lt;/P&gt;
&lt;P&gt;Comments?&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:cloud>
    </item>
    <item>
      <title>Transmorpher 1.0 announced</title>
      <pubDate>Mon, 06 Jan 2003 16:44:50 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;Transmorpher 1.0&lt;/P&gt;
&lt;P&gt;Fluxmedia and INRIA are pleased to announce the availability of Transmorpher 1.0. Transmorpher is a software tool for defining and processing complex transformations of XML documents. It can accept external transformations (e.g., XSLT stylesheets) and provide a simple transformation language offering unit transformations (suppression, renaming, regular expression substitutions and query facilities). In addition to generating, transforming and serializing XML documents, it features constructors like merging, dispatching, querying, iterating, and composing transformations. These transformations can have several input and output streams. New implementation of these constructors can be plugged in Transmorpher. Transmorpher can be used as a compiler, an interpreter, a Ant task, a Servlet generator or embeded in another program.&lt;/P&gt;
&lt;P&gt;Transmorpher 1.0 is written in Java 1.3. It is the first full implementation of Transmorpher as presented in [1]. This version does not put emphasis on performances that we will consider in ulterior version but on functions. Transmorpher takes advantage of external resources (XML parsers, XSLT servers, Regular expression substituers and many other optionnal components). A graphic user interface, FlowComposer(&lt;A href="http://www.fluxmedia.fr/flowcomposer/"&gt;http://www.fluxmedia.fr/flowcomposer/&lt;/A&gt;), is under development at Fluxmedia.&lt;/P&gt;
&lt;P&gt;Transmorpher is available to everyone (sources included) from &lt;A href="http://transmorpher.inrialpes.fr/"&gt;http://transmorpher.inrialpes.fr&lt;/A&gt; under the GPL license (other licenses possible). Transmorpher is a joint development of the Exmo team(&lt;A href="http://www.inrialpes.fr/exmo"&gt;http://www.inrialpes.fr/exmo&lt;/A&gt;) of INRIA Rhône-Alpes and Fluxmedia. Its development is being supported by a ODL grant from INRIA.&lt;/P&gt;
&lt;P&gt;[1] Jérôme Euzenat, Laurent Tardif, XML transformation flow processing, Markup languages: theory and practice 3(3):, 2002 (a pre-version is available at &lt;A href="http://transmorpher.inrialpes.fr/wpaper/"&gt;http://transmorpher.inrialpes.fr/wpaper/&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Contact: &lt;A href="mailto:transmorpher-dev@inrialpes.fr"&gt;transmorpher-dev@inrialpes.fr&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;From &lt;A href="mailto:xml-dev@lists.xml.org"&gt;xml-dev@lists.xml.org&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;This looks like a very interesting piece of software for augmenting XML processing in cases where XSLT is required, but too complex or unable to perform certain operations.&amp;nbsp; Or for structured processing involving a number of operations in sequence.&amp;nbsp; I like the sound of the FlowComposer as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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:cloud>
    </item>
    <item>
      <title>Looking for my next aggregator</title>
      <pubDate>Wed, 08 Jan 2003 23:15:36 +0000</pubDate>
      <description>&lt;P&gt;Okay this is a real problem with the Radio news aggregator.&amp;nbsp; There is an RSS item that I know is in there somewhere, I saw it this afternoon, but I can't find it.&lt;/P&gt;
&lt;P&gt;It has been buried by a mountain of new items.&amp;nbsp; As far as I can tell the only way to find it again is to delete enough items that Radio will show it on the news page again.&amp;nbsp; Oh I guess that I can find the feed URL and fake a URL for the Zoom feature to display all items from that feed... (since the feed doesn't appear on the news page at all right now).&lt;/P&gt;
&lt;P&gt;As I come to depend more and more upon RSS to keep track of the life &amp; work of the people I am becoming friends and colleagues with I am increasingly finding that the Radio aggregator doesn't cut it.&amp;nbsp; This is just one of a number of items that are bugging me and I don't have time to address, even if I thought it was a worthwhile exercise.&lt;/P&gt;
&lt;P&gt;I'd really like to try out some of the alternatives.&amp;nbsp; Can anyone &lt;FONT color=maroon&gt;recommend&lt;/FONT&gt; any aggregator software?&amp;nbsp; It must run on&amp;nbsp;Windows (so don't suggest &lt;EM&gt;iNews&lt;/EM&gt;) and ideally it should be written in Java (but that's just a nice to have).&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000670.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/00000679.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="how-to-develop-software" ent:classification="user" ent:href="http://matt.blogs.it/topics/how-to-develop-software.xml"/>
        <ent:topic ent:id="java" ent:classification="user" ent:href="http://matt.blogs.it/topics/java.xml"/>
        <ent:topic ent:id="music" ent:classification="user" ent:href="http://matt.blogs.it/topics/music.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>The purple cow of knowledge</title>
      <pubDate>Tue, 18 Feb 2003 11:25:37 +0000</pubDate>
      <description>&lt;P&gt;I've been reading &lt;A href="http://pf.fastcompany.com/online/67/purplecow.html"&gt;In Praise of the Purple Cow&lt;/A&gt; in which the&amp;nbsp;author, Seth Godin, proposes that, in order to be truly successful,&amp;nbsp;a product must be &lt;FONT color=purple&gt;&lt;STRONG&gt;remarkable&lt;/STRONG&gt;&lt;/FONT&gt;.&amp;nbsp; His claim is that being &lt;EM&gt;very good&lt;/EM&gt; is also failure.&amp;nbsp; These days everyone is good or very good, you &lt;STRONG&gt;have&lt;/STRONG&gt; to be remarkable to stand out and get the notices (good and bad).&lt;/P&gt;
&lt;P&gt;The purple cow idea&amp;nbsp;jives very much with what I've read of Gary Hamel's notion of how&amp;nbsp;revolutionary approaches create new markets and deliver profits.&amp;nbsp; Unless you also invest in new purple cows then building upon success is the road to stagnation.&amp;nbsp; Ask AOL, Palm and Yahoo.&amp;nbsp; This idea &lt;EM&gt;feels&lt;/EM&gt; right to me.&lt;/P&gt;
&lt;P&gt;Which lead me to thinking about knowledge management products and how so many of them are good, but hardly remarkable.&amp;nbsp; &lt;A href="http://www.thebrain.com/"&gt;Personal Brain&lt;/A&gt; is a remarkable product which was never exploited.&amp;nbsp;&amp;nbsp; The &lt;A href="http://c2.com/cgi/wiki"&gt;Wiki&lt;/A&gt; idea was remarkable, but none of the Wiki software I've used has been.&amp;nbsp; In fact when I think about it, the whole field of KM is dominated by the idea of being &lt;EM&gt;good enough&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;For example &lt;A href="http://www.opentext.com/"&gt;OpenText Livelink&lt;/A&gt; is&amp;nbsp;a very successful KM product.&amp;nbsp; Which gives you some idea of the state of that market.&amp;nbsp; Livelink is a&amp;nbsp;&lt;EM&gt;well-dressed&lt;/EM&gt; document management system.&amp;nbsp; Hardly innovative, definitely not purple cow territory.&amp;nbsp; But it's been successful.&amp;nbsp; Why is that?&lt;/P&gt;
&lt;P&gt;I think the answer is partly about OpenText being an aggressive sales driven company, partly that the KM market is dominated by large, conservative, corporations, and partly because the whole market is ripe, waiting for a &lt;STRONG&gt;&lt;FONT color=purple&gt;real&lt;/FONT&gt; &lt;/STRONG&gt;purple cow.&lt;/P&gt;
&lt;P&gt;Can anyone say "Moo!?!"&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000749.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="mozilla" ent:classification="user" ent:href="http://matt.blogs.it/topics/mozilla.xml"/>
        <ent:topic ent:id="radio-userland" ent:classification="user" ent:href="http://matt.blogs.it/topics/radio-userland.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Free XML editor</title>
      <pubDate>Thu, 27 Feb 2003 09:28:02 +0000</pubDate>
      <description>&lt;FONT size=2&gt;
&lt;P&gt;Altova Offers Free Software License for Authentic 5 Browser Enabled XML Document Editor.&lt;/P&gt;
&lt;P&gt;Altova Inc. has announced the public availability of Altova's XML document editor product Authentic 5 under a free software license. Authentic 5 is a customizable, light-weight, and easy-to-use XML document editor. It allows business users to create and edit content through a web-enabled interface that resembles a word processor. Authentic 5 supports WebDAV and HTTP, with real-time document validation and multilingual spell checking. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;[From &lt;A href="http://xml.coverpages.org/ni2003-02-20-a.html"&gt;Cover&amp;nbsp;Pages Newsletter&lt;/A&gt;]&lt;/P&gt;
&lt;P&gt;Checking it out now.&amp;nbsp; I already use &lt;A href="http://www.altova.com/products_ide.html"&gt;XML Spy&lt;/A&gt; but this might be a better choice when editing markup for my new website (which I am hoping to deploy using &lt;A href="http://www.shelter.nu/xsiteable/"&gt;xSiteable&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Thank you &lt;A href="http://www.altova.com/"&gt;Altova&lt;/A&gt;.&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000774.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="email" ent:classification="user" ent:href="http://matt.blogs.it/topics/email.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>Follow your nose (almost)</title>
      <pubDate>Mon, 17 Mar 2003 14:14:18 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;What are you looking at?. &lt;IMG src="http://paolo.evectors.it/myImages/srlabs.gif" align=right&gt;This morning a friend of mine, &lt;A href="http://luca.srlabs.it/"&gt;Luca Reginato&lt;/A&gt;, who works at &lt;A href="http://www.srlabs.it/"&gt;SrLabs&lt;/A&gt; in Padova sent me &lt;A href="http://paolo.evectors.it/stories/eyeTracking.html"&gt;&lt;B&gt;this very cool movie&lt;/B&gt;&lt;/A&gt;. Using a technology that they are developing, he tracked his eyes movements while browsing my weblog. The blue spot you will see in the movie shows where he is looking, the larger the spot becomes, the longer he has been looking at a specific item. It's really amazing. While today these services are available mainly to large companies (with large budgets), I'm trying to convince Luca that such a service made available at affordable prices would not only make sense, but be profitable. How much would you pay to have this kind of feed-back on a site you are designing or that you already have? [&lt;A href="http://paolo.evectors.it/"&gt;Paolo Valdemarin: Paolo's Weblog&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P dir=ltr&gt;This is way cool.&amp;nbsp; I want a version of this software for $99 that runs on my PC and uses my webcam.&lt;BR&gt;&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000808.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="google" ent:classification="user" ent:href="http://matt.blogs.it/topics/google.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>InfoPath: Golden path or mantrap</title>
      <pubDate>Tue, 18 Mar 2003 11:18:09 +0000</pubDate>
      <description>&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;A href="http://www.docuverse.com/blog/donpark/2003/03/17.html#a358"&gt;OneNote and InfoPath&lt;/A&gt;. &lt;/P&gt;
&lt;P&gt;I just saw the demos for OneNote and InfoPath.&amp;nbsp; OneNote is just a glorified Notepad, no where as good as NoteTaker is.&amp;nbsp; InfoPath, on the other hand, is going to be a catalyst, an monster underwater earquake that will start a tsunami of changes across industries.&amp;nbsp; Its going to generate Office suite upgrade momentum as well as Microsoft server and middleware software sales.&amp;nbsp; Buy Microsoft stock.&amp;nbsp; Their revenue will rise sharply in the near future because of InfoPath.&amp;nbsp; I am not exaggerating, folks.&lt;/P&gt;
&lt;P&gt;[&lt;A href="http://www.docuverse.com/blog/donpark/"&gt;Don Park's Blog&lt;/A&gt;]&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Reading Don's blog these past few months I've come to trust his judgement on this kind of thing.&amp;nbsp; The InfoPath &lt;A href="http://www.microsoft.com/office/preview/infopath/demo/sniff/enter.html"&gt;demo&lt;/A&gt; certainly offers&amp;nbsp;some attractive possibilities.&amp;nbsp; Looks like M$ may have a winner.&lt;/P&gt;
&lt;P&gt;Of course the usual M$ questions remain:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Not browser based, back to the proprietary client&lt;/LI&gt;
&lt;LI&gt;XML forms but not &lt;A href="http://www.w3.org/TR/xforms/"&gt;XForms&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;How easy will it be to work with non-M$ platforms&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I guess that the last question is, ultimately, key.&amp;nbsp; If InfoPath is just another &lt;A href="http://www.w3.org/TR/ws-arch/"&gt;Web Services Architecture&lt;/A&gt; client (and something that propels that future) then it's a good thing.&amp;nbsp; Otherwise...&lt;/P&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00000812.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
        <ent:topic ent:id="java" ent:classification="user" ent:href="http://matt.blogs.it/topics/java.xml"/>
      </ent:cloud>
    </item>
    <item>
      <title>How to win a customer</title>
      <pubDate>Fri, 28 Oct 2005 16:23:51 +0100</pubDate>
      <description>&lt;p&gt;Well now this is very interesting.  This morning I emailed the authors of &lt;a href="http://www.ambrosiasw.com/utilities/snapzprox/"&gt;SnapZ Pro X&lt;/a&gt; (which most of the Mac cognoscenti are using to make nice screencam-movies) to tell them why I wasn't planning to register (it's to do with how the program runs, rather than the capture functionality itself).  I confess I did so with little hope of a response and little hope that any response would be polite or helpful.&lt;/p&gt;
&lt;p&gt;I remember one occasion where I emailed a company with an online MP3 catalogue to say that it would be much easier to browse if they actually had categories and an A-Z rather than just putting a random bunch on each page with a next button.  They asked me what the hell I was talking about.  I tried to explain why browsing was a good thing and got a response along the lines of "You are an idiot.  We are glad you are not a customer!"   What a great way to build your business!&lt;/p&gt;
&lt;p&gt;So I was a bit surprised this afternoon to get a personal response from David at Ambrosia software which began:&lt;blockquote&gt;Thank you for the feedback.  We often get ideas for ways to best improve our products from customers who've decided not to purchase it.&lt;/blockquote&gt;What a great start.  He then went on to describe some of the historical reasons for the way the app works, hinted it might be rethought in an upcoming version, and offered me a reasonable workaround.&lt;/p&gt;
&lt;p&gt;Polite, informed, listening, helpful.  I think I may register as much as anything to support a company who seems to understand what customer relationship (especially with non-customers) management actually means.&lt;/p&gt;
&lt;p&gt;Two thumbs up to &lt;a href="http://www.ambrosiasw.com"&gt;Ambrosia Software, Inc!&lt;/a&gt;&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002054.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
    <item>
      <title>Great flow</title>
      <pubDate>Sun, 05 Mar 2006 11:54:24 +0000</pubDate>
      <description>&lt;p&gt;Despite being very money conscious right now I shelled out $20 on Friday for &lt;a href="http://www.essl.at/works/flow/download.html"&gt;Flow&lt;/a&gt;. I can't remember where I got the link from but I'm damned grateful because it's great.&lt;/p&gt;

&lt;p&gt;According to author Karlheinz Essl, Flow:&lt;/p&gt;

&lt;blockquote&gt;
    &lt;p&gt;Generates an ever-changing and never repeating soundscape in real time that fills the space with flooding sounds that resemble - metaphorically - the timbres of water, fire, earth, and air.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I now tend to leave it running while I work and I find it really helps me to get into flow state and ignore distractions. I also find it quite restful in the evening before bed.&lt;/p&gt;

&lt;p&gt;Definitely recommended.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002154.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
  </channel>
</rss>
