Opf Files

An EPUB 3 archive has a skeleton – the files which are mandatory to structure the content – and some flesh – the ebook content.

As explained in the introduction, the flesh is a set of (X)HTML 5 and CSS resources, javascript code, images, audio and video assets. Let’s focus on the skeleton then, which is specified as the EPUB Open Container Format (OCF).

Because only the current version supports the latest OPF file format. Search, therefore, e.g. On the manufacturer website after an available Flip Album File update. To make sure that your OPF file is not corrupted or virus-infected, get the file again and scan it with Google's virustotal.com. Please visit NARA’s site on Official Military Personnel Files (OMPFs) for details. OPF/eOPF Amendments. If you feel that your official personnel folder is in error, please submit a written request to:U.S. Office of Personnel Management Office of the Chief Information Officer Chief, Records Management and Data Policy 1900 E Street, N.W.

The first file you may spot in the zip archive is the mimetype file, which states that this archive is *really* an EPUB publication.

The content of this text file must be “application/epub+zip” and nothing else. This is how an EPUB reading system will assured he can process the ebook.

It is required that the mimetype file is the first file found in the zip archive. This may appear a weird constraint, but as a matter of fact this constraint originates in the Open Document file format which was the source of the EPUB file format. The rationale behind it is that if an application reads the first bytes of the archive, it will always find the same “magic numbers” (see here for OCF magic numbers). This can replace the detection of the format in case the file extension .epub is not reliable.

A practical issue with this requirement is that one cannot create a proper EPUB file with a simple zip tool: generic tools cannot guarantee that the mimetype file will be first in the archive.

This small XML file, found in the mandatory META-INF directory, is a bootstrapping item. It simply contains the relative location of the .opf file (a.k.a. package document), which is the brain of the publication and will be described shortly.

If the content.opf file is for instance in the folder content in the archive, then the location will be content/content.opf.

Using this information, the reading system will be able to open the .opf file and know more about structure of the publication.

EPUB 3 supports multiple renditions of an EPUB publication. You may find for instance a fixed-layout rendition and a reflowable rendition packaged in the same EPUB file. In such a case, container.xml will reference several package documents usually placed in several directories.

Apart from container.xml, you may find other files in the META-INF directory, like signatures.xmlwhich holds digital signatures of the container and its contents, metadata.xml and manifest.xml which may contain information about the publication itself (i.e. the container; this is useful in the multiple renditions use case), or proprietary files like com.apple.ibooks.display-options.xml. Their presence is rather exceptional, therefore we won’t describe them in details here.

This XML file carries bibliographic and structural metadata about an EPUB publication (or an EPUB rendition), and is thus the primary source of information about how to process and display that publication.

In this file, the reading system will find:

Some metadata

i.e. information about the publication (or rendition) content. Diverse sets of metadata (e.g. Onyx) can be expressed as XML elements, from different schemes. The only required elements in EPUB 3.01 are title, identifier, language and modified, from the Dublin Core set. A fixed-layout publication must be tagged by a specific metadata item in this set. Other metadata can be expressed inline, using a generic meta element, or as an external resource via a link element.

A manifest

i.e. the exhaustive list of all publication (or rendition) resources, including (x)html text chapters, images and videos or audio files, fonts, scripts, css files. The reading system will only process the files it finds in the list, and knows from their media type (a.k.a. mime type) that it can process them. From the properties declared on each item, the reading system will also know its type, e.g. if the file corresponds to a navigation document, cover image, vector graphic or a script. If the reading system cannot process the resource because its format is a bit exotic, it will find here the fallback resource he can process instead.

A spine

As its name indicates, this is a “backbone” where the reading system finds the default reading order of all publication “chapters”. As these sections of a publication may not really represent book chapters, each item of the sequence is called … a spine item. Each spine item contains a reference to a manifest item. Spine items can be declared as “non linear”, meaning they are not displayed in the normal flow, but can be reached from another spine item as supplementary content (e.g. popup content).

Below is a simple package document with metadata, a manifest and a spine.

A quick word about this file, sometime found in EPUB 3 containers: this is the deprecated EPUB 2 way of declaring a navigation document. Some EPUB 3 authors still prefer to include it so that EPUB 2 reading systems can process the publication. An EPUB 3 reading system will not access it, so we won’t bother describing its content.

Here is a diagram illustrating the complete structure of an EPUB file.

In this example, we find the .opf file and all content files in a directory named “OEBPS”. Why such a strange name? This is simply historical: Open eBook Publication Structure was the name of a legacy ebook format which has been superseded by the EPUB format. The acronym found its way in the publishing vocabulary and is still used by some EPUB authoring tools when they structure an EPUB publication, so that the .opf file and content files are not stored in the root of the EPUB archive (something which would still be harmless by the way).

The Readium projects provide rock-solid, performant building blocks and applications for processing EPUB3 publications. EDRLab is participating to the Readium codebase maintenance and evolution.

Support for people wih print disabilities is a key part of our mission. We collaborate with European publishers and major inclusing organizations on the creation of a born-accessible ebook market. We also make sure that Readium projects take into account the assistive technologies used by visually-impaired users.

It is the policy of the Department of General Services (DGS) that records of the Office of Human Resources (OHR) are open to public inspection at all times during normal working hours. Every person has the right to inspect any record except those that are exempted from public disclosure by statute or other authority.

Copies of records will be provided to any person with authorized access by OHR. The fee for this service may not exceed the direct cost of duplication. This includes the cost of operating the copy machine and the cost of the machine operator. Any reasonable portions of a record shall be provided after deletion of the portions that are exempted by law.

Records will not be removed from custody of the Personnel Officer or employee having responsibility for them. OHR reserves the right to be physically present during the inspection of any records.

Persons found guilty of stealing, willfully destroying, mutilating, defacing, altering or falsifying, removing or secreting, the whole or any part of such a record, map, book, paper or proceeding, or who permits any other person to do so, are punishable by imprisonment in state prison, or in a county jail not exceeding one year, or by a fine not exceeding $1000, or by both fine and imprisonment (Government Code [GC] section 6220-6201).

See “Public Record Inspection Guidelines” (GS 17) posted in the OHR reception area for further information.

DEFINITION
The term “personal information” means any information that is maintained by an agency that identifies or describes an individual, including, but not limited to, his/her name, social security number, physical description, home address, home telephone number, education, financial matters, and medical or employment history.

Personnel files contain employment records maintained by an employer for the purpose of administering benefits, providing training, and maintaining the employment history of employees for continued employment and/or promotional opportunities.

GC section 6254(c), Civil Code section 1798, and Penal Code section 832.7 an 502 protect the confidentiality of personnel records and strictly limit their disclosure. Locked files and appropriate physical safeguards shall be established by the Personnel Officer to ensure the security and confidentiality of personnel records.

OPF CONTENTS AND RETENTION
OPF material shall be maintained no longer than the period of time required by law and in accordance with the approved departmental retention period established for the record. The Official Personnel Folder Purging Chart provides guidance for items that may be in the employee’s OPF.

PUBLIC INFORMATION
The following information is subject to review, upon request, as the items are considered public under the Public Records Act:

• Name
• Department
• Reporting unit
• Reporting location and telephone number
• Classification and specifications for the position
• Assignment (duty statement)
• Salary range (gross salary rate)
• Tenure
• Time base
• Date appointed or separated
• Rehire information
• Training received