-
Website
http://www.scripting.com/ -
Original page
http://www.scripting.com/stories/2007/11/05/rss20CommentsElement.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
eas
55 comments · 4 points
-
AndrewBurton
134 comments · 10 points
-
Michael Markman (Mickeleh)
154 comments · 16 points
-
Rex Hammock
52 comments · 9 points
-
malatmals
81 comments · 3 points
-
-
Popular Threads
-
How I develop formats and protocols. (Scripting News)
1 day ago · 11 comments
-
Open is in the eye of the beholder. (Scripting News)
3 days ago · 13 comments
-
Store Twitter URLs in earth's oceans? (Scripting News)
5 days ago · 16 comments
-
Why today's Twitter is like Napster in Y2K. (Scripting News)
5 days ago · 15 comments
-
If you wrote the words you own the copyright. (Scripting News)
5 days ago · 7 comments
-
How I develop formats and protocols. (Scripting News)
I am working on an application (statzen.com) that publishes feeds for many different blogs and am planning to provide support for the <comments> element.
On a somewhat related note, it seems that in order for the author element to be valid, it must expose an email address to spammers. What if that author element had an alternate syntax that allowed a URL to a contact form i.e.:
<author>http://example.com/contact (author name)</author>
For me the issue that is holding back things is that currently we have POST feed & COMMENT feed, why not both together? We have put in massive amounts of work to match up post & comment from sources that dont really give us all the information we need.
The future of feed reading will be integrating the commenting process and although we are the first to do it t fav.or.it, I dont believe it be long before google/bloglines/newsgator do the same thing. In fact as thats not part of our business model I really really welcome it, as the standards need sorting out.
Picture here: http://radio.weblogs.com/0106327/2007/11/06.html
Picture here: http://radio.weblogs.com/0106327/2007/11/06.html