Ah, but I'm thinking in terms of multiple feeds on a single page, each
feed being identified by a URI. Or do you think this is a bad idea also?
I notice that Tantek has placed a generic opaque container as a
potential idea onto the blog. If multiple feeds per page is OK with all
and a generic opaque container is available, then we get it "for free".
However, your wider point is appreciated, in both senses.
Regards, etc...
David
Mark Pilgrim wrote:
On 12/28/05, David Janes -- BlogMatrix <[EMAIL PROTECTED]> wrote:
Although not covered explicitly in the examples, my latest thought is to
allow a Feed element to be embedded in an Entry element. Why? To model a
comment feed, which obviously is blog like content.
I plan to implement it in feedparser.py when it's done, so I am
intensely interested in a few crucial design decisions. You've been
doing pretty well with hAtom so far, so I've stayed
uncharacteristically quiet. But now you're just making shit up, and
that's dangerous.
hAtom is a derivative format, like hCard is derivative of vCard. The
Atom format has been endlessly argued and finally codified and RFC'd.
Now you're trying to find an elegant way to backport it to HTML, which
I fully support. But please resist the temptation to invent new
things.
The Atom community already had this particular argument; nested feeds lost.
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
