RE:
How to Make Blogging More SemWeb Friendly,
RSS Conversations,
Topics in Weblogs,
Threads of Conversation.

This particular fork got started here.

Blog-to-blog conversations are easily fragmented, with responses residing on blog discussion boards, the responder's site, and on various tracking services.

I have been thinking about how to implement a "reply on my blog" link which would enable a writer to reply using his own CMS.

Implemented with current web technology, this idea assumes that the API of the responder's blogging software can be known to the site which he is responding to. This reply would link to a script on the original site, which, after noting the action, would redirect the request to the content management system under the responder's control.

RDF for the original entry (and historical data about the conversation) would be passed to the responder's CMS in the url string. He would respond. As his CMS updates his blog, his response would be forwarded on to the cited blog (which would be expecting it), trackers, aggregators, and online communities.

Additional concepts:

• the responder would be provided with a standard blog posting page, perhaps with: a listing of links in the original post, metadata about the discussion, information about the participants, a way to view the conversation tree, etc.
  
• any metadata (such as dc:Subject and the tracking service of choice) assigned to the entry by the original blogger could carry over to the responder, who could add additional metadata. But how much metadata should accumulate?
  
• the effort to implement something like "reply on my site" would add to the culture of interoperability between sites (as TrackBack did)
  
• threading, summarization, and other forms of conversational analysis could be performed by any interested party, provided that the RDF can be obtained from each participating site
  
• organized conversation forking could be supported