[uf-discuss] does hatom for comments make sense?

Eran limbo at actcom.co.il
Mon Sep 11 22:32:35 PDT 2006


1. you don't have to, it's bonus meta-info.
2. you can probably map cite-rel to Atom Threading Extensions -
http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-thread-12.txt
and get as good a coverage as you would from atom.

Eran.

> -----Original Message-----
> From: microformats-discuss-bounces at microformats.org [mailto:microformats-
> discuss-bounces at microformats.org] On Behalf Of Chris Messina
> Sent: Monday, September 11, 2006 10:14 PM
> To: Microformats Discuss
> Subject: Re: Re: [uf-discuss] does hatom for comments make sense?
> 
> How would you handle nested comments like in Digg for example?
> 
> Just curious how that fits into the model -- I suppose it would map to
> what you described?
> 
> Chris
> 
> On 9/11/06, Karl Dubost <karl at w3.org> wrote:
> > Hi Steph,
> >
> > Le 12 sept. 06 à 07:17, Stephanie Booth (bunny) a écrit :
> > > A while back somebody showed me a blog marked up with hatom. That
> > > person used hatom on the comments too (on the single post page) --
> > > that meant two hfeeds: one containing only the post, and another one
> > > with the comments.
> > >
> > > Does this way of using hatom on comments make sense to you? I noticed
> > > that neither K2 nor Sandbox wordpress themes do this.
> >
> > Completely logical.
> >
> > Each individual comment is nothing more than a weblog post.
> > The only technical difference is that it is not made on another
> > weblog, but directly on the weblog of the person.
> >
> > Each individual comment is structured like a weblog post.
> > It has  (required)
> >         - an id, the URI of the comment
> >         - a title, often the same than the original weblog post,
> sometimes a
> > different (see SPIP)
> >         - a date when it has been done (updated)
> > It has (recommended)
> >         - often an author
> >         - content (core text of the comment)
> >         - link (the URI of the Weblog original post we are commenting
> on)
> >
> > It just miss a summary, but that is not mandatory in Atom either.
> >
> > IMHO, it should be an individual hatom entry for each comment, The
> > way everything is aggregated and organized has a full feed is another
> > debate. The date and link should help to create a pseudo thread.
> > It could be a full thread like in SPIP when the commenter has the
> > possibility to reply to a specific comment in this case the link
> > becomes the URI of the specific comment.
> >
> >
> >
> > --
> > Karl Dubost - http://www.w3.org/People/karl/
> > W3C Conformance Manager, QA Activity Lead
> >    QA Weblog - http://www.w3.org/QA/
> >       *** Be Strict To Be Cool ***
> >
> >
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss at microformats.org
> > http://microformats.org/mailman/listinfo/microformats-discuss
> >
> 
> 
> --
> Chris Messina
> Citizen Provocateur &
>   Open Source Ambassador-at-Large
> Work: http://citizenagency.com
> Blog: http://factoryjoe.com/blog
> Cell: 412 225-1051
> Skype: factoryjoe
> This email is:   [ ] bloggable    [X] ask first   [ ] private
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss



More information about the microformats-discuss mailing list