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: Extension Schemas

6.7.8 - ISO 19005-1 PDF/A Specification:

All extension schemas used in a conforming file shall have their descriptions embedded within that file in the metadata stream defined by 6.7.2. These descriptions shall be specified using the PDF/A extension schema description schema defined in this clause.

NOTE 1: An extension schema is any XMP schema that is not defined in XMP Specification. The extension schema description schema defined in Table 2 uses the namespace URI <http://www.aiim.org/pdfa/ns/schema>. The required schema namespace prefix is pdfaSchema.

NOTE 2: According to the W3C XML Namespace recommendation [18], namespace URI’s are for identification purposes only and are not required to be actionable links. None of the namespace URI’s defined for XMP extension schemas in this part of ISO 19005 is an actionable link. Attempting to dereference or follow any of these links will not result in a valid web page.

Table 2 — PDF/A extension schema description schema

PropertyValue typeCategoryDescription
pdfaSchema:schemaTextExternalOptional description of schema
pdfaSchema:namespaceURIURIExternalSchema namespace URI
pdfaSchema:prefixTextExternalPreferred schema namespace prefix
pdfaSchema:propertyseq PropertyInternalDescription of schema properties
pdfaSchema:valueTypeseq ValueTypeInternalDescription of schema-specific value types


The Property type defined in Table 3 is an XMP structure containing the description of a schema property. The field namespace URI is . The required field namespace prefix is pdfaProperty.

Table 3 — PDF/A property type schema
Field nameValue typeDescription
pdfaProperty:nameTextProperty name
pdfaProperty:valueTypeOpen Choice of TextValue type of the property, drawn from XMP Specification 4, or an embedded PDF/A value type extension schema
pdfaProperty:categoryClosed Choice of TextProperty category: internal or external
pdfaProperty:descriptionTextDescription of the property


The preferred values for pdfaProperty:valueType should be the non-deprecated property value types defined in XMP Specification 2004, 4. Array types shall be preceded by their container type: alt, bag or seq, separated from the base type by a single white-space character.

The ValueType type defined in Table 4 is an XMP structure containing the description of all property value types used by embedded extension schemas that are not defined in XMP Specification 4. The field namespace URI is <http://www.aiim.org/pdfa/ns/type>. The required field namespace prefix is pdfaType.

Table 4 — PDF/A value type schema
Field nameValue typeDescription
pdfaType:typeTextProperty value type name
pdfaType:namespaceURIURIProperty value type field namespace URI
pdfaType:prefixTextPreferred value type field namespace prefix
pdfaType:descriptionTextDescription of the property value type
pdfaType:fieldseq FieldOptional description of the structured fields


The Field type defined in Table 5 is an XMP structure containing the description of a property value type field. The field namespace URI is . The required field namespace prefix is pdfaField.

Table 5 — PDF/A field schema
Field nameValue typeDescription
pdfaField:nameTextField name
pdfaField:valueTypeOpen Choice of TextField value type, drawn from XMP Specification 2004, 4, or an embedded PDF/A value type extension schema
pdfaField:descriptionTextField description

 


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-2024 Solid Documents Limited - All Rights Reserved