(Difference between revisions)

Jump to: navigation, search
(Add examples from my blog)
m (Authors)
Line 9: Line 9:
* [[User:EranGloben|Eran Globen]]
* [[User:EranGloben|Eran Globen]]
* [[User:BenjaminCarlyle|Benjamin Carlyle]]
* [[User:BenjaminCarlyle|Benjamin Carlyle]]
* ...
== Examples of Related Solutions==
== Examples of Related Solutions==

Revision as of 23:42, 25 January 2006


Distributed Conversation

This is an exploratory page to document various methods used to anotate online conversations both distributed and not. The purpose of the studies on this page is to serve as background for the design of a microformat to anotate distributed conversations on blogs and other online media.

see citation-brainstorming for more discussion on this topic.


Examples of Related Solutions


Email and Usenet both keep track of discussion threads in a non-central manner using headers and references to message IDs. Some common headers and their use are highlighted in RFC2076 - Common Internet Message Headers section 3.6:

Thread Description Language

Thread Description Language - TDL is an RDF vocabulary for describing threaded discussions, such as Usenet, weblogs, bulletin boards, and e-mail conversations.

TDL v3 defines the following properties:

Discussion of TDL

  1. respondsNegativelyTo, respondsPositivelyTo are beyond the scope of this spec. They can both be implemented using vote-links.
  2. Without those, respondsTo remains the main connector between posts in a thread.
  3. mentions and discusses seem to be splitting hairs. It appears that both of them can be replaced by using the CITE tag.
  4. follows seems to be designed for use in a central registry that tracks threads and therefore is useless for a distributed solution.

IBIS - Issues Based Information Systems

Kunz's Issue Based Information Systems (IBIS) provide a framework for collaborative understanding of the major issues and implications surrounding what are described as ``wicked problems (problems that lack a definitive formulation). Understanding is achieved by using hypertext components to create structured arguments surrounding the issues. (Weblog Kitchen)

 The hypertext model of IBIS consists of three node types:
  1. issues
  2. positions
  3. arguments
 Eight link types represent the allowable relationships between these nodes:
  1. generalises
  2. specialises
  3. replaces
  4. questions
  5. is_suggested_by
  6. responds_to
  7. objects_to
  8. supports

Discussion of IBIS

Similar to TDL, IBIS seems to tackle a bigger problem than the one discussed here.

Examples of Use

From Email we get two basic relations between message:

From various publications (often of standards) we get:

Citation of resources comes in several flavors:

Web Examples

Author, href and blockquote

<p>His column was picked up all over the web, including by Danny Ayers. He dives into discussion about <a href="http://dannyayers.com/archives/2006/01/10/new-data-languages-harmful/">how to build an RDF model</a>, rather than an XML language: </p>

<blockquote> <p>When working with RDF, my current feeling (could be wrong ;-) is that in most cases it’s probably best to initially make up afresh a new representation that matches the domain model as closely as possible(/appropriate). Only then start looking to replacing the new terms with established ones with matching semantics. But don’t see reusing things as more important than getting an (appropriately) accurate model. (Different approaches are likely to be better for different cases, but as a loose guide I think this works.) </p> </blockquote>


Danny Ayers is the author of the pieces being referenced. The href identifies an article the blockquote comes from. "How to build an RDF model" may be considered a short description of the link, however sometimes this text is as short as "writes".

distributed-conversation-examples was last modified: Wednesday, December 31st, 1969