Define two elements inside the <head> element.
<icon> for linking to a favicon for the feed
<image> for linking to an image for the feed
Related and Conflicting Proposals
Feature parity with RSS 2.0
Provide images for displaying with the feed in user-agent UI.
Both <image> and <icon> are valid for feeds, but not for <entry>, and thus the generic <link> construct isn't perfectly appropriate. Also, the <link> element is/was intended for linking to resources which are not intended for direct independent/standalone access.
Add to Section 4 two new sections.
=== 4.x atom:icon Element === The "atom:icon" element's content is a URI which identifies an image which provides iconic visual identification for a feed. The image SHOULD have an aspect ratio of one (horizontal) to one (vertical), and should be suitable for presentation in small size. === 4.y atom:image Element === The "atom:image" element's content is a URI which identifies an image which provides visual identification for a feed. The image SHOULD have an aspect ratio of 2 (horizontal) to 1 (vertical).
Insert into section 4.2 The "atom:head" Element
* atom:head elements MAY contain exactly one atom:icon element. * atom:head elements MAY contain exactly one atom:image element.
The RSS 2.0 <image> element has constraints on maximum height and width. For interoperability purposes should we suggest the same limits (as a SHOULD)?