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
{{ message }}
This repository has been archived by the owner on Apr 9, 2022. It is now read-only.
There does seem to be a tradeoff inherent in some of these external registries and other documents. It's easier to maintain a registry, but it makes it harder to read the spec when essential information is outside the spec. Especially with core media types, do we envision adding or deprecating core media types outside of an actual revision of EPUB?
The text was updated successfully, but these errors were encountered:
do we envision adding or deprecating core media types outside of an actual revision of EPUB
The problem with embedding in a spec is that it looks silly when new media types are rolled out that are fully supported by browser engines, yet are artificially invalid for use in EPUBs because there needs to be a full revision of the specifications before anyone can bless them into existence (or when something needs deprecating, like text/javascript). When it was taking three years per revision, that was a long time to sit waiting to make any modification.
But another thought would be to instead make the CMT document a staging ground. These media types could fall somewhere between the ones fully recognized in the specification and foreign resources (noted in epubcheck, for example, but not errors or warnings).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There does seem to be a tradeoff inherent in some of these external registries and other documents. It's easier to maintain a registry, but it makes it harder to read the spec when essential information is outside the spec. Especially with core media types, do we envision adding or deprecating core media types outside of an actual revision of EPUB?
The text was updated successfully, but these errors were encountered: