A wholistic rss namespace for podcasting that is meant to synthesize the fragmented world of podcast namespaces. The broad goal is to create a single, compact, efficient namespace that is easily extensible, community controlled/authored and addresses the needs of the independent podcast industry now and in the future. Our hope is that this namespace will become the framework that the independent podcast community needs to deliver new functionality to apps and aggregators.
Our guiding principles for development of this namespace are the "Rules for Standards Makers" by Dave Winer. Please read it before contributing if you aren't familiar with it.
The podcast namespace is part of the larger "Podcasting 2.0" project which exists to bring control of podcasting's protocols back into the hands of the open podcasting community. A good overview can be found here: Podcasting 2.0
- Official XMLNS Definition the official definition of all formalized tags.
- List of platforms and apps that currently implement some or all of these tags: Supporting Platforms and Apps.
- Example Feed: There is an example feed example.xml in this repository showing the podcastindex namespace side by side with the Apple itunes namespace.
- Other recommendations when creating RSS podcast feeds.
Phase 1 - [Closed] Comment period closed on 11/15/2020 and 5 tags were formalized.
Phase 2 - [Closed] Comment period closed on 1/31/2021 and 4 tags were formalized.
Phase 3 - [Closed] Comment period closed on 6/1/2021 and 5 tags were formalized.
Phase 4 - [Closed] Comment period closed on 12/1/2021 and 3 tags were formalized.
Phase 5 - [Closed] Comment period closed on 7/15/2022 and 2 tags were formalized.
Formalized - This tag is frozen and listed in the XMLNS document. Any future changes to it's definition must maintain backwards compatibility.
Finalized - The tag is structurally stable and implementation testing should be considered safe. Any breaking changes will be widely communicated.
Open - The tag/phase is open for discussion and collaboration.
Required - This tag or attribute must be present.
Optional - This tag or attribute may be left out.
Recommended - This tag or attribute is technically optional, but is strongly recommended to be present for the tag to function as fully intended.
To be adopted as an official part of the namespace, there must be consensus around a tag's usefulness and either commitment to adoption by at least 1 host and 1 app, or a recognition that the tag is already being used in the wild.
It is ALWAYS ok to delay a tag to a future Phase if there is any concern about it. That is to be expected and encouraged.
When a Phase comes to a close, there will be a full review of any tags currently open for comment and questions will be asked to gather consensus before final adoption. No tags will be adopted by fiat, or if there are unresolved questions. They will just be moved to the next Phase for further comment and refinement.
Tags that are proposals or rough ideas should be expected to have syntax problems or typos. Those should be refined away as they are worked on. If they are not, that is a good idea that the tag in question isn't being seen as useful and should be considered for dropping.
We are not a "standards body". It is a community driven project where all stake holders are encouraged to participate, so that many voices are heard. This is an open-source project to be built fully in the open. Discussions also take place on podcastindex.social where anyone is free to register and participate.
There is significant overlap amongst the many existing podcast namespaces. Each platform and publisher has created their own namespace to give their respective system and audience the metadata they need in the way they want it delivered.
The only required tags should be those that solve an overwhelming need in the industry. Requiring tags is a roadblock to adoption and should be avoided. Attributes should also only be required when they are key to the functionality of the tag.
Reinventing the wheel helps nobody. When at all possible, existing conventions should be maintained. For example, it would make sense to turn <podcast:explicit> into a unary element, where it's existence is taken as a "yes" and it's absence as a "no". But, that has never been the standard. And, given as how this namespace will probably sit alongside at least one other namespace, it makes sense to keep existing conventions in place.
There is no way to address every possible metadata point that each platform would want. That is not the aim. Instead we focus on defining the elements that would be useful to the broadest set of apps, publishers, platforms and aggregators. Individual parties can keep their respective supplemental namespaces small and targeted as an adjunct to this larger namespace. But, we don't want to be so general that the spec becomes overly complicated. A beautiful, "perfect" spec is not important. Solving real problems is.
The following tags have been formally adopted into the namespace. They are fully documented in the XMLNS document located here. Please see that file for full implementation details.
- <podcast:locked>
- <podcast:transcript>
- <podcast:funding>
- <podcast:chapters>
- <podcast:soundbite>
The following tags have been formally adopted into the namespace. They are fully documented in the XMLNS document located here. Please see that file for full implementation details.
- <podcast:person>
- <podcast:location>
- <podcast:season>
- <podcast:episode>
The following tags have been formally adopted into the namespace. They are fully documented in the XMLNS document located here. Please see that file for full implementation details.
- <podcast:trailer>
- <podcast:license>
- <podcast:alternateEnclosure>
- <podcast:source>
- <podcast:integrity>
- <podcast:source>
- <podcast:guid>
The following tags have been formally adopted into the namespace. They are fully documented in the XMLNS document located here. Please see that file for full implementation details.
- <podcast:medium>
- <podcast:images>
- <podcast:liveItem>
The following tags have been formally adopted into the namespace. They are fully documented in the XMLNS document located here. Please see that file for full implementation details.
- <podcast:socialInteract>
- <podcast:block>
The following tags are under review for inclusion in this phase. Changes to them are now frozen. Any modifications will mean the tag needs to be reworked and submitted to Phase 6.
<podcast:complete> - Discuss
<podcast:complete
archive="[feed url(string)]"
>
[yes|no(bool)]
</podcast:complete>This element allows a podcaster to signal to the world that this podcast will never publish another episode to this feed. In it's basic form, it is a direct drop-in
replacement for <itunes:complete> and functions identically. The addition of the archive attribute allows for specifying the url of a complete archival feed of the
podcast that contains every episode in case this feed does not.
Specifying a value of no is the same as this tag not being present.
- archive (optional) A url of a feed that contains every episode of this podcast.
Examples:
<!-- This podcast will never publish again -->
<podcast:complete>yes</podcast:complete>
<!-- Redundant usage and not recommended -->
<podcast:complete>no</podcast:complete>
<!-- This podcast is over, and a complete episode archive feed is "here" -->
<podcast:complete archive="https://example.org/rss/myarchive.xml">yes</podcast:complete>A list of the current proposed tags can be found in the issues section here.
If the "locked" element is present and set to "yes", podcasting hosts should not allow importing of this feed until the email listed in the element's owner="" attribute is contacted and subsequently changes the value of the element to "no".
There can be multiple <podcast:id> elements to indicate a listing on multiple platforms, directories, hosts, apps and services. The "platform" attribute shall be a slug representing the platform, directory, host, app or service. The full list is here. More should be added by the community as needed.
