Django

Code

Ticket #1028 (assigned)

Opened 3 years ago

Last modified 2 months ago

High-level feed framework should make more feed elements available

Reported by: ubernostrum Assigned to: ekarulf (accepted)
Milestone: Component: RSS framework
Version: SVN Keywords: feature_request
Cc: toke-django@toke.de, dan90 Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Currently, certain RSS and Atom elements can be populated only by making use of the "low-level" feed framework; this is particularly annoying in the case of certain common items such as the RSS category element. Ideally, all valid elements could be populated by use of the high-level framework, but in practice perhaps it would be best simply to determine which elements are needed in the most common use cases, and provide access to them.

One possible implementation would be to extend the high-level framework's use of the template system; instead of providing templates for the title and description elements, perhaps the high-level framework could allow specification of a template for the complete item element. For example, a publisher who wished to list the categories to which items belong would be able to include this in the template for items in an RSS feed:

{% for category in obj.get_category_list %}
<category>{{ category }}</category>
{% endfor %}

Attachments

Change History

01/18/07 02:38:57 changed by Simon G. <dev@simon.net.nz>

  • stage changed from Unreviewed to Design decision needed.

03/09/07 06:54:09 changed by mtredinnick

  • stage changed from Design decision needed to Accepted.

I don't know if the template approach is the correct one, but the sentiment of the bug report is correct: we are a bit restricted when it comes to creating full feeds.

09/14/07 11:39:11 changed by cmcavoy

  • owner changed from nobody to cmcavoy.
  • status changed from new to assigned.

taking a sprint stab at this, if anyone else wants to help i'm cmcavoy on irc.

09/15/07 09:53:44 changed by toke

  • cc set to toke-django@toke.de.

09/15/07 14:32:14 changed by PhiR

  • keywords set to feature.

09/15/07 14:32:38 changed by PhiR

  • keywords changed from feature to feature_request.

(in reply to: ↑ description ) 05/05/08 01:25:25 changed by mikechambers

Replying to ubernostrum:

Try to document which RSS elements are not supported.

Looking at the RSS 2 spec:

http://blogs.law.harvard.edu/tech/rss

and

django.utils.feedgenerator.Rss201rev2Feed / RssFeed?

It appears the the following optional rss.channel are missing:

managingEditor webMaster pubDate generator docs cloud image rating textInput skpiHours skipDays

05/05/08 01:29:27 changed by mikechambers

That is "I am trying to document which RSS elements are not supported". I will go over item elements next.

06/10/08 13:20:06 changed by ekarulf

  • owner changed from cmcavoy to ekarulf.
  • status changed from assigned to new.
  • version set to SVN.

RSS 2.0 Missing Elements:

Compared RSS 2.0 Spec against feedgenerator.py(r7066)'s Rss201rev2Feed class

  • Channel
    • managingEditor
    • webMaster
    • pubDate
    • generator
    • docs
    • cloud
    • image
    • rating
    • textInput
    • skipHours
    • skipDays
  • Item
    • Currently contains TTL field, not specified in RSS 2.0 spec
    • pubDate
    • source

I'll take a shot at this later in the week, since I assume cmcavoy was not able to finish at the last sprint.

(follow-up: ↓ 14 ) 06/10/08 13:20:16 changed by ekarulf

  • status changed from new to assigned.

(follow-up: ↓ 12 ) 06/17/08 02:36:09 changed by dan <dan@possumpalace.org>

  • cc changed from toke-django@toke.de to toke-django@toke.de, dan@possumpalace.org.

Other things to think off include the entire idea of the extensibility of RSS - embedding [geographical information], say. Or is that getting off-topic?

More generally, as an RDF format, RSS 1.0 potentially includes the entire world of RDF as embeddable info, although presumably the humble django feed framework is not intended to encompass all of that.

(in reply to: ↑ 11 ) 06/17/08 11:14:19 changed by ekarulf

Replying to dan <dan@possumpalace.org>:

Other things to think off include the entire idea of the extensibility of RSS - embedding [geographical information], say. Or is that getting off-topic? More generally, as an RDF format, RSS 1.0 potentially includes the entire world of RDF as embeddable info, although presumably the humble django feed framework is not intended to encompass all of that.

I think that might be getting a bit off topic. The syndication code defines the various feed formats using OO-style inheritance. I think that if someone wanted to embed geographical info (or any other bits) they could accomplish it using the existing framework. That said, I will see if I can't leave a hook to make extending more flexible.

08/03/08 20:41:25 changed by dan90

  • cc changed from toke-django@toke.de, dan@possumpalace.org to toke-django@toke.de, dan90.

(in reply to: ↑ 10 ; follow-up: ↓ 15 ) 08/07/08 23:32:08 changed by taojian

It would also be very nice to be able to specify feed stylesheets:

<?xml-stylesheet type="text/css" href="http://example.com/rss.css" ?>

class MyFeed(Feed):
    stylesheet = 'http://example.com/rss.css'

Unless this is already possible...?

(in reply to: ↑ 14 ) 09/21/08 01:34:05 changed by anonymous

Looking for discount prices on designer handbags? Visit http://www.designer-handbags-purses.com for the lowest prices on Coach handbags, Vera Bradley handbags and many other designer handbags. *


Add/Change #1028 (High-level feed framework should make more feed elements available)




Change Properties
Action