[uf-discuss] Re: User comment entries

Sarven Capadisli csarven at gmail.com
Sat Oct 4 15:12:57 PDT 2008


Apologies for some of the obvious typos in my previous email. If it
may have caused any confusion, please see the Wiki:
http://microformats.org/wiki/hatom-brainstorming#User_comment_entries

Thanks,
-Sarven


On Sat, Oct 4, 2008 at 12:29 AM, Sarven Capadisli <csarven at gmail.com> wrote:
> Hi all, here is what I'm thinking about user comments:
>
> A user comment (e.g., in blogs, wikis, forms) can be marked as an
> hAtom [1] 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-replies-to" [2] from Atom
> Threading Extensions [3]. It provides a mechanism to indicate that an
> entry is a response to another resource.
>
> rel="in-repl-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-repl-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 [4], [5], [6].
>
> I've put the above into hatom-brainstorming in the Wiki [7].
>
> What do you think?
>
> [1] http://microformats.org/wiki/hatom
> [2] http://tools.ietf.org/html/rfc4685#section-3
> [3] http://tools.ietf.org/html/rfc4685
> [4] http://microformats.org/wiki/mfcomment
> [5] http://microformats.org/wiki/hcomment
> [6] http://microformats.org/wiki/comment-brainstorming
> [7] http://microformats.org/wiki/hatom-brainstorming#User_comment_entries
>
> Sarven Capadisli
> http://www.csarven.ca
>


More information about the microformats-discuss mailing list