Powered by OPF
OPF WIKI STATIC ARCHIVE
2,681 pages · 153 spaces · 776 tags · 4,025 history records · 96.2% of the original wiki recovered
Archived copy. This page was recovered from the Internet Archive snapshot of /pages/viewpage.action?pageId=68124719 taken on 2021-09-24. The original wiki at wiki.opf-labs.org is being decommissioned.

Jhove reports error for non-standard violating criterion (imbalanced page trees)

Added by Michelle Lindlar · last edited by Michelle Lindlar · on Sep 02, 2014
Title
Jhove error messages "Invalid page tree node" and "Improperly constructed page tree" are not file format errors according to the PDF 1.7 standard
Detailed description Jhove reports an error for PDF files which contain imbalances page trees. The PDF 1.7 does not formulate balanced page trees as a requirement, but only gives information on this subject matter: "However, to optimize application performance, a conforming writer can construct trees of a particular form, known as balanced trees." (section 7.7.3)
The jhove error messages leads to the objects being considered not well-formed.
Issue champion [Michelle Lindlar
Other interested parties
Any other parties who are also interested in applying Issue Solutions to their Datasets.
Possible Solution approaches Brief brainstorm of possible approaches to solving the Issue. Each approach should be described in a single sentence as part of a bulleted list. Further detail can go in a dedicated Solution page.
Solution A: the message should either be removed completley and the fact of imbalanced trees be integrated as an extracted technical metadata criterion
Solution B: the message should be turned from an "error" into an "info" message.
In either cases, it should not lead to the object being regarded not well-formed.
Context As jhove is used by many digital preservation repositories, the correct reporting of errors is essential.
Lessons Learned A central knowledge page linking jhove errors against standard information and testing them against actual standard violations would be beneficial.
Datasets Reference to the appropriate Dataset page, by hyperlink. Note that all Issues MUST be linked to at least one Dataset!
Solutions Reference to the appropriate Solution page(s), by hyperlink.