You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a podcast I participate, we often list in the show notes, of a given episode, other episodes from the same podcast, that are related to the same topic.
With a tag to list related episodes, clients could show already the option to download or add these episodes to the playing queue.
A syntax for the tag could simply be:
<!-- tag can be multiple -->
<podcast:relatedEpisodeguid="[ep guid]"/>
<podcast:relatedEpisodeguid="[e p guid]">[comment on why it is related]</podcast:relatedEpisode>
To a certain extent this could be covered with <podcast:recomendations> (#205), but I feel this could be self contained in the feed without too much cluttering, without delegating to an external resource.
PS: I don't have strong feelings about it, but I thought it would be good to have it documented for discussions.
The text was updated successfully, but these errors were encountered:
If this is "tagging" other episodes your talking about inside an episode,
maybe it's kinda in the scope of #180 : tagging content you talked about
inside an episode.
I had in mind movies, music, TV shows etc and a whole podcast, but tagging
another episode of the same feed seems useful too.
Been thinking a lot about this today, and also #180 . What were really talking about, it seems, is structured show notes. I think this could really benefit from a bigger group discussion. I have it marked down as a show topic and I’m going to bring it up on podcastindex.social.
In a podcast I participate, we often list in the show notes, of a given episode, other episodes from the same podcast, that are related to the same topic.
With a tag to list related episodes, clients could show already the option to download or add these episodes to the playing queue.
A syntax for the tag could simply be:
To a certain extent this could be covered with
<podcast:recomendations>
(#205), but I feel this could be self contained in the feed without too much cluttering, without delegating to an external resource.PS: I don't have strong feelings about it, but I thought it would be good to have it documented for discussions.
The text was updated successfully, but these errors were encountered: