pull/331/head
Dave Jones 2022-01-20 11:33:32 -06:00
rodzic e6a9c3acce
commit 5a0b06bf18
1 zmienionych plików z 4 dodań i 3 usunięć

Wyświetl plik

@ -774,14 +774,15 @@ apps know.
All tags that are valid as children of a standard `<item>` tag are also valid as children here.
When specifying the audio/video source, the [`<podcast:alternateEnclosure>`](#alternate-enclosure) tag is highly encouraged since it gives the broadest coverage of possible stream types and is
explicit in it's communication of what transport protocol and media codecs are being used. In addition to [`<podcast:alternateEnclosure>`](#alternate-enclosure), a standard `<enclosure>` should
explicit in it's communication of what transport protocol and media codecs are being used. In addition to [`<podcast:alternateEnclosure>`](#alternate-enclosure), a standard `<enclosure>` should also
be given as a fallback to support podcast apps that don't yet implement [`<podcast:alternateEnclosure>`](#alternate-enclosure). Regardless of which enclosure tag is used, feed owners must be conscious
of the fact that choosing a non-mainstream streaming protocol/codec will limit the number of apps that can play the content. For that reason, it's highly recommended to use only the two most widely supported
protocols (mp3 and mp4/h.264) to ensure compatibility with the broadest number of apps on various platforms. Choosing a streaming format that is outside of this narrow list might exclude many
apps from playing your content. As broader adoption of HLS, Opus, etc. becomes apparent, this recommendation will change to include newer formats.
The [`<podcast:contentLink>`](#content-link) tag is also required to ensure that listeners have a fallback option in case their chosen app cannot play the given content stream directly. Podcasters
who live stream to multiple platforms at once can also use the `<podcast:contentLink>` tag to provide links to those other platforms.
The [`<podcast:contentLink>`](#content-link) tag is also required to be present, to ensure that listeners have a fallback option in case their chosen app cannot play the given content stream directly. In
most instances this will just be a link to an HTML page that can play the live stream. Such a page can reside on the podcaster's own website, a page provided by their hosting company or a third party
platform they have chosen to use. Podcasters who live stream to multiple platforms at once can also use the `<podcast:contentLink>` tag to provide links to those other platforms.
A robust, well-written `<podcast:liveItem>` tag will include all three of: [`<podcast:alternateEnclosure>`](#alternate-enclosure), `<enclosure>` and [`<podcast:contentLink>`](#content-link) to
ensure the broadest interopability with podcast apps.