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.

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

Chapters MIME-type does not adhere to RFC 6839 #312

Open
ziggythehamster opened this issue Nov 11, 2021 · 1 comment
Open

Chapters MIME-type does not adhere to RFC 6839 #312

ziggythehamster opened this issue Nov 11, 2021 · 1 comment

Comments

@ziggythehamster
Copy link

It may be too late to fix this, but the syntax of the chapters MIME-type is not conforming to RFC 6839, which would prevent it from ever being registerable as an IANA media type.

In MIME-types, the +suffix should be something like +json, +xml, +der, or another registered suffix type. application/vnd.podcast.chapters+json would be a legal MIME-type, or if you were aiming for registering it with the IANA, application/podcast-chapters+json or application/chapters+json (the latter most likely would be rejected for being too broad given the limited scope of the spec).

If you wanted to fix this in the future, I think the spec would need to say that clients should support the old MIME-type as well, and that servers should use the new type.

@daveajones
Copy link
Contributor

If you wanted to fix this in the future, I think the spec would need to say that clients should support the old MIME-type as well, and that servers should use the new type.

Thanks for bringing this up Keith. I think this approach makes a lot of sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants