locked
Atom author in RSS 2 RRS feed

  • General discussion

  • The forums are producing RSS 2 feeds with some Atom elements. While most of the additional elements are useful, the Atom author element in RSS 2 is not widely supported (Does any feed reader supports it? The Windows RSS Platform does not.), dc:creator should be used instead. However, the best solution I think, is to generate full Atom feeds by default, so that core elements can be in the same namespace and interoperability is ensured.
    Franklin Tse (whale)
    Monday, February 18, 2008 1:22 AM

All replies

  • Franklin,

    Thank you for taking the time to provide feedback. This element is supported by several major clients including NewsGator. I'll definitely look into the Windows RSS Platform issue. Are you having an issue with any other feed client?

    I am a personal fan of ATOM over RSS. My hope is that we will continue to review feed client support of ATOM and eventually make the switch. In the mean time, you can append "?format=atom10" to the end of the feed URI and get an ATOM 1.0 compliant feed.

    Please let me know if you have any more questions.

    Thanks!


    • Edited by tshak Tuesday, February 19, 2008 12:00 AM It looks like IE7 only supports this field for ATOM feeds, not RSS feeds. I'll continue to investigate.
    Monday, February 18, 2008 10:03 PM
  • Thank you very much for looking into the issues!

    Besides the Windows RSS Platform, Snarfer does not support atom:author in RSS 2 either. According to the RSS Best Practices Profile, dc:creator should be used instead: http://www.rssboard.org/rss-profile#namespace-elements-dublin-creator

    I am a fan of Atom too, I am glad that the forums provide an option to get Atom feeds. Please note that the Atom feeds generated by the Microsoft Forums do not currently validate: http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Fservices.community.microsoft.com%2Ffeeds%2Ffeed%2Fquery%2Ftype%2Fforum%2Feq%2Fdatatype%2Fmessage%2Feq%2Fand%2FthreadId%2F44431d20-d453-43e6-9f54-1ddb63c7be1f%2Feq%2Fand%3Fformat%3Datom10

    The errors are easy to fix - The first error can be fixed by adding "urn:uuid:" before the id string and the second error (or warning) can be fixed by adding the absolute URL of the feed to the Atom self link. (The Atom self link issue also affects RSS 2 feeds)

    By the way, do you have any plan on using the Atom Threading Extensions? http://tools.ietf.org/html/rfc4685

    Thanks and regards,
    Franklin Tse (whale)
    Tuesday, February 19, 2008 12:35 PM
  • One of the issues with RSS, and a large part of why I would like to support ATOM by default, is that there are competing RSS shcemas; there is no RSS standard. I know that the Harvard schema is one that we are looking closely at to provide maximum compatibility accross all popular clients. Dublin Core is another.

    We actually had a bug on the ATOM ID issue and it looks like it only got fixed at the feed level but not the feed item level. I'll file a new bug on this. The self link issue was postponed since it wasn't breaking any of the clients we tested with. This should be fixed in a future release as well.

    Since RSS is still our current focus we have not looked at features like ATOM Threading Extensions yet. My hope is that as the mindshare around ATOM increases that we will be able to look at added features like this.

    Thanks again for your feedback!

    Regards,


    Tim Shakarian, Software Developer
    Wednesday, February 20, 2008 12:44 AM
  • I've just found 2 more issues, but I am not sure if they are bugs.

    I think atom:content should be used instead of atom:summary since the whole post is included in each summary currently.

    Will the feeds support HTTP conditional GET? Conditional GET can save resources, and many feed readers support it. Using both Last-Modified (If-Modified-Since) and ETag (If-None-Match) is recommended.

    Thanks!
    Franklin Tse
    Wednesday, February 20, 2008 9:21 AM
  • I agree that we should review our decision around content vs. summary for Forums feeds. Additionally, for our next release we are looking at overall performance. HTTP conditional GET is a great idea for saving bytes transferred over the wire.

    Thanks!
    Tim Shakarian, Software Developer
    Wednesday, February 20, 2008 7:03 PM
  • Tim, I have just submitted two bug reports about the .NET System.ServiceModel.Syndication namespace, which appears to be affecting the forums feeds.

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=330046
    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=330049

    I hope the reports help you and the .NET Team to understand and resolve the issues as soon as possible.

    Best,

    Franklin Tse
    • Edited by whale Tuesday, February 26, 2008 10:52 AM Make the hyperlinks clickable
    Tuesday, February 26, 2008 10:50 AM
  • I've forwarded these issues to a PM on the WCF team. The RSS "ATOM elements" bug you filed is "by design". I think we need to do a better job communicating the design philosophy around the RSS serializer in WCF. Hopefully we'll be able to follow up on this soon.

    Thanks!
    Tim Shakarian, Software Developer
    • Edited by tshak Thursday, February 28, 2008 11:41 PM Clarified RSS/ATOM elements.
    Thursday, February 28, 2008 11:40 PM
  • The RSS Atom Elements Bug has been resolved as "Postponed". Since the next service pack or the next major release of the .NET Framework will not be released shortly, I suggest using Atom as the default feed format.
    Franklin Tse
    Tuesday, March 18, 2008 5:44 AM