Dominic, Ian, John, Nick, Lloyd, Fujimori
OCF Container Sample Review
- Reuben sent around to group on 3/12/2009.
- Lloyd had unpacked it the other day and looked at it, but had not tried playing it.
- John had tried it in bookworm, although some of the text seemed to get lost.
ODF Container Sample
- John used the same sample book as in the OCF, and created a package but had nothing to try it out in, and it may not be quite right. OpenOffice did not recognize it.
- Packaging requirements are simple in ODF. It only requires a META-INF/manifest.xml. This duplicates much of what is in the DAISY OPF file (path and mime-type) but also allows you to add information about encryption if it is used.
- The 1.1 spec is current, and has the packaging as a small section at the end. The 1.2 spec is in progress and will separate the packaging spec more clearly, but a draft of that portion is not publicly available yet. Technical specs at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical.
- The OCF spec refers to portions of ODF, but either an old version (OCF uses the 1.0 "container.xml" spec) or a non-version (the namespace "urn:oasis:names:tc:opendocument:xmlns:container" that is not in any ODF version)
- Nick: Do we need to worry about packaging older versions of DAISY files in the new container? That is, should we expect a player to be able to play a DAISY 2005 book that arrives in the new container? (Dominic: probably not)
- Use of Protected DTBook spec (http://www.daisy.org/projects/pdtb/daisy-pdtb-spec.html). Will the encryption options offered with a container replace this? Is anyone using it now? It seems that we could perhaps choose a container without DRM issues and incorporate the PDTB spec.
- OPC/OOXML: Lloyd has looked at it briefly. It may be using a more recent ZIP format; if so it might allow the option of using implosion instead of deflation. The spec seems to describe a lot of relationship files, with the flexibility (and complexity) of indirection. See Nick's description from 10/22/2008 meeting minutes.
- Need for compression
- Nick: We should look for a minimal container that lets us do what we need to do, without constraints or requirements that we don't need. With this in mind, are there any containers that we can disqualify yet?
- Lloyd: For audio-only books, there is some amount of XML, but compression isn't going to give you much space saving, so not much value in it.
- Nick: For lightweight players to use a ZIP container, requiring it to work with compressed files means extra resource requirements (processing power and/or memory), so compression should be optional, not mandatory.
- Technical Committee phone call 4/1/2009: Agenda TBD
- Container group call 4/8/2009: OPC/OOXML discussion