Desktop Products:

Process Automation:

Software Development:

 
PDF to Word Converter Customers
 

PDF/A-1 Compliance Issues

For each PDF/A-1 validation issue we try to explain what it means and, if possible how to resolve it. For a more technical explanation of the issue we quote the related section of the ISO 19005-1 PDF/A Specification.

6.1
File Structure - General
6.1.2
File Header
6.1.3
File Trailer
6.1.4
Cross Reference Table
6.1.6
String Objects
6.1.7
Stream Objects
6.1.8
Indirect Objects
6.1.10
Filters
6.1.11
Embedded Files
6.1.12
Implementation Limits
6.1.13
Optional Content
6.2.2
Output Intent
6.2.3
Color Spaces - General
6.2.3.3
Uncalibrated Color Spaces
6.2.3.4
Separation and DeviceN Color Spaces
6.2.4
Images
6.2.5
Form XObjects
6.2.6
Reference XObjects
6.2.7
PostScript XObjects
6.2.8
Extended Graphics State
6.2.9
Rendering Intents
6.2.10
Content Streams
6.3.2
Font Types
6.3.3.1
General Font Issues
6.3.3.2
CIDFonts
6.3.3.3
CMaps
6.3.4
Embedded Font Programs
6.3.5
Font Subsets
6.3.6
Font Metrics
6.3.7
Character Encodings
6.3.8
Unicode Character Maps
6.4
Transparency
6.5.2
Annotation Types
6.5.3
Annotation Dictionaries
6.6.1
General Multimedia Content
6.6.2
Trigger Events
6.7
Metadata
6.7.2
Properties
6.7.3
Document Information Dictionary
6.7.5
XMP Header
6.7.8
Extension Schemas
6.7.9
Validation
6.7.11
Version and Conformance Level Identification
6.8.2.2
Mark information dictionary
6.8.3.3
Structure hierarchy
6.8.3.4
Structure types
6.9
Interactive Forms
TN0001
TechNote : Namespaces
TN0003
TechNote - Metadata
TN0008
Predefined XMP Properties
TN0008-2.2
XMP Basic Schema
TN0009
XMP Extension Schemas
TN0009-3.3
Unqualified RDF Attributes

Compliance Issue: Properties

What does this mean?

The key <<Metadata>> is required for PDF/A-1b
Invalid or non-compliant metadata

6.7.2 - ISO 19005-1 PDF/A Specification:

The document catalog dictionary of a conforming file shall contain the Metadata key. The metadata stream that forms the value of that key shall conform to XMP Specification. All metadata properties embedded in a file shall be in XMP form except for document information dictionary entries that have no XMP analogues, as defined in 6.7.4. Properties specified in XMP form shall use either the predefined schemas defined in XMP Specification 4, or extension schemas that comply with XMP Specification 4, and 6.7.8. Metadata object stream dictionaries shall not contain the Filter key.

NOTE 1: The explicit prohibition of the Filter key has the implicit effect of preserving the contents of XMP metadata streams as plain text that is visible to non-PDF aware tools.

NOTE 2: An extension schema is any XMP schema that is not defined in XMP Specification.

 


We use cookies on this site to enhance your user experience. By continuing to use this website you are giving consent to set cookies. Please see our privacy policy for more details.
©2000-2020 Solid Documents Limited - All Rights Reserved