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
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.
The text was updated successfully, but these errors were encountered:
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.
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
orapplication/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.
The text was updated successfully, but these errors were encountered: