Search the web
Sign In
New User? Sign Up
rss-public
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Show off your group to the world. Share a photo of your group with us.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Overriding Core elements via extensions   Message List  
Reply | Forward Message #310 of 1975 |
Re: [rss-public] Overriding Core elements via extensions

Sam Ruby wrote:
> Consider an RSS 2.0 item which contains only the following elements:
> description
> content:encoded
> xhtml:body
> atom:summary
> atom:content

I ran a couple of tests through my little aggregator collection and these
were the results:

Basically everyone supported content:encoded (except Thunderbird), almost
nobody supported atom extensions (except Sharpreader), and around half
supported xhtml:body to some extent (prefixed xhtml generally caused
problems). When they're mixed together in a single item, extensions are
usually chosen before the standard description element and when multiple
extensions are supported by an aggregator, the last one encountered usually
takes preference.

Aggregators tested: Blogbridge, Bloglines, BottomFeeder, FeedDemon,
FeedReader, Googler Reader, GreatNews, JetBrains Omea, Netvibes, Newsgator
Online, NewzCrawler, RSSBandit, RSSOwl, Sharpreader, Snarfer and
Thunderbird.

Bloglines, BottomFeeder, JetBrains Omea, Newsgator Online, NewzCrawler,
RSSBandit, Sharpreader and Snarfer all supported xhtml:body. Only Snarfer
interpreted markup when it was prefixed (i.e. xhtml wasn't the default
namespace), BottomFeeder never interpreted the markup regardless of whether
it was prefixed or not, and Bloglines failed to display any content at all
when the markup was prefixed.

When all the elements were included in the order you listed, Bloglines,
JetBrains Omea, Newsgator Online, NewzCrawler, RSSBandit and Snarfer
displayed xhtml:body, Sharpreader displayed atom:content, Thunderbird
displayed the description, and everyone else displayed content:encoded.

When the elements were included in reverse order, FeedDemon, NewzCrawler and
Thunderbird displayed the description element, Newsgator Online display
xhtml:body, and everyone else display content:encoded.

It's probably also worth nothing that everyone interpreted the markup
correctly when included in the description element although this wasn't
intended to be a markup test so the example used was as simple as possible.

Regards
James



Wed Feb 22, 2006 5:05 am

james_holder...
Offline Offline
Send Email Send Email

Forward
Message #310 of 1975 |
Expand Messages Author Sort by Date

I've seen a recent suggestion on this list that Atom elements may be used to replace core elements in RSS 2.0 that have perceived deficiencies. Others have...
Sam Ruby
sa3ruby
Online Now Send Email
Feb 21, 2006
6:23 pm

... Of course, as soon as I sent this, I remembered one more. The discussion that the draft-1 description of guid "could be interpreted as meaning that the...
Sam Ruby
sa3ruby
Online Now Send Email
Feb 21, 2006
6:33 pm

... I ran a couple of tests through my little aggregator collection and these were the results: Basically everyone supported content:encoded (except...
James Holderness
james_holder...
Offline Send Email
Feb 22, 2006
5:04 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help