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
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.

Modernizing PDF Techniques for Accessibility

The PDF Techniques Accessibility Summit will identify best-practices in tagging various cases in PDF documents. Questions to be addressed will likely include: the legal ways to tag a nested list, the correct way to caption multiple images, the appropriate way to organize content within headings.

Refried PDF

My hospital emailed me a medical records release form as a PDF. They told me to print it, fill it, sign it, scan it and return it to the medical records department, in that order. In 2018? To get the form via email (i.e., electronically), yet be asked to print it? Did the last 20 years just… not mean anything! So I thought I’d be clever. I’d fill it first, THEN print it. Or better yet, never print it, but sign it anyhow, and return it along with a note making the case for improving their workflow. The story continues…

The myths and legends surrounding PDF/A

A number of critics have spoken out against PDF/A, especially when the standard was first introduced. Many criticisms of the format, however, are based on misunderstandings. These are some of the most commonly encountered myths and legends:

  • PDF/A files are too large: PDF/A actually allows exceptionally small file sizes thanks to its sophisticated use of powerful compression algorithms such as JBIG2 and JPEG (and JPEG2000, from PDF/A-2 onwards). Embedded fonts can slightly increase the size of a PDF/A file. When archiving a very large number of individual, fairly similar documents, this can in some cases (such as for mass mailings) prove problematic.
  • PDF/A is not as revision-safe as TIFF: TIFF files are easier to alter than PDF and PDF/A documents. In any case, however, revision safety is not achieved through your choice of file format. It can only be achieved by using an appropriate document management or archiving system.
  • PDF/A does not allow signatures: Quite the opposite. PDF/A expressly supports embedded digital signatures. PDF/A-2 requires PADeS-standard compliance here.
  •  Links are not allowed: This claim is also false. Hyperlinks are allowed in principle. The PDF/A standard sets no requirements as to whether an external link should lead to a valid destination.
  • PDF is a proprietary format: PDF was originally developed by Adobe Systems, but since then PDF (ISO 32000) and PDF/A (ISO 19005) have become ISO standards. TIFF, on the other hand, is a specification belonging to Adobe Systems alone, and it has not achieved the status of ISO standard.
  • Scanned documents cannot be searched by text: PDF/A permits text recognition processes, meaning that even scanned PDF/A documents can be searched.
  • PDF/A is not supported by DMS systems: Any ECM system which works with PDF can also handle PDF/A in principle. Many DMS suppliers offer solutions which support PDF/A.
  • PDF/A does not allow metadata: Not at all: PDF/A specifically requires embedded standardised metadata corresponding to the modern XMP metadata standard, which was published in February 2012 as “ISO 16684-1”. XMP metadata can be directly embedded into the PDF/A document.
  • PDF/A is not globally relevant: This statement is false. Although the very first PDF/A initiatives and products did come from German-speaking countries, the ISO standard has since become a recommendation or even a legal requirement in many countries and industries.
  • PDF/A is expensive to implement: Yes and no. Implementing PDF/A solutions and training staff will incur costs at first, but these investments very often pay for themselves within months.

< previousoverviewnext >


Tags: DMS, ECM, JBIG2, JPEG2000, TIFF
Categories: PDF/A