Skip to content
This repository has been archived by the owner on Apr 9, 2022. It is now read-only.

Should core media types be defined in EPUB? #1

Open
dauwhe opened this issue Mar 29, 2018 · 1 comment
Open

Should core media types be defined in EPUB? #1

dauwhe opened this issue Mar 29, 2018 · 1 comment

Comments

@dauwhe
Copy link

dauwhe commented Mar 29, 2018

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?

@mattgarrish
Copy link
Member

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants