Code Monkey home page Code Monkey logo

Comments (6)

rla avatar rla commented on September 26, 2024

As I see there are requests for 3 extensions:

RSS Content module

I find very little information about it. The MDN article mentions RDF serialization. This requires RSS 1.0 support? There won't be any RSS 1.0 support unless someone contributes patches :) AND proves them to be memory safe and without any leaks. Supporting <content:encoded> element only is doable.

Dublin Core

I had some thoughts about supporting it before but the full spec is too large and complex to get right. One way would be extracting everything under "dc" namespace and slap it either to feed or item under dc property. This means no interpretation of data or children elements (I'm not sure how many nested elements are in DC). Another option is to try to extract only sensible information but someone has to decide which elements of DC are selected. The DC support will be behind a flag.

Arbitrary extensions

This also covers the two above. Could be done by extracting everything under feed/item elements and slapping under raw property or something like that. No interpretation of data would be made (dates will be strings). This should be put behind a flag. I'm not sure what to do with nested elements that are not items inside the feed.

Implementation issues:

RapidXML does not support namespaces. Elements like <dc:date> will just appear as tags "dc:date". I'm pretty sure that some stupid feed will use other namespace than "dc" to prefix DC elements.

from fast-feed.

rla avatar rla commented on September 26, 2024

Implementing arbitrary extensions would be the best/easiest/lowest burden way?

<content:encoded> is for RSS (not Atom) and its contents should appear under content property of items (currently RSS item has description)?

from fast-feed.

rla avatar rla commented on September 26, 2024

Would be nice to know how other feed parsers solve the issue with custom extensions.

from fast-feed.

amazing-gao avatar amazing-gao commented on September 26, 2024

node-feedparser supports many namespaces.
But i don't like the usages of steam method. :)

from fast-feed.

rla avatar rla commented on September 26, 2024

I added support for <content:encoded>element. It will appear as content property on the RSS 2 item. Published version 1.3.0.

It is unlikely that I can work on other extensions before 3rd June.

from fast-feed.

rla avatar rla commented on September 26, 2024

Extensions for the arbitrary case have been implemented and documented in the README. Published version 1.4.0.

from fast-feed.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.