Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for the "podcast" namespace #301

Open
ibz opened this issue Jan 6, 2022 · 1 comment
Open

Add support for the "podcast" namespace #301

ibz opened this issue Jan 6, 2022 · 1 comment

Comments

@ibz
Copy link

ibz commented Jan 6, 2022

The "podcast" namespace is getting quite some traction these days. It would be awesome to be able to properly parse feeds that use this namespace.

Details about the "podcast" namespace: https://github.com/Podcastindex-org/podcast-namespace
1.0 spec: https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md

More specifically, I am trying to parse the podcast:valueRecipient tags and I took this feed as an example: http://feed.nashownotes.com/rss.xml

What happened was: only the last of the 5 recipients is accessible in the parsed feed (under ['feed']['podcast_valuerecipient']).

I'm happy to look into this, but it seems like adding new namespaces is non-trivial and I don't see any tutorials on how to do it, so I guess I would just have to see how other namespaces are implemented and try doing the same - right?

Before that - is there some quick fix through which I could possibly access all tags of an unknown/unsupported namespace in the parsed feed?

Cheers!

@ibz
Copy link
Author

ibz commented Jan 6, 2022

Could this be related to this BTW? #297

I think support for the "podcast" namespace would be still nice, and I am willing to spend a little time to look into it, but the fact that multiple tags become inaccessible seems like a more general issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant