Difference between revisions of "PDF/A in PDS4 - A Primer"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
=== PDF/A-1 === | === PDF/A-1 === | ||
PDF/A-1 (ISO 19005-1) is based on PDF Version 1.4, and imposes further specifications. | PDF/A-1 (ISO 19005-1) is based on PDF Version 1.4, and imposes further specifications. | ||
| − | + | ||
| − | : | + | PDF/A-1 files '''must''' include: |
| − | : | + | * <span style="background:#F0FFFF">Embedded fonts</span> <ref name="FAQ">[http://www.npes.org/pdf/19005-1_FAQ.pdf ''19005-1 FAQ'']. (2006, July 10). PDF/A Joint Working Group. From [http://www.npes.org/programs/standardsworkroom/toolsbestpractices/pdfa.aspx NPES PDF/A FAQ]</ref> |
| − | : | + | * <span style="background:#F0FFFF">Device-independent color</span> <ref name="FAQ"/> |
| − | + | * <span style="background:#F0FFFF">XMP metadata</span> <ref name="FAQ"/> | |
| − | + | ** XMP (Extensible Metadata Platform) is an ISO-standardized metadata model created by Adobe. A PDF file contains its metadata in <code><x:xmpmeta></code> tags in XML-based syntax. PDF/A-1 specifies information to be included in this structure, using both predefined XMP schemas and industry-specific XMP extension schemas. | |
| − | + | ** From PDFlib: "PDF/A-1 requires XMP for identifying conforming files and supports custom metadata through XMP extension schemas. XMP support in PDF/A-1 is based on the XMP 2004 specification."<ref>[https://www.pdflib.com/knowledge-base/xmp-metadata/ XMP Metadata]. (n.d.). Retrieved July 07, 2017.</ref> | |
| − | : | + | PDF/A-1 files '''may not''' include: |
| − | : | + | * <span style="background:#FFE4E1">Encryption</span> <ref name="FAQ"/> |
| − | + | * <span style="background:#FFE4E1">LZW Compression</span> <ref name="FAQ"/> | |
| − | + | ** LZW is a proprietary, somewhat outmoded lossless data compression algorithm. | |
| − | + | ** Flate compression, which is more efficient and is in the public domain, is generally used instead of LZW. | |
| − | + | ** ZIP is allowed <ref name="PDFA FAQ">McAlearney, S. (n.d.). [https://www.pdfa.org/pdfa-faq/ PDF/A FAQ]. Retrieved July 11, 2017.</ref> | |
| − | + | ** JPEG is allowed,<ref name="PDFA FAQ"/> but not JPEG2000 <ref name="Dov">Isaacs, D. (2012, May 27). Re: What are the permitted compression techniques for PDF/A-1? Retrieved July 12, 2017, from https://forums.adobe.com/thread/1012639. Various discussion board replies by Adobe employee.</ref> | |
| − | : | + | *** Note that though ISO standard recommends lossless compression, lossy compression isn't prohibited.<ref name="Dov"/> |
| − | + | * <span style="background:#FFE4E1">Embedded files</span> <ref name="FAQ"/> | |
| − | + | ** This refers specifically to embedded file streams, which are used to embed contents of an external file within the body of the PDF.<ref name="EFS">Van der Knijff, V. (2013, January 9). [http://openpreservation.org/blog/2013/01/09/what-do-we-mean-embedded-files-pdf/ What do we mean by “embedded” files in PDF?] [Web log post]. Retrieved July 12, 2017.</ref> | |
| − | + | ** Not to be confused with "embedded" images <ref name="EFS"/> | |
| − | + | ** From [[Creating and Validating PDF/A-1 Documents#veraPDF|veraPDF]]'s validation rules: | |
| − | : | + | : <blockquote>A file specification dictionary, as defined in PDF 3.10.2, shall not contain the EF key [...] This key is used to encapsulate files containing arbitrary content within a PDF file. The explicit prohibition of EF key has the implicit effect of disallowing embedded files that can create external dependencies and complicate preservation efforts.<ref name="Rules">VeraPDF Consortium. (2016, December 23). [https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-1-rules PDF/A-1 validation rules]. Retrieved July 12, 2017.</ref></blockquote> |
| − | : | + | * <span style="background:#FFE4E1">External content references</span> <ref name="FAQ"/> |
| − | : | + | * <span style="background:#FFE4E1">PDF Transparency</span> <ref name="FAQ"/> |
| − | :* JavaScript <ref name=" | + | * <span style="background:#FFE4E1">Multi-media</span> <ref name="FAQ"/> |
| + | * <span style="background:#FFE4E1">JavaScript</span> <ref name="FAQ"/> | ||
| + | ** From veraPDF: "JavaScript actions permit an arbitrary executable code that has the potential to interfere with reliable and predictable rendering."<ref name="Rules"/> | ||
| + | |||
There are two levels of conformance: | There are two levels of conformance: | ||
| − | + | ; PDF/A-1b — Level B (Basic) Conformance | |
| − | + | * ''This is the minimum conformance level required for PDS4.'' | |
| − | + | * encompasses ISO 19005-1 requirements "regarding the visual appearance of electronic documents, but not their structural or semantic properties" <ref name="ISO 19005-1">''ISO 19005-1:2005(en) Document management — Electronic document file format for long-term preservation — Part 1: Use of PDF 1.4 (PDF/A-1)''. (2005). Geneva: ISO. Preview only, retrieved from https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:en.</ref> | |
| − | + | ; PDF/A-1a — Level A (Accessible) Conformance | |
| − | + | * ''This is the much preferred conformance level for PDS4.'' | |
| − | + | * encompasses all requirements of ISO 19005-1 <ref name="ISO 19005-1"/> | |
| − | + | * Not only does this level better accommodate people with disabilities, it's also recommended over Level B "for an exact text searchability, text extraction, and for the reuse of content."<ref name="PDFA FAQ"/> | |
Note that it's not immediately apparent whether a PDF file conforms to a standard. All PDF documents are defined by the same file format, after all, and thus they all use the <code>.pdf</code> filename extension. A document that is intentionally standard-compliant should, however, have XMP metadata which specifies its standard. A file which claims to conform to PDF/A-1a, for example, will include the following tags in the <code>pdfaid</code> namespace: | Note that it's not immediately apparent whether a PDF file conforms to a standard. All PDF documents are defined by the same file format, after all, and thus they all use the <code>.pdf</code> filename extension. A document that is intentionally standard-compliant should, however, have XMP metadata which specifies its standard. A file which claims to conform to PDF/A-1a, for example, will include the following tags in the <code>pdfaid</code> namespace: | ||
Revision as of 17:08, 13 July 2017
PDF/A Overview
The Portable Document Format (PDF) is a broad, complex file format. The International Organization for Standardization (ISO) has created various PDF subset standards which are specialized for different uses. The PDF/A standard (ISO 19005) is designed for long-term preservation. There are three iterations of the PDF/A standard so far: PDF/A-1, PDF/A-2, and PDF/A-3. Versions of PDF/A retain backward but not forward compatibility (e.g., a document that complies with PDF/A-2 will also conform to PDF/A-3, but not necessarily to PDF/A-1). PDS4 requires compliance specifically to the first version, PDF/A-1.[1]
PDF/A-1
PDF/A-1 (ISO 19005-1) is based on PDF Version 1.4, and imposes further specifications.
PDF/A-1 files must include:
- Embedded fonts [2]
- Device-independent color [2]
- XMP metadata [2]
- XMP (Extensible Metadata Platform) is an ISO-standardized metadata model created by Adobe. A PDF file contains its metadata in
<x:xmpmeta>tags in XML-based syntax. PDF/A-1 specifies information to be included in this structure, using both predefined XMP schemas and industry-specific XMP extension schemas. - From PDFlib: "PDF/A-1 requires XMP for identifying conforming files and supports custom metadata through XMP extension schemas. XMP support in PDF/A-1 is based on the XMP 2004 specification."[3]
- XMP (Extensible Metadata Platform) is an ISO-standardized metadata model created by Adobe. A PDF file contains its metadata in
PDF/A-1 files may not include:
- Encryption [2]
- LZW Compression [2]
- LZW is a proprietary, somewhat outmoded lossless data compression algorithm.
- Flate compression, which is more efficient and is in the public domain, is generally used instead of LZW.
- ZIP is allowed [4]
- JPEG is allowed,[4] but not JPEG2000 [5]
- Note that though ISO standard recommends lossless compression, lossy compression isn't prohibited.[5]
- Embedded files [2]
A file specification dictionary, as defined in PDF 3.10.2, shall not contain the EF key [...] This key is used to encapsulate files containing arbitrary content within a PDF file. The explicit prohibition of EF key has the implicit effect of disallowing embedded files that can create external dependencies and complicate preservation efforts.[7]
- External content references [2]
- PDF Transparency [2]
- Multi-media [2]
- JavaScript [2]
- From veraPDF: "JavaScript actions permit an arbitrary executable code that has the potential to interfere with reliable and predictable rendering."[7]
There are two levels of conformance:
- PDF/A-1b — Level B (Basic) Conformance
- This is the minimum conformance level required for PDS4.
- encompasses ISO 19005-1 requirements "regarding the visual appearance of electronic documents, but not their structural or semantic properties" [8]
- PDF/A-1a — Level A (Accessible) Conformance
- This is the much preferred conformance level for PDS4.
- encompasses all requirements of ISO 19005-1 [8]
- Not only does this level better accommodate people with disabilities, it's also recommended over Level B "for an exact text searchability, text extraction, and for the reuse of content."[4]
Note that it's not immediately apparent whether a PDF file conforms to a standard. All PDF documents are defined by the same file format, after all, and thus they all use the .pdf filename extension. A document that is intentionally standard-compliant should, however, have XMP metadata which specifies its standard. A file which claims to conform to PDF/A-1a, for example, will include the following tags in the pdfaid namespace:
<pdfaid:part>1</pdfaid:part> <pdfaid:conformance>A</pdfaid:conformance> |
A PDF reader may make note of this designation. Adobe Acrobat, in particular, displays a blue banner which states that the file "claims compliance with the PDF/A standard." Regardless, this claim of compliance must be validated. A non-compliant document may incorrectly have metadata indicating compliance; conversely, compliance metadata may be missing from an otherwise compliant document.
See Also
External Links
- General
- Backend
References
- ↑ Policy on Formats for PDS4 Data and Documentation. (2014, June 30). The Planetary Data System. From PDS Policies
- ↑ 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 19005-1 FAQ. (2006, July 10). PDF/A Joint Working Group. From NPES PDF/A FAQ
- ↑ XMP Metadata. (n.d.). Retrieved July 07, 2017.
- ↑ 4.0 4.1 4.2 McAlearney, S. (n.d.). PDF/A FAQ. Retrieved July 11, 2017.
- ↑ 5.0 5.1 Isaacs, D. (2012, May 27). Re: What are the permitted compression techniques for PDF/A-1? Retrieved July 12, 2017, from https://forums.adobe.com/thread/1012639. Various discussion board replies by Adobe employee.
- ↑ 6.0 6.1 Van der Knijff, V. (2013, January 9). What do we mean by “embedded” files in PDF? [Web log post]. Retrieved July 12, 2017.
- ↑ 7.0 7.1 VeraPDF Consortium. (2016, December 23). PDF/A-1 validation rules. Retrieved July 12, 2017.
- ↑ 8.0 8.1 ISO 19005-1:2005(en) Document management — Electronic document file format for long-term preservation — Part 1: Use of PDF 1.4 (PDF/A-1). (2005). Geneva: ISO. Preview only, retrieved from https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:en.
