comment-brainstorming

(Difference between revisions)

Jump to: navigation, search
(Orginally entered in hatom-brainstorming)
Line 51: Line 51:
* If an hfeed is embedded in an hEntry, that could be enough context to show "these items are replies to the one they're embedded in" [[User:Singpolyma|singpolyma]] 12:20, 25 Sep 2008 (PDT)
* If an hfeed is embedded in an hEntry, that could be enough context to show "these items are replies to the one they're embedded in" [[User:Singpolyma|singpolyma]] 12:20, 25 Sep 2008 (PDT)
 +
 +
 +
== hAtom Route ==
 +
 +
A user comment (e.g., in blogs, wikis, forms) can be marked as an [http://microformats.org/wiki/hatom hAtom] since it has a similar content pattern. A way to differentiate an hEntry (e.g., a blog post) from another hEntry (e.g., a user comment) can be done reusing [http://tools.ietf.org/html/rfc4685#section-3 in-reply-to] from [http://tools.ietf.org/html/rfc4685 Atom Threading Extensions]. It provides a mechanism to indicate that an entry is a response to another resource. rel="in-reply-to" can indicate that the current hEntry is a reply to another hEntry and has a reference point @href:
 +
<pre><nowiki>
 +
<a rel="in-reply-to" href="#comment_20080902144745">Parent</a>
 +
</nowiki></pre>
 +
 +
hEntries that use rel="in-reply-to" can be considered as a comment entry in response to a parent entry in the threaded conversation (e.g., in blogs, wikis, forms).
 +
 +
hEntries that are chronologically listed can all use rel="in-reply-to" and refer to the root hEntry (e.g., blog post, form post)
 +
 +
By reusing in-reply-to, we can solve the microformats representation for user comments [http://microformats.org/wiki/mfcomment], [http://microformats.org/wiki/hcomment], [http://microformats.org/wiki/comment-brainstorming].
 +
 +
--[[User:Csarven|Sarven Capadisli]] 21:25, 3 Oct 2008 (PDT)

Revision as of 14:11, 11 November 2008

Brainstorming for a Comment Microformat

Contents


This is a brainstorm for commentmicroformat. Examples of a comment can be found here comment-examples

Contributors


Discovered Elements

Based on the analysis of 25 real world examples, the results can be found at the Comment Analysis section

The following properties occur most regularly across all examples (92% or more)

Other achievable elements


Feedback

If we can indicate that the hAtom entries are also comments, we could add an indicator beside hAtom.

<div class="hfeed hcomment">

hAtom pattern goes here.

</div>

Alternatively, we could add hcomment with hentry to indicate that the following hentry can be treated also as a comment.

<div class="hentry hcomment">

hEntry pattern goes here.

</div>

--Sarven Capadisli 11:59, 25 Sep 2008 (PDT)



hAtom Route

A user comment (e.g., in blogs, wikis, forms) can be marked as an hAtom since it has a similar content pattern. A way to differentiate an hEntry (e.g., a blog post) from another hEntry (e.g., a user comment) can be done reusing in-reply-to from Atom Threading Extensions. It provides a mechanism to indicate that an entry is a response to another resource. rel="in-reply-to" can indicate that the current hEntry is a reply to another hEntry and has a reference point @href:

<a rel="in-reply-to" href="#comment_20080902144745">Parent</a>

hEntries that use rel="in-reply-to" can be considered as a comment entry in response to a parent entry in the threaded conversation (e.g., in blogs, wikis, forms).

hEntries that are chronologically listed can all use rel="in-reply-to" and refer to the root hEntry (e.g., blog post, form post)

By reusing in-reply-to, we can solve the microformats representation for user comments [1], [2], [3].

--Sarven Capadisli 21:25, 3 Oct 2008 (PDT)

comment-brainstorming was last modified: Wednesday, December 31st, 1969

Views