A dictionary with details about the entry summary.

Comes from

  • /atom10:feed/atom10:entry/atom10:summary
  • /atom03:feed/atom03:entry/atom03:summary
  • /rss/channel/item/description
  • /rss/channel/item/dc:description
  • /rdf:RDF/rdf:item/rdf:description
  • /rdf:RDF/rdf:item/dc:description


Same as entries[i].summary.

If this contains HTML or XHTML, it is sanitized by default.

If this contains HTML or XHTML, certain (X)HTML elements within this value may contain relative URIs. If so, they are resolved according to a set of rules.

If this contains HTML or XHTML, it will be parsed for microformats.


The content type of the entry summary.

Most likely values for type:

  • text/plain
  • text/html
  • application/xhtml+xml

For Atom feeds, the content type is taken from the type attribute, which defaults to text/plain if not specified. For RSS feeds, the content type is auto-determined by inspecting the content, and defaults to text/html. Note that this may cause silent data loss if the value contains plain text with angle brackets. There is nothing I can do about this problem; it is a limitation of RSS.

Future enhancement: some versions of RSS clearly specify that certain values default to text/plain, and Universal Feed Parser should respect this, but it doesn’t yet.


The language of the entry summary.

language is supposed to be a language code, as specified by RFC 3066, but publishers have been known to publish random values like “English” or “German”. Universal Feed Parser does not do any parsing or normalization of language codes.

language may come from the element’s xml:lang attribute, or it may inherit from a parent element’s xml:lang, or the Content-Language HTTP header. If the feed does not specify a language, language will be None, the Python null value.


The original base URI for links within the entry summary.

base is only useful in rare situations and can usually be ignored. It is the original base URI for this value, as specified by the element’s xml:base attribute, or a parent element’s xml:base, or the appropriate HTTP header, or the URI of the feed. (See Relative Link Resolution for more details.) By the time you see it, Universal Feed Parser has already resolved relative links in all values where it makes sense to do so. Clients should never need to manually resolve relative links.