distributed-conversation-formats-fr

Formats de Conversation Distribuée

Exemples de Formats Apparentés

Email/Usenet

Email et Usenet gardent tous les deux trace des fils de discussion d'une manière non-centrale en utilisant les en-têtes et références vers les IDs de messages. Quelques en-têtes communs et leurs usages sont soulignés dans RFC2076 - Common Internet Message Headers section 3.6 :

• In-Reply-To - Référence vers un message dont ce message est un "reply to".
• References - Dans l'e-mail : référence vers d'autres messages apparentés, en référence aux News Usenet vers les 'replied-to-articles'.
• See-Also - Références vers d'autres articles en rapport dans Usenet News.
• Obsoletes - Référence au message précédent étant corrigé et remplacé.
• Supersedes - Communément utilisé dans Usenet News avec des manières similaires aux header "Obsoletes" décrit au-dessus. Dans Usenet News, néanmoins, Supersedes provoque un effacement total de l'article remplacé dans le serveur, alors que "Supersedes" et "Obsoletes" dans l'email est implémenté dans le client et n'enlève pas souvent la vieille version du texte.
• Article-Updates - Seulement dans Usenet News, similaire à "Supersedes:" mais ne provoque pas le fait que l'article référencé soit effacé physiquement.
• Article-Names - Référence vers articles tout particulièrement importants pour un Newsgroups spécifique Usenet.

Langage de Description de Fil

Thread Description Language - TDL est un vocabulaire RDF pour décrire les discussions en mode fil, tels que Usenet, weblogs, les bulletin boards et conversations par e-mail.

• http://www.eyrie.org/~zednenem/2002/web-threads/
• http://www.eyrie.org/~zednenem/2002/wtprofile/

TDL v3 définit les propriétés suivantes :

• Property tdl:discusses - Relates a Post to a resource it talks about
• Property tdl:follows - Indicates that this resource comes no earlier than the specified resource
• Property tdl:inThread - Relates a post to a thread which includes it
• Property tdl:mentions - Indicates that this resource refers to the specified resource
• Property tdl:respondsTo - Relates a post to its parent(s) in a discussion
• Property tdl:respondsNegativelyTo - Relates a post to a parent post which it dissents from or corrects
• Property tdl:respondsPositivelyTo - Relates a post to a parent post with which it concurs

Discussion sur 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) fournit un cadre pour une compréhension collaborative des principales problématiques et implications entourant ce qui est décrit comme des ``wicked problems (des problèmes qui manquent d'une formulation définitive). La compréhension est atteinte en utilisant les composants hypertexteproblems that lack a definitive formulation). Understanding is achieved by using hypertext components to create structured arguments surrounding the issues. (Weblog Kitchen)

• IBIS vocabulary
• How to start an IBIS discussion in Email
• graphical IBIS (gIBIS)

 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 à propos d'IBIS

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

• The different node types are not necessary for tracking a discussion thread. Tracking the flow of the conversation, the arguments and flow of ideas is a wider more complex issue than just gluing together disparate pieces of an online discussion.
• Link type such as "generalises" and "specialises" might be useful but seem to require a lot from the user. If we allow for inheritance of link type they could be used as optional parts of the format but it appears that we can do well enough without them.

SIOC - Semantically-Interlinked Online Communities

SIOC (Semantically Interlinked Online Communities) is an ontology for describing discussion forums and posts on topic threads in online community sites. This includes but is not limited to: blogs, bulletin boards, mailing lists, newsgroups, etc.

• http://rdfs.org/sioc/
• http://rdfs.org/sioc/spec/

Relevant properties defined under SIOC:

• has_reply - This details replies or responses to this Post, which can be used for purposes of display ordering.
• reply_of - Links to a previous Post, which this Post is a reply of (or to).
• next_version - Links to the next revision of this Post.
• previous_version - Links to a previous revision of this Post.
• has_sibling - A Post may have a sibling or a twin that exists in a different Forum, but the siblings may differ in some small way (for example, language, category, etc.). The sibling of this Post only needs to have the changed information.
• sibling_of - This Post differs from its sibling in some small way. The other sibling can be used as a source for any missing data.
• attachment - A URI of the attachment related to a Post.
• related_to - Related Posts for this Post, perhaps determined implicitly from topics or references.
• is_closed - Details if this (and any children) is closed.

Discussion of SIOC

• We cannot expect the complementary relations (e.g. has_reply) to exist. This would require a more strongly connected system that we do not assume exists. Similarly for is_closed.
• next_version and previous_version might be an interesting alternative to updates in the case where the author of the updated version has control of the previous version as well. This is not always the case but might happen often enough to include this option.
• The concept of siblings is an interesting one, although the difference between that and update or forward might be too particular for most users.
• attachment might be interesting but is it necessary?
• related_to might be useful in an aggregate environment (think delicious related tags) but otherwise I see those posts use as source citations, so this specific relation type might be pointless.

Exemples d'Utilisation

From Email we get two basic relations between message:

• Reply - This message is a reply to the referenced message.
• Forward - This message forwards the referenced message to additional recipients.

From various publications (often of standards) we get:

• Updates/Obsoletes - This documents contains updates or even replaces the referenced document.

Citation of resources comes in several flavors:

• Quote
• Citing a reference
• Via link/Hat tip (mainly in blogs)