MediaRSS in ingested Atom feeds is discarded/not output in Buzz

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create two feeds that make use of the MediaRSS extension, one Atom, one 
RSS.

Atom feed declaration:
<feed xmlns="http://www.w3.org/2005/Atom" 
xmlns:media="http://search.yahoo.com/mrss/">

RSS feed declaration:
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" 
xmlns:atom="http://www.w3.org/2005/Atom">

Add elements making use of MediaRSS extension.  In the RSS feed, they can 
be added as a child of <item>, in the Atom feed as a child of <entry>:

            <media:content 
url="http://www.huffingtonpost.com/2010/03/25/david-frum-aei-split-
cons_n_513544.html" type="text/html" medium="document"><media:title>David 
Frum, AEI SPLIT: Conservative&#039;s Position &#039;Terminated&#039; By 
Major Think Tank</media:title><media:description>See late updates below...
Former George W. Bush speechwriter David Frum has resigned from the right-
wing American Enterprise...</media:description></media:content>
                            <media:content 
url="http://images.huffingtonpost.com/gen/152124/thumbs/r-FRUM-
medium260.jpg" type="image/jpeg" width="260" height="190" medium="image">
                   <media:thumbnail 
url="http://images.huffingtonpost.com/gen/152124/thumbs/s-FRUM-mini.jpg"  
width="97" height="75" />
</media:content>

2. Validate - make sure both feeds pass as valid XML, RSS, and Atom and 
warnings aren't thrown at http://validator.w3.org/feed/

3. Add an entry with recent date/timestamp to the top of both feeds if 
there isn't one already

4. Using XFN, link the two feeds to Buzz.  Add two pages, each one with XFN 
link to Google profile, but one with the RSS version, one with Atom.  Add 
each to Google profile at http://www.google.com/profiles , then use 
https://sgapi-recrawl.appspot.com/ to verify XFN claim.

5. In Buzz, add both of the feeds to Connected Sites

What is the expected output? What do you see instead?

Expected output: same or similar in-Buzz view of the items.
Actual output: Item ingested via RSS feed with MediaRSS extensions works 
fine, the image passed in via MediaRSS is displayed.  Item ingested via 
Atom feed with MediaRSS extensions does not show any of the attached media.

Even though it is called "Media RSS", this practice of using it in 
conjunction with Atom is not so uncommon: 
http://code.blogger.com/2008/09/feeds-now-include-media-rss-thumbnails.html 
. The docs specify support for Media RSS but not any Atom equivalent, 
making it seem as if Media RSS is the universal solution for media 
embedding.

Original issue reported on code.google.com by bregens...@gmail.com on 26 Mar 2010 at 8:37

Attachments:

• mediaRSStest.zip
• buzz_display.gif

[GoogleCodeExporter]

The attached buzz_display.gif shows the output of the above reproduction steps 
in 
Buzz, mediaRSStest.zip contains the 4 HTML and XML files used for the test.

Original comment by bregens...@gmail.com on 26 Mar 2010 at 8:38

[GoogleCodeExporter]

This issue may not actually be related to Google Buzz.

I would be interesting to know *how* both the RSS and Atom feed get into Buzz. 
If 
you guys used PubSubHubbub to get this content, and assuming that you did so 
with 
the Superfeedr hub, then, we'll push you Atom, without the MediaRSS content. 
The 
problem is that this is true for the Atom *and* the RSS feeds. 

In this case, the expected result would be: same or similar in-Buzz view of the 
items, 
without the mediaRSS content.

Original comment by julien.g...@gmail.com on 26 Mar 2010 at 10:02

[GoogleCodeExporter]

In this case, there is actually no Pubsubhubbub involved, the above replication 
steps
work (in that they show the problem in question) without any hub being added.

When I do involve Superfeedr in it, and send in RSS 2.0 with Media RSS, 
Superfeedr's
(by design) normalization to Atom seems to result in the same problem as above. 
  As
far as I can see, there is a problem with Atom input into Google Buzz not being
parsed for Media RSS enclosures (or maybe it is something by design/due to 
current
beta status, just undocumented), and this problem happens both when the Atom 
input
comes via Pubsubhubbub or via regular fetching.

Original comment by bregens...@gmail.com on 26 Mar 2010 at 10:19

[GoogleCodeExporter]

Does this still happen if you use the new-style feeds?

Original comment by a...@google.com on 18 Aug 2010 at 8:55