Proposal: Podcasting 2.0 Certification

[theDanielJLewis]

I propose that we offer a "Podcasting 2.0 Certified" program and badge.

The requirements would be simply: support at least 75% (or so) of the finalized features. This then gives that app- or tool-provider a certification they can proudly display.

Think of how being IAB-certified is a badge of honor and validity among podcast-hosting providers. "Are you Podcasting 2.0 certified?" could be the new litmus test.

The certification process would be simple:

1. Applicants register and checkmark a list of features that they support and provide evidence of such.
2. Someone reviews and verifies that those features are truly supported.
3. Applicant is awarded the certification and the Podcast Index website adds the provider to the certification list.

I suggest it not require 100% conformity because there could be some things that are too expensive (in time or money) for developers to support. For example, handling the value block inside a podcast app. So the certification could be given based on supporting a large-majority percentage of the features, or maybe it's given for supporting for the tags the program reasonable deems required.

I think the value in this goes beyond a gold-star sticker. It gives something podcasters can ask about, even if they don't understand what it all means, just like many have done with the IAB certification. And getting tech-unsavvy podcasters and consumers to start asking for and demanding Podcasting 2.0 certified options can help interest become viral.

[mikeneumann]

This sounds like a great way to "Boost!" Value-for-Value adoption.

My concern is point #2, above; "Someone".

Unless this is somehow automated, at least partially, for human review/arbitration, it will bury a human. Perhaps some kind of Schema DTD-driven "lint"er that would periodically do a pass over the Index to do this? Kinda like Github does with its build stats for repos?

• Podcasting 2.0 Tags implemented, implemented but with errors.
• Phase 1 tags, Phase 2 tags, Phase 3 tags...
• How to handle complex vs simple tags? not syntactically, but in a generally-accepted level-of-effort to implement.
• Are there mandatory (some minimum set) tags?

Does the Podcasting Index care about allowing/requiring maintaining backward compatibility to "iTunes". i.e. Does a Podcasting 2.0 Certified(TM) stream need to maintain backward compatibility to iTunes or any other proprietary syntax? if so, for what period of time? 1 year? 2, 3 years?

Am I conflating "Podcasting Index" with "Podcasting 2.0" Certification with these questions?

[theDanielJLewis]

@mikeneumann, I mean for this certification for developers and service providers, not for individual podcasters. For example, (making up this list) Overcast, Podfriend, Captivate, Libsyn, and Podcast Addict could all be Podcasting 2.0 certified because they support enough of the features.

I think making certain reasonable features mandatory would help developers prioritize support.

There are certain issues, like how the lock tag is unnecessary for podcast apps to support, but necessary for publishing tools.

We could even have different levels of the standard. Like Podcasting 2.0 Certified Gold supports every feature, while Bronze supports the bare minimum. That can encourage some health competition, but might confuse users.

[keunes]

I think in addition to hosters/service providers and podcaster-tools, it would also be great if clients like AntennaPod and Podfriend could get certified.

I like the idea of the different levels, but (in addition to confusion for end-users) that would mean extra work to check that the right level is awarded. As new tags are introduced recalculations are needed already, so I reckon that's enough of a task already.

@theDanielJLewis Did you intend this to be strictly about the Podcast Namespace? Or was your idea to also cover Podcast Index integration?

I think making certain reasonable features mandatory would help developers prioritize support.

While the idea is nice to get some minimum level of support, if there already is like a '75%' threshold I would leave it at that. A percentage without identified required tags would leave freedom to app developers to decide which tags they find relevant or important for their app. E.g. an audio-tour-app might decide that the 'person', 'season' and 'recommendations' tags aren't relevant to them. If for some reason we had identified 'season' as required such app developer would be limited.

Maybe a different number of points could be awarded per tag. More difficult tags (like value) and more important ones (tbd) could be worth more. That way we can provide an incentive while still maintaining some flexibility.

[theDanielJLewis]

I think in addition to hosters/service providers and podcaster-tools, it would also be great if clients like AntennaPod and Podfriend could get certified.

Yes. That's the "app" part I mentioned.

Did you intend this to be strictly about the Podcast Namespace? Or was your idea to also cover Podcast Index integration?

I see it as a namespace thing. Probably nearly all podcasters and listeners won't care about the catalog source, only that it has the podcasts they want. But the benefits that come with Podcasting 2.0 features are what might compel people to try those apps or services.