[uf-discuss] does hatom for comments make sense?
Stephen Paul Weber
singpolyma at gmail.com
Tue Sep 12 10:39:37 PDT 2006
I think that if using hAtom for comments is going to become 'standard'
that we definately need to use class="comments" (or something similar)
to identify the nested comments feeds inside the main hfeed. Also,
comments don't really have a 'title'... you could use the original
post title (rarely done, and could confuse the user), or an
auto-generated thing based on content (ie 'comment by jake on post'...
usually how comment feed titles work, but then you have data
On 9/12/06, David Janes <davidjanes at blogmatrix.com> wrote:
> Right -- and a uF for expressing that relationship; this gets a little
> trickier. As uFs are about codifying existing practices, my
> (superficial) look at comment nesting shows that many sites (like
> slashdot) using nesting to express relationships, not explicit URI
> linking. On the other hand, threaded mail list managers do use links
> to express the hierarchy.
> The nice part is that this (hypothetical uF) composites with hAtom to
> achieve our result; the trickier part is documenting nesting examples
> to support the uF.
> Regards, etc...
> On 9/12/06, Karl Dubost <karl at w3.org> wrote:
> > Just think that a comment is "a weblog post about a weblog post"
> > uri1 <--- comment-x/uri2 about uri1
> > <--- comment-xa/uri5 about uri2
> > <--- comment-xb/uri6 about uri2
> > <--- comment-y/uri3 about uri1
> > <--- comment-z/uri4 about uri1
> > It is just a question of having the right *atomic* model.
> > and to make individual statements about things.
> > Then the application layer is above.
> microformats-discuss mailing list
> microformats-discuss at microformats.org
- Stephen Paul Weber, Amateur Writer
MSN/GTalk/Jabber: singpolyma at gmail.com
NSA: stephen4 at northstar-academy.org
More information about the microformats-discuss