Go directly to main content.

Tie the three specs to EPUB

Project:EPUB Maintenance
Component:General
Category:task
Priority:normal
Assigned:GConboy
Status:completed @ 2.0.1

There should be an introductory paragraph (at least) in each of the three specs (OCF, OPF, OPS) that defines what EPUB is, and that "this" spec is one of the three components.  Perhaps we should also incorporate (real soon to be defined) EPUB branding/logo into each of the three specs.

Description
Issue Id: 
5
Resolution: 

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.  The required resolution will drive a logical unification (while keeping three documents) pass over all three specifications.

The following two changes should also be made during this pass:

-- OCF should point at OPS/OPF publications, not OEBPS 1.2.  Thus, that issue is proposed to be dismissed and moved here.

-- It should entail a change from "OCF" standing for "OEBPS Container Format" to "Open Container Format" (to match OPS and OPF) [finally]

-- All current agreed errata shall be incorporated

-- include a non-normative list of approved extensions -- reference the font mangling informational document from OCF.

 

Comments

#1

Assigned to:Anonymous» GConboy

#2

This change can not be done as a simple errata -- it requires mechanical, but substantive, changes throughout the specifications.  The required resolution will drive a logical unification (while keeping three documents) pass over all three specifications.

The following two changes should also be made during this pass:

-- OCF should point at OPS/OPF publications, not OEBPS 1.2.  Thus, that issue is proposed to be dismissed and moved here.

-- It should entail a change from "OCF" standing for "OEBPS Container Format" to "Open Container Format" (to match OPS and OPF) [finally]. 

#3

 Further any previously agreed errata's should be incorporated into their respective specifications during this pass.

#4

Status:open» proposed resolution

 Moved to "Proposed resolution" -- status to be changed to "accepted" (see resolution field).

#5

Status:proposed resolution» accepted

 Moved to "accepted."

#6

Status:accepted» completed @ 2.0.1
Valid XHTML 1.0!

Powered by Drupal, an open source content management system