distributed-conversation-examples: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
= Distributed Conversation Examples =
= Distributed Conversation --[[User:EranGloben|EranGloben]] 14:01, 22 Jan 2006 (PST)Examples =


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.
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.
Line 7: Line 7:
== Authors ==
== Authors ==


* EranGloben
* --[[User:EranGloben|EranGloben]] 14:01, 22 Jan 2006 (PST)


== Examples ==
== Examples ==

Revision as of 22:01, 22 January 2006

Distributed Conversation --EranGloben 14:01, 22 Jan 2006 (PST)Examples

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.

Authors

Examples

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:

  • In-Reply-To - Reference to message which this message is a reply to.
  • References - In e-mail: reference to other related messages, in Usenet News reference to replied-to-articles.
  • See-Also - References to other related articles in Usenet News.
  • Obsoletes - Reference to previous message being corrected and replaced.
  • Supersedes - Commonly used in Usenet News in similar ways to the "Obsoletes" header described above. In Usenet News, however, Supersedes causes a full deletion of the replaced article in the server, while "Supersedes" and "Obsoletes" in e-mail is implemented in the client and often does not remove the old version of the text.
  • Article-Updates - Only in Usenet News, similar to "Supersedes:" but does not cause the referenced article to be physically deleted.
  • Article-Names - Reference to specially important articles for a particular Usenet Newsgroup.

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