Bug 82070 - librss Should Treat Dublin Core and RSS Metadata Elements as Interchangable
Summary: librss Should Treat Dublin Core and RSS Metadata Elements as Interchangable
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepimlibs
Classification: Applications
Component: syndication (show other bugs)
Version: 4.7
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-23 19:31 UTC by Jared Warren
Modified: 2020-10-19 23:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Warren 2004-05-23 19:31:21 UTC 
Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages

If librss is parsing a channel or item and does not find a title or description in the RSS 1.0 namespace, I think it would be a good idea to check if there is metadata in the Dublin Core namespace. For example, the following should be semantically equivalent:

<rdf:RDF ... xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rss="http://purl.org/rss/1.0/">
  <rss:channel>
    <rss:title>Foo</rss:title>
  </rss:channel>
</rdf:RDF>

<rdf:RDF ... xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rss="http://purl.org/rss/1.0/">
  <rss:channel>
    <dc:title>Foo</dc:title>
  </rss:channel>
</rdf:RDF>

I think that this change would increase librss's interoperability with other XML technologies and in anticipation that RSS will depreciate its custom metadata elements for DC in the future.
Comment 1 Sandro Knauß 2020-10-19 23:09:23 UTC 
Thank you for taking the time to file a bug report.

The compontent kdepimlibs don't exist anymore since 2011. It was splitted into several parts some moved to Frameworks the other are still under de KDE PIM umbrella. 

The entire code base went through significant changes. We ported the source code in meanwhile  to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out the new 20.08 release and give your feedback.