Skip to content
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.

Sign up for GitHub

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

fix broken URL formatting in namespace 1.0.md #619

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

fix broken URL formatting in namespace 1.0.md #619

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9f613cc
fix broken URL formatting in namespace 1.0.md
Marzal Mar 22, 2024
e153d3b
fix Soundbite markdown link
Marzal Mar 22, 2024
ba344b6
Fix Live Item <enclosure> URL wraping
Marzal Mar 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions docs/1.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1037,9 +1037,9 @@ All tags that are valid as children of a standard `<item>` tag are also valid as

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>`](https://cyber.harvard.edu/rss/rss.
html#ltenclosuregtSubelementOfLtitemgt) should also be given as a fallback to support podcast apps that don't yet
implement [`<podcast:alternateEnclosure>`](#alternate-enclosure).
what transport protocol and media codecs are being used. In addition to [`<podcast:alternateEnclosure>`](#alternate-enclosure), a standard
[`<enclosure>`](https://cyber.harvard.edu/rss/rss.html#ltenclosuregtSubelementOfLtitemgt) 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
Expand Down Expand Up @@ -1285,9 +1285,8 @@ In plain language, the sequence of discovery an ingesting platform should use is
`<podcast:txt>`<br><br>
This element holds free-form text and is modeled after the DNS "[TXT](https://en.wikipedia.org/wiki/TXT_record)"
record. It's meant to allow for usages that might be niche or otherwise not rise to the level of needing a
dedicated tag. Just like TXT records in DNS allowed for new things like [SPF](https://en.wikipedia.
org/wiki/Sender_Policy_Framework#Implementation) to evolve, this tag can allow novel techniques to be created and
sandboxed without a formalization process.
dedicated tag. Just like TXT records in DNS allowed for new things like [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework#Implementation)
to evolve, this tag can allow novel techniques to be created and sandboxed without a formalization process.

### Parent
&nbsp; `<channel>` or `<item>`
Expand Down Expand Up @@ -1681,4 +1680,4 @@ use the `<podcast:chat>` tag at the `<item>` or `<podcast:liveItem>` level.
accountId="@bob:example.com"
space="#general:example.com"
/>
```
```