I have read that this should work for comment threads, but no luck (at least not in my reader):
<link rel="replies" type="application/atom+xml" href="" />
atom enabled-ing
December 19, 2005 1:38am (6 years, 1 month and 2 weeks ago)
Does anyone know of an Atom equivalent to <wfw:commentRss> and/or <slash:comments>?
I have read that this should work for comment threads, but no luck (at least not in my reader):
I have read that this should work for comment threads, but no luck (at least not in my reader):
Comments
Dec 19, 2005 3:55pm
Good plan! I had forgotten it was open source. I looked at about a bazillion Atom feeds and none of them have support for comments.
Rss Bandit has specific support for the slash namespace in Atom feeds (MakeAtomItem method in RssComponents/RssHandler.cs).
I don’t see any way to refer to a comment feed besides commentRss, but optional components are handled the same in both types of feed, so the wfw namespace should work in Atom also.
Hopefully other aggregators agree.
Rss Bandit has specific support for the slash namespace in Atom feeds (MakeAtomItem method in RssComponents/RssHandler.cs).
I don’t see any way to refer to a comment feed besides commentRss, but optional components are handled the same in both types of feed, so the wfw namespace should work in Atom also.
Hopefully other aggregators agree.
Dec 19, 2005 4:04pm
Looking at your link, I may put in a <link rel=”comments” …> as well as <wfw:commentRss>. I imagine most aggregators would support one or the other.
Jun 1, 2006 1:13pm
So, I followed the “my reader” link you have and went to rssbandit. Anyhoo, they have this nifty little W3C XHTML valid image at the bottom of their page. 22 errors I counted in their “valid” XHTML.
I don’t really see how you can place a valid XHTML graphic on your site if the site is clearly not valid XHTML.
Mind boggling.
I don’t really see how you can place a valid XHTML graphic on your site if the site is clearly not valid XHTML.
Mind boggling.
Jun 1, 2006 4:05pm
That’s the problem with open systems like Wikis not validating (or automatically fixing) input. MediaWiki (which runs Wikipedia) seems to do a better job at ensuring valid code.
At least the NewsGator site appears to be valid XML. Technically, XHTML that isn’t XML is complete garbage, but you’d be surprised (well maybe not) how many sites get it wrong.
At least the NewsGator site appears to be valid XML. Technically, XHTML that isn’t XML is complete garbage, but you’d be surprised (well maybe not) how many sites get it wrong.
Jun 1, 2006 6:00pm
XHTML is hard…
It’s like you think everything’s cool, then it fails to validate. And you’re like, “Good sir, why must a hidden input element be nested inside a div or paragraph?” And XHTML is all “AHAHA YOUR LAME”
It’s like you think everything’s cool, then it fails to validate. And you’re like, “Good sir, why must a hidden input element be nested inside a div or paragraph?” And XHTML is all “AHAHA YOUR LAME”
Leave a comment
Accepts BBCode with a few enhancements.
I suppose if I dug around the RSS Bandit source code I could figure out an answer for you. I believe that it transforms (possibly through XSLT, but I’m not sure) all feeds of different types into its own internal format.
If you have a SourceForge account, maybe you could open a bug and see if you get a response. That’s how I found out I needed both the elements you mentioned for RSS to support comments feeds (which is odd since they’re part of two entirely different extensions to RSS and should not be both required).