PDF Association logo.

Facebook
Twitter
YOUTUBE
LINKEDIN
XING
About the contributor
PDF Association

Mission Statement: To promote Open Standards-based electronic document implementations using PDF technology through education, expertise and shared experience for stakeholders worldwide.
More contributions
Save-The-Date: PDF Day France, Toulouse, April 4, 2019

PDF Day France will be the first French-speaking event of the PDF Association, organised by our member ORPALIS. It will take place in Toulouse which is the home ground of Airbus and we are very happy that Airbus will present a case study around its usage of PDF in their document management environment!

Electronic Document Conference: Call for Papers

Prospective presenters at the Electronic Document Conference 2019 are invited to submit high-quality original proposals for 25-minute presentations on subjects of interest to developers and technical product managers concerned with electronic document implementations.

Have we passed ‘peak PDF’?

How do we gain insight into how users’ views of documents are shifting? Google Trends is an increasingly interesting source of high-level marketplace data. By aggregating Google’s search data over time, reporting a term’s popularity as compared with all other searches.

Participating in the PDF Techniques Accessibility Summit

The PDF Techniques Accessibility Summit’s objective is to establish a broad-based understanding of how PDF files should be tagged for accessibilty. It’s an opportunity to focus on establishing a common set of examples of accessible PDF content, and identify best-practice when tagging difficult cases.

Members supporting PDF features!

The typical adoption curve for PDF technologies until approximately 2007 tended to track with that of the original PDF developer. Since then the marketplace has shifted; it’s no longer clear that Adobe drivesPDF feature support worldwide. Accordingly, we are happy to report that adoption of PDF 2.0 continues apace, with new vendors announcing their support every month.

Isartor Test Suite

The Isartor test suite is named after the location of the first meeting of the Technical Working Group, a medieval gate towards the river Isar in the center of Munich/Germany. This test suite comprises a set of files which can be used to check the conformance of software regarding the PDF/A-1 standard. More precisely, the Isartor test suite can be used to “validate the validators”: It deliberately violates the requirements of PDF/A-1 in a systematic way in order to check whether PDF/A-1 validation software actually finds the violations.

Basic Principles

The Isartor test suite has been constructed according to the following basic principles:

  • Atomic: A test file attempts to examine a particular aspect of the standard. Wherever possible test files avoid to touch more than one aspect of the standard.
  • Complete: The Isartor test suite provides full coverage of all requirements in the PDF/A-1 standard.
  • Self-documenting: The test files contain intrinsic information about the expected result of performing the test.
  • Traceable: Each test is based on a specific clause in PDF/A-1 which can easily be identified.
  • Reproducible: All test files (with only a few exceptions) have been created programmatically with a documented change history. This creation process support reproducibility.

Through a rigid quality assurance and testing process a lot of effort has been spent to make sure that all test files adhere to these basic principles.

What the Test Suite checks

The Isartor test suite for PDF/A-1b deliberately violates each requirement of the PDF/A-1b standard in order to check whether validation software detects all possible kinds of violation of the standard requirements, and whether it provides appropriate explanation for rejected nonconforming documents.

A PDF/A validator which completely passes the Isartor test suite is known to implement all required checks.

For the sake of simplicity, only a single aspect of the standard is violated at a time. However, in a few cases this is not possible because of interdependencies among multiple aspects of the standard.

The test requirements (assertions) are the inverse of requirements in the standard. For example, PDF/A-1 mandates that fonts be embedded, so the test suite contains several documents where the fonts are deliberately not embedded. PDF/A validators must report this standard violation in order to pass the test.

Who created the Test Suite?

The Isartor test suite is a project of the PDF/A Competence Center, and was developed by its Technical Working Group (TWG). Members of the TWG are volunteers from member companies of the PDF Association. All companies who send TWG delegates are software vendors. Individual TWG members are experts in the field of PDF and/or standardization. Most members are involved in the design, development, and testing of software for creating, processing, or validating PDF/A documents. Several TWG members are also members of TC 171 SC2 WG 5, the ISO committee which defined the PDF/A family of standards.

Design and structure of the Isartor test suite have been devised by the TWG. Test files have been created by a core group after thoroughly discussing the respective criteria in the standard. All test files have been formally reviewed by at least two other members of the TWG.

Acknowledgements

Isartor test suite files have been contributed by the following founding members of the PDF/A Competence Center:
PDF Tools AG
PDFlib GmbH
callas software GmbH

Extensive reviews of the test suite have been performed by the above companies plus the following:
intarsys consulting GmbH
SEAL Systems AG

Download the Isartor Test Suite Download PDF icon


Tags: Isartor, conformance, test suite, validate
Categories: PDF/A