PDF/A: Мұрағаттау үшін ISO стандартындалған формат

ISO standardized version of PDF for archives

PDF/A is an ISO standardized version of the Portable Document Format (PDF) specialized for use in the archiving and long term preservation of electronic documents. PDF/A differs from PDF by prohibiting features unsuitable for long term archiving, such as font linking (as opposed to font embedding) and encryption. The ISO requirements for PDF/A file viewers include color management guidelines, support for embedded fonts, and a user interface for reading embedded annotations.

+ ISO 19005 – Document management – Electronic document file format for long term preservation (PDF/A) Abbr. (Abbreviation) Subtitle Published Standard Based on Ref. PDF/A 1 Part 1: Use of PDF 1.4 2005 09 28 ISO 19005 1 PDF 1.4 (Adobe Systems, PDF Reference, third edition) PDF/A 2 Part 2: Use of ISO 32000 1 2011 06 20 ISO 19005 2 PDF 1.7 (ISO 32000 1:2008) PDF/A 3 Part 3: Use of ISO 32000 1 with support for embedded files 2012 10 15 ISO 19005 3 PDF 1.7 (ISO 32000 1:2008) PDF/A 4 Part 4: Use of ISO 32000 2 2020 11 ISO 19005 4 PDF 2.0 (ISO 32000 2:2020)

PDF is a standard for encoding documents in an "as printed" form that is portable between systems. However, the suitability of a PDF file for archival preservation depends on options chosen when the PDF is created: most notably, whether to embed the necessary fonts for rendering the document; whether to use encryption; and whether to preserve additional information from the original document beyond what is needed to print it. PDF/A was originally a new joint activity between the Association for Suppliers of Printing, Publishing and Converting Technologies (NPES) and the Association for Information and Image Management AIIM in conjunction with Adobe to develop an international standard defining the use of the Portable Document Format (PDF) for archiving documents. The goal was to address the growing need to electronically archive documents in a way that would ensure preservation of their contents over an extended period of time and ensure that those documents would be able to be retrieved and rendered with a consistent and predictable result in the future. This need exists in a wide variety of government, industry and academic areas worldwide, including legal systems, libraries, newspapers, and regulated industries.

Part 4 of the standard, based on PDF 2.0, was published in late 2020.

Archives sometimes request from their users to submit PDF/A Files. They thus provide their users with information how to convert their files to PDF/A. There are several methods using standard software that differ in computation time as well as preservation of links, equations, vectorgraphs and special characters. Converting a simple PDF (up to version 1.4) into a PDF/A 2 usually works as expected, except for problems with glyphs. According to the PDF Association, "Problems can occur before and/or during the generation of PDFs. A PDF/A file can be formally correct yet still have incorrect glyphs. Only a careful visual check can uncover this problem. Because generation problems also affect Unicode mapping, the problem attracts the attention when a visual check is carried out on the extracted text. In PDF/A, text/font usage is specified uniquely enough to ensure that it cannot be incorrect. If viewers or printers do not offer complete support for encoding systems, this can result in problems with regard to PDF/A." Meaning that for a document to be completely compliant with the standard, it will be correct internally, while the system used for viewing or printing the document may produce undesired results. A document produced with optical character recognition (OCR) conversion into PDF/A 2 or PDF/A 3 doesn't support the notdefglyph flag. Therefore, this type of conversion can result in unrendered content. PDF/A standard documents can be created with the following software: SoftMaker Office 2021, MS Word 2010 and newer, Adobe Acrobat Distiller, PDF Creator, OpenOffice or LibreOffice since release 3.0, LaTeX with pdfx or pdfTeX addons, or by using a virtual PDF printer (Adobe Acrobat Pro, PDF24, FreePDF + Ghostscript).

A PDF/A document can be identified as such through PDF/A specific metadata located in the "http://www. aiim. org/pdfa/ns/id/" namespace. This metadata represents a claim of conformance; in itself it does not ensure conformance:

a PDF document can be PDF/A compliant, except for its lack of PDF/A metadata. This may happen for instance with documents that were generated before the definition of the PDF/A standard, by authors aware of features that present long term preservation issues. a PDF document can be identified as PDF/A, but may incorrectly contain PDF features not allowed in PDF/A; hence, documents which claim to be PDF/A compliant should be tested for PDF/A compliance.

Validation of PDF/A documents is attempted to reveal whether a produced file really is a PDF/A file or not. Unfortunately, PDF/A validators quite often disagree, since the interpretation of the PDF/A standards is not always clear.

Industry collaboration in the original PDF/A Competence Center led to the development of the Isartor Test Suite in 2007 and 2008. The test suite consists of 204 PDF files intentionally constructed to systematically fail each of the requirements for PDF/A 1b conformance, allowing developers to test the ability of their software to validate against the standard's most basic level of conformance. By mid 2009 the test suite had already made an appreciable difference in the general quality of PDF/A validation software.

The veraPDF consortium, led by the Open Preservation Foundation and the PDF Association, was created in response to the EU Commission's PREFORMA challenge to develop an open source validator for the PDF/A format. The PDF Association launched the PDF Validation Technical Working Group in November 2014 to articulate a plan for developing an industry supported PDF/A validator. The veraPDF consortium subsequently won phase 2 of the PREFORMA contract in April 2015. Development continued throughout 2016, with Phase 2 completed on schedule by December 2016. The Phase 3 testing and acceptance period concluded in July, 2017. veraPDF now covers all parts (1, 2 and 3) and conformance levels (a, b, u) of PDF/A. veraPDF is available for installation on Windows, macOS, or Linux using a PDFBox based or "Greenfields" PDF parser.

A PDF/A document must embed all fonts in use; accordingly, a PDF/A file will often be larger than an equivalent PDF file that does not include embedded fonts. The use of transparency is forbidden in PDF/A 1. The majority of PDF generation tools that allow for PDF/A document compliance, such as the PDF export in OpenOffice. org or PDF export tool in Microsoft Office 2007 suites, will also make any transparent images in a given document non transparent. That restriction was removed in PDF/A 2. The PDF Association had addressed various misconceptions regarding PDF/A in its publication "PDF/A in a Nutshell 2.0".