-
Notifications
You must be signed in to change notification settings - Fork 19
Packaging for WP Audiobooks
Wendy Reid edited this page Jan 2, 2019
·
21 revisions
A packaging standard is required for Audiobooks, and WP as a whole. The best option would be to find something that works for both WP and Audiobooks, unless technical requirements prevent it. To make the best decision, it is best to compare the potential options.
| OCF | OCF (lite) | Pure ZIP | OPC | MPEG 14 | Web Packaging | HEIF | |
|---|---|---|---|---|---|---|---|
| Specification link | Link | [OCF Lite] | Link | Link | Link | Link | dsinger preso |
| Spec status | mature, IDPF rec, CG draft | doesn't exist | mature | mature, ISO/IEC | mature | wildly experimental | unknown |
| Compression | Zip | Zip | Zip | Zip | n/a? | CBOR | n/a? |
| Where to start? |
/META-INF/container.xml points to package.opf
|
index.html? other well-known filename? |
no convention | --- | n/a | WAM manifest with start_url? |
? |
| What system(s) supports it? | EPUB Reading Systems | ? | everything but browsers | ? | iTunes, various audio/media players | Chrome behind flags | ? |
| Additional features | digital signatures, encryption, multiple renditions | ? | ? | ? | bookmarkable | provides signed web origin | ? |
| Pros | widely used in EPUB, well understood | can be designed to our requirements? | ubiquitous, simple | ? | you can make and listen to audio books today | compatible with web security model | ? |
| Cons | more complex than needed | doesn't yet exist | boring | ? | hard to figure out capabilities | not ready, lots of complexity | ? |
Packaging for WP and Audiobooks should fit into the following requirements:
- Simple - the option we choose should be straightforward and understandable to the industry