Given all this, does anybody have an idea why this wasn't implemented
in things like Sandbox, and how to encourage the theme authors to do
it in the next version?
Steph
--
http://climbtothestars.org/
___
microformats-discuss mailing list
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,
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
would the feeds be nested? I think that in the example I saw, there
were two feeds. One with only the blog post, and a separate one with
the comments. Is it permitted by hAtom to nest feeds? I thought it
wasn't.
Steph
On 9/12/06, Stephen Paul Weber [EMAIL PROTECTED] wrote:
I think that if
Comments are (almost) always right after a post... so yes, the comment
feeds would have to be nested, unless the existed only on item pages.
Having all the data avaliable at once has proved very useful in my
previous applications of related technology (XOXO-based encoding as
seen on
Comments are nested within entries and hfeed elements can be nested
too. Typically, one doesn't see multiple entries with comments on the
same page.
In usage that I've seen, one would probably use this nesting structure:
* hfeed (for the blog, optional)
** hentry (for the one entry on the page)
On 9/12/06, David Janes [EMAIL PROTECTED] wrote:
Comments are nested within entries and hfeed elements can be nested
too. Typically, one doesn't see multiple entries with comments on the
same page.
it can be found in the wild, though. A very famous french-language
blog, for example:
I don't think it makes much sense... I use a 'standard' XOXO markup on
comments...
On 9/11/06, Stephanie Booth (bunny) [EMAIL PROTECTED] wrote:
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
Why wouldn't it make sense? Comments are structured much the same way
blog posts are. My personal rule of thumb is things that you'd make an
Atom feed for -- and comments certainly fall under this category --
should be worth considering for hAtom if there's a clear HTML
representation.
What
On 11 Sep 2006, at 23:17, Stephanie Booth (bunny) wrote:
Does this way of using hatom on comments make sense to you?
It does to me, yes. Although not using two separate hAtom feeds. I'd
just have one with the original post as the first entry in the feed
and comments following on
On 9/11/06, Ben Ward [EMAIL PROTECTED] wrote:
On 11 Sep 2006, at 23:17, Stephanie Booth (bunny) wrote:
Does this way of using hatom on comments make sense to you?
It does to me, yes. Although not using two separate hAtom feeds. I'd
just have one with the original post as the first entry in the
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
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 [EMAIL PROTECTED] wrote:
Hi Steph,
Le 12 sept. 06 à 07:17, Stephanie Booth (bunny) a écrit :
A while back
] [mailto:microformats-
[EMAIL PROTECTED] 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
14 matches
Mail list logo
