-
Notifications
You must be signed in to change notification settings - Fork 116
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
Proposal: <podcast:trailer> #84
Comments
@KieranMcKeefery There is wording for a single I know the name "alternateEnclosure" doesn't fit for this application. But, RFSM: "It totally doesn't matter what we call it. We can learn to use anything. There are more important things to spend time on." :-) |
Food for thought: There's an argument for letting the feed support both 1 trailer to define the show, and various trailers. A pod can release a new trailer for each new season, for example. However, a non-seasonal show could also just have 1 trailer they always want to feature. Not proposing a solution, here, though. ;/ |
That's great to point out! We do already have that in the iTunes namespace with the use of episode type, episode number, and season number. So I agree with Stacey that we need to ensure whatever we do supports that same level of flexibility, if not more. |
What are we thinking here? A |
Or maybe @KieranMcKeefery wants to write it up? |
I recommend innovating on Apple's foundation. They use I suppose we could have a |
+1 |
Could we consider adding some addition information for a trailer? Like a language tag? I would love to have trailer in several languages (even if my content is only in one language). . |
I’m down with that. Adding a language attribute seems appropriate to me. |
Do we not have one in the RSS spec anyway? How likely is the use-case that the trailer would be in a different language to the podcast it describes? |
Sorry @daveajones I'm not sure how I missed this - feel free to write it up. I think we continue to use Apple's trailer tag for the seasonal approach but I think this is more |
Paged feeds, as discussed in #117, would eliminate the need for a feed limit. That trailer at position 1 would always be there. This would not provide as much functionality as a trailer tag of some sort, but it might solve the described problem of trailers (and episodes) getting "chopped off" at the bottom end of a feed. |
@KieranMcKeefery What do you think about the way I wrote up the trailer tag in the README under the phase 3 section? Can you guys work with that structure? |
@staceygoers Would the tie-in with podcast:season work for you guys as well? |
That seems sharp! It could be even cooler if apps DID display multiple seasonal trailers, so that if a user wanted to "taste" the trailers for season 1/2/3, they could. But it's likely the default of pub:date makes sense. LMK if that was not the section you wanted me to dive into ... :) |
We can work with that for sure, looks great. |
Anyone else have thoughts or concerns about this tag? If not, I think it's ready to finalize. It's a fairly simple structure. |
I'm finalizing this tag. Barring any changes between now and 6/1/21 it will be formalized into the namespace. |
I've briefly touched on this with both @jamescridland and @tomrossi7 but I think there could be something in trailers, having trailers in the items block is great amongst episodes but I've come across a few occasions where trailers drop off of shows because they've got a limit of say 300 and they hit episode 301, boom the trailer is gone.
Now we can fix it of course by pinning the episode to the RSS at all times and removing the last episode but that does feel like a hacky way to do it.
What could we potentially do for trailers/pinned episodes inside RSS feeds? I'm not here to bloat RSS feeds by any means but I feel like we could do something better.
The text was updated successfully, but these errors were encountered: