RSS tags and substitutions

Asked by Stefaan Haesen

Hello,

The substitutions CONTENT and DESCRIPTION both display the content of the description-tag. This seems a bit confusing to me. Is there a reason for this ?

Kind Regards,
Stefaan

Running Xibo server 1.6.4

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Stefaan Haesen
Solved:
Last query:
Last reply:
Revision history for this message
Dan Garner (dangarner) said :
#1

One is the <description> and the other is the <content:encoded>

What happens to be in those tags is down to the feed itself

Cheers,
Dan

Revision history for this message
Stefaan Haesen (stefaanh) said :
#2

Hello Dan,

Thanks for your answer, but that was what I already assumed ...

I searched a little more and found my answer here:
http://www.rssboard.org/rss-profile#namespace-elements-content-encoded

5.2.1 content:encoded

Requirements

The content:encoded element defines the full content of an item (OPTIONAL). This element has a more precise purpose than the description element, which can be the full content, a summary or some other form of excerpt at the publisher's discretion.

The content MUST be suitable for presentation as HTML and be encoded as character data in the same manner as the description element.

Recommendations

The content:encoded element can be used in conjunction with the description element to provide an item's full content along with a shorter summary. Under this approach, the complete text of the item is presented in content:encoded and the summary in description.

All of the tested aggregators support the use of content:encoded to define an item's content with the exception of Mozilla Firefox 2.0, which only displays items by their title.

Only one of the aggregators, Bloglines, supports the related use of description as a summary.

When an item contains both elements, six of the eight aggregators display content:encoded and ignore description. FeedDemon displays the element defined last within the item element and Firefox 2.0 doesn't support descriptions.

Publishers who don't want to employ item summaries in their feeds SHOULD use the description element for an item's full content rather than content:encoded because it has the widest support.

Publishers who employ summaries SHOULD store the summary in description and the full content in content:encoded, ordering description first within the item. On items with no summary, the full content SHOULD be stored in description.

Revision history for this message
Dan Garner (dangarner) said :
#3

Yeah, I find the specification a little rough around the edges - use the description if there is no summary, but if there is a summary use the content encoded.

Xibo supports both so that you can adapt your layout on a feed by feed basis.

By the way - sorry for the short answers - I run out of time a lot :)

Cheers,
Dan