<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2008:/1/tag:72.47.210.69,2004://1.4199-</id>
  <updated>2008-09-24T12:29:21Z</updated>
  <title>Comments for Combined project for topic mapping in blogging?</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>
  <entry>
    <id>tag:72.47.210.69,2004://1.4199</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=4199" title="Combined project for topic mapping in blogging?" />
    <published>2004-04-25T07:58:51Z</published>
    <updated>2007-12-16T23:15:32Z</updated>
    <title>Combined project for topic mapping in blogging?</title>
    <summary><![CDATA[I mentioned in my last post that one of my ongoing interests is topic mapping in weblogs. Topic Exchange and K-Collector are two initiatives that I've hyped a lot over the last year. However the blogosphere still&nbsp;doesn't have&nbsp;a mainstream topic-mapping application - and I mean mainstream as in Technorati or Bloglines, apps that are used...]]></summary>
    <author>
      <name>Richard MacManus</name>
      <uri>http://www.readwriteweb.com</uri>
    </author>
    
    <category term="Info Architecture" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p>I mentioned in <a href="http://www.readwriteweb.com/2004/04/25.html#a226">my last post</a> that one of my ongoing interests is topic mapping in weblogs. <a href="http://topicexchange.com/">Topic Exchange</a> and <a href="http://k-collector.evectors.it/">K-Collector</a> are two initiatives that I've hyped a lot over the last year. However the blogosphere still&nbsp;doesn't have&nbsp;a mainstream topic-mapping application - and I mean mainstream as in <a href="http://www.technorati.com/">Technorati</a> or <a href="http://www.bloglines.com/">Bloglines</a>, apps that are used by a large percentage of bloggers.</p> <p>Seb Paquet <a href="http://radio.weblogs.com/0110772/2004/04/21.html#a1548">recently re-opened&nbsp;the conversation</a>&nbsp;on&nbsp;topic-mapping in blogs, and Rogers Cadenhead and Dave Winer <a href="http://www.cadenhead.org/workbench/2004/03/30.html#a1721">have been talking about it</a>, so it's on peoples minds. I'd like to suggest the following...</p> <p><strong>We need to meld the best features of Topic Exchange and K-Collector.</strong></p> <p>Topic Exchange and K-Collector each has its strengths. K-Collector has a great add-on for <a href="http://radio.userland.com/">Radio Userland</a>, which allows you to easily select relevant topics and add them to the community server. Topic Exchange requires you to send a trackback ping to its server for each topic, which makes it more open and extensible but also more effort for the blogger. Topic Exchange&nbsp;has a strong&nbsp;user community - it's like an open source project. K-Collector seems to be aiming at a corporate market and so that's where their development focus is I think. Nothing wrong with that per se, but it does mean I'm more emotionally attached to Topic Exchange these days.</p> <p>So the two development efforts can learn from each other. For example, it'd be great if Topic Exchange can automate its ping process a bit more (I'll try and think more about this, so I can offer some potential solutions), and K-Collector can keep the blogosphere in the loop regarding its continued development (e.g. more updates, especially to the mailing list).</p> <p>I wonder if it's worthwhile merging Topic Exchange and K-Collector? There is so much talent in each project, but&nbsp;perhaps topic mapping has its best chance of gaining mainstream acceptance if we work under one umbrella "project". What do you reckon, am I getting all hippie about this or is&nbsp;a&nbsp;combined project&nbsp;a viable solution?</p> <p><i>Cross-posted to <a href="http://topicexchange.com/t/topic_exchange/">Topic Exchange</a> and <a href="http://k-collector.evectors.it/">K-Collector</a></i></p>]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2004://1.4199-comment:35385</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2004://1.4199" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php#c35385" />
    <title>Comment from Greg on 2004-04-25</title>
    <author>
        <name>Greg</name>
        <uri>http://www.blogdigger.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.blogdigger.com/">
        <![CDATA[<p>I posted a whiles back about shared topics - this is a more important development for smaller communities, as opposed to the web as a whole, I think.  But it would be nice if, in MovableType for example, I'm given the choice of associating topics from the TopicExchange's directory along with, or as opposed to, the topics in my own blog.  I'm sure it wouldn't be too hard to add support into the blogging apps to create a TopicExchange trackback ping, send it off to the TopicExchange, which could automaticallty create new topics as needed.</p>

<p>Also somewhat relavant - Blogdigger supports searching by topic: try <a href="http://blogdigger.com/search.jsp?q=subject%3Atopics&sortby;=date" rel="nofollow"><a href="http://blogdigger.com/search.jsp?q=subject%3Atopics&sortby;=date" rel="nofollow">http://blogdigger.com/search.jsp?q=subject%3Atopics&sortby;=date</a></a> for all blog posts that are contain "topic" in their subject or category fields.</p>]]>
    </content>
    <published>2004-04-26T01:25:11Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2004://1.4199-comment:35386</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2004://1.4199" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php#c35386" />
    <title>Comment from Danny on 2004-04-26</title>
    <author>
        <name>Danny</name>
        <uri>http://dannyayers.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://dannyayers.com">
        <![CDATA[<p>I like your aims, and agree 100% that such a combination would be really good. However I believe it's worth taking a step back, and rather trying to merge Topic Exchange and K-Collector, make both of them work with a common framework. That way, if there's an additional kind of application, you only have to look at the framework, not the other two apps (same idea as programming to interfaces).</p>

<p>OPML is underspecified, and doesn't tell you in a standard fashion how different links are related. It appears to work well for single-purpose applications, but is hopeless for interop across different systems, because there's no standardization on how things should be represented. e.g. the aggregators all use different interpretations of the spec for their feedlists.</p>

<p>The RDF framework *is* eminently suitable. There's more of a learning curve for developers, but there's also a much greater payoff. If TE and KC had such interfaces, then immediately they could not only interoperate with each other, but any existing RDF data, e.g. FOAF or RSS.</p>]]>
    </content>
    <published>2004-04-26T08:51:37Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2004://1.4199-comment:35387</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2004://1.4199" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/combined_projec.php#c35387" />
    <title>Comment from Richard MacManus on 2004-04-26</title>
    <author>
        <name>Richard MacManus</name>
        <uri>http://www.readwriteweb.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com">
        <![CDATA[<p>Thanks Greg and Danny for your thoughtful comments. Much to mull over there... If anyone else has some ideas, feel free to deposit them here and I'll perhaps write it all up into a summary post.</p>]]>
    </content>
    <published>2004-04-26T09:24:12Z</published>
  </entry>

</feed>