Testimonials
driki opened this issue · comments
Thoughts about including a structured way for shows to promote testimonials? Testimonials provide social validation and help new listeners make selection choices.
Examples that 99% Invisible uses:
<testimonials>
<testimonial>
<description>99% Invisible…is completely wonderful and entertaining and beautifully produced.</description>
<author>Ira Glass</author>
<organization>This American Life</organization>
</testimonial>
<testimonial>
<description>We think what he’s doing is inspiring. It has a kind of rhythm and musicality that you don’t normally find in radio or podcast storytelling.</description>
<author>Jad Abumrad</author>
<organization>Radiolab</organization>
</testimonial>
</testimonials>
A wfw namespace supports a well structured way of doing this. The commentRss element just points to an external feed.
It's not even that uncommon, just a lack of support in clients.
Testimonials for marketing purposes feel like they are fundamentally different than arbitrary comments. Is there a way to use wfw without redefining its purpose?
While I think a whitelist of comments is exactly what testimonials are, I guess you're right, this could cause UI inconsistentcies.
I would again argue that an extension to Atom's links (a new rel) is better than a namespace for RSS. It's easier to implement, both creation and parsing. It's language aware. You can have one link to testimonials as a feed, and one to a web page.
It's easier to implement, both creation and parsing.
Need enlightenment. Can you make an example that's simpler to implement or parse than the example used at the top?
Well that needs new structures, new database tables. A link would just be another in an array. You have to remember that most podcast clients don't even support the RSS spec propperly, the harder it is for them the less it will be adopted.