Thanks Sean,
On the content type, I can agree and at the same moment I could start a discussion on how we than should provide simple links in feeds that can be understood by client applications and better be exploited than just obtain a single image.
On the choice for RSS2.0, well to be honest the reason is probably more laziness than anything else :) . There was an existing RSS2.0 feed providing the latest information added to the catalog. That feed output was then re-used to also provide RSS2.0 formatted output on searches since it was already in place. I now just extended and hopefully improved it. I was thinking to look into Atom later, but now am more stressed for time to get a GeoNetwork v2.2 release out. I caused the RC2 release to be delayed for a couple of weeks already :( . That said, I very much hope to find a good solution for the link problem when it comes to W*S services. I'll write a separate entry on that to try to explain the problem better (at least give better insight in my personal trouble to get a proper grip on the issue). And now I'll start reading the ORE Specification, maybe that has all the answers and I can forget about blogging on this problem :)
Ciao, Jeroen