OCF needs to point at OPF/OPS not OEBPS 1.2
| Project: | EPUB Maintenance |
| Component: | Open Container Format (OCF) |
| Category: | task |
| Priority: | normal |
| Assigned: | GConboy |
| Status: | completed @ 2.0.1 |
Jump to:
OCF was done as the first of the three specification that now make up EPUB. At that time it was documents as a container for OEBPS 1.2 (as that was the then current markup standard). The OCF specification needs to be updated to refer to OPF/OPS 2.0 and become a full fledged member of the EPUB trio.
This change will be done during the (real soon now) 2.0.1 maintenance pass over the specs, it can not be done as a simple errata -- it requires mechanical, but substantive, changes throughout the specifications. Also, it should entail a change from "OCF" standing for "OEBPS Container Format" to "Open Container Format" (to match OPS and OPF) [finally]. Notes covering these points moved into the "Tie the three specs to EPUB" issue, as that is the issue that should drive a logical unification (while keeping three documents) pass over all three specifications.
This will be done in the 2.0.1 spec-pass.
- Login to post comments
Comments
#1
#2
Promoting to "Proposed resolution" the resolution being "accepted". This change, while required, can not be done as a simple errata -- it requires mechanical, but substantive, changes throughout the specification. Also, it should entail a change from "OCF" standing for "OEBPS Container Format" to "Open Container Format" (to match OPS and OPF) [finally]. I will move notes covering these points into the "Tie the three specs to EPUB" issue, as that is the issue that should drive a logical unification (while keeping three documents) pass over all three specifications.
#3
Moved to "accepted."
#4