-
Notifications
You must be signed in to change notification settings - Fork 16
PDFA Parts 2 and 3 rules
The file header shall begin at byte zero and shall consist of "%PDF-1.n" followed by a single EOL marker, where 'n' is a single digit number between 0 (30h) and 7 (37h)
File header starts at non-zero offset or does not match the pattern %PDF-1.n, where 'n' is a single digit number between 0 and 7.
- Object type:
CosDocument - Test condition:
headerOffset == 0 && /^%PDF-1\.[0-7]$/.test(header) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The aforementioned EOL marker shall be immediately followed by a % (25h) character followed by at least four bytes, each of whose encoded byte values shall have a decimal value greater than 127.
Binary comment in the file header is missing or does not start with 4 bytes with byte values above 127.
The presence of encoded character byte values greater than decimal 127 near the beginning of a file is used by various software tools and protocols to classify the file as containing 8-bit binary data that should be preserved during processing.
- Object type:
CosDocument - Test condition:
headerByte1 > 127 && headerByte2 > 127 && headerByte3 > 127 && headerByte4 > 127 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The file trailer dictionary shall contain the ID keyword whose value shall be File Identifiers as defined in ISO 32000-1:2008, 14.4
Missing or empty ID in the document trailer.
Processing systems and documents may contain references to PDF files. Simply storing a file name, however, even in a platform-independent format, does not guarantee that the file can be found. Even if the file still exists and its name has not been changed, different server software applications may identify it in different ways. For example, servers running on DOS platforms must convert all file names to 8 characters and a 3-character extension; different servers may use different strategies for converting longer file names to this format.
External file references can be made more reliable by including a file identifier in the file itself and using it in addition to the normal platform-based file designation. File identifiers are defined by the optional ID entry in a PDF file’s trailer dictionary. The value of this entry is an array of two strings. The first string is a permanent identifier based on the contents of the file at the time it was originally created, and does not change when the file is incrementally updated. The second string is a changing identifier based on the file's contents at the time it was last updated. When a file is first written, both identifiers are set to the same value. If both identifiers match when a file reference is resolved, it is very likely that the correct file has been found; if only the first identifier matches, then a different version of the correct file has been found.
- Object type:
CosDocument - Test condition:
lastID != null && lastID.length() > 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 14.4
The keyword Encrypt shall not be used in the trailer dictionary.
Encrypt keyword is present in the trailer dictionary.
The explicit prohibition of the Encrypt keyword has the implicit effect of disallowing encryption and password-protected access permissions.
- Object type:
CosTrailer - Test condition:
isEncrypted != true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
No data can follow the last end-of-file marker except a single optional end-of-line marker as described in ISO 32000-1:2008, 7.5.5.
Data is present after the last end-of-file marker.
The trailer of a PDF file enables an application reading the file to quickly find the cross-reference table and certain special objects. Applications should read a PDF file from its end. The last line of the file contains only the end-of-file marker, %%EOF. Some PDF viewers require only that the %%EOF marker appear somewhere within the last 1024 bytes of the file. But having any data after %%EOF marker introduces risks that the PDF document might not be processed correctly.
- Object type:
CosDocument - Test condition:
postEOFDataSize == 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 7.5.5
The xref keyword and the cross-reference subsection header shall be separated by a single EOL marker.
Extra spacings or missing EOL characters after the 'xref' keyword in the cross reference table.
The cross-reference table contains information that permits random access to indirect objects within the file, so that the entire file need not be read to locate any particular object. The table contains a one-line entry for each indirect object, specifying the location of that object within the body of the file.
The cross-reference table is the only part of a PDF file with a fixed format; this permits entries in the table to be accessed randomly. Any variations in this format, including unnecessary EOL markers may result in incorrect parsing of the cross-reference table and, thus, errors in reading the PDF document.
- Object type:
CosXRef - Test condition:
xrefEOLMarkersComplyPDFA - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Hexadecimal strings shall contain an even number of non-white-space characters.
A hexadecimal string contains odd number of non-white-space characters.
Strings in PDF documents may be written as a literal byte sequence or as a hexadecimal string; the latter is useful for including arbitrary binary data in a PDF file. A hexadecimal string is written as a sequence of hexadecimal digits (0–9 and either A–F or a–f) enclosed within angle brackets (< and >):
<4E6F762073686D6F7A206B6120706F702E>
Each pair of hexadecimal digits defines one byte of the string. White-space characters (such as space, tab, carriage return, line feed, and form feed) are ignored.
White-space characters are defined as NULL (00h), TAB (09h), LINE FEED (0Ah), FORM FEED (0Ch), CARRIAGE RETURN (0Dh), SPACE (20h). They may appear within hexadecimal strings for formatting purposes:
<4E6F 7620 7368 6D6F
7A20 6B61 2070 6F70>
- Object type:
CosString - Test condition:
(isHex != true) || hexCount % 2 == 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A hexadecimal string is written as a sequence of hexadecimal digits (0-9 and either A-F or a-f).
Hexadecimal string contains non-white-space characters outside the range 0 to 9, A to F or a to f.
- Object type:
CosString - Test condition:
(isHex != true) || containsOnlyHex == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The value of the Length key specified in the stream dictionary shall match the number of bytes in the file following the LINE FEED (0Ah) character after the stream keyword and preceding the EOL marker before the endstream keyword.
Actual length of the stream does not match the value of the Length key in the Stream dictionary.
Every stream dictionary has a Length entry that indicates how many bytes of the PDF file are used for the stream's data. (If the stream has a filter, Length is the number of bytes of encoded data.) In addition, most filters are defined so that the data is self-limiting; that is, they use an encoding scheme in which an explicit end-of-data (EOD) marker delimits the extent of the data. Finally, streams are used to represent many objects from whose attributes a length can be inferred. All of these constraints must be consistent.
- Object type:
CosStream - Test condition:
Length == realLength - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The stream keyword shall be followed either by a CARRIAGE RETURN (0Dh) and LINE FEED (0Ah) character sequence or by a single LINE FEED (0Ah) character. The endstream keyword shall be preceded by an EOL marker.
Extra spacings or missing EOL characters around keywords 'stream' and 'endstream'.
These requirements remove potential ambiguity regarding the ending of stream content.
- Object type:
CosStream - Test condition:
streamKeywordCRLFCompliant == true && endstreamKeywordEOLCompliant == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A stream dictionary shall not contain the F, FFilter, or FDecodeParms keys.
A stream object dictionary contains one of the F, FFilter, or FDecodeParms keys.
These keys are used to point to document content external to the file. The explicit prohibition of these keys has the implicit effect of disallowing external content that can create external dependencies and complicate preservation efforts.
- Object type:
CosStream - Test condition:
F == null && FFilter == null && FDecodeParms == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
All standard stream filters listed in ISO 32000-1:2008, 7.4, Table 6 may be used, with the exception of LZWDecode. In addition, the Crypt filter shall not be used unless the value of the Name key in the decode parameters dictionary is Identity. Filters that are not listed in ISO 32000-1:2008, 7.4, Table 6 shall not be used.
Unknown or not permitted Stream filter is used.
The use of the LZW compression algorithm has been subject to intellectual property constraints. The Crypt filter is used to apply encryption and access control to the file.
- Object type:
CosFilter - Test condition:
internalRepresentation == "ASCIIHexDecode" || internalRepresentation == "ASCII85Decode" || internalRepresentation == "FlateDecode" || internalRepresentation == "RunLengthDecode" || internalRepresentation == "CCITTFaxDecode" || internalRepresentation == "JBIG2Decode" || internalRepresentation == "DCTDecode" || internalRepresentation == "JPXDecode" || (internalRepresentation == "Crypt" && decodeParms == "Identity") - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Font names, names of colourants in Separation and DeviceN colour spaces, and structure type names, after expansion of character sequences escaped with a NUMBER SIGN (23h), if any, shall be valid UTF-8 character sequences.
The name object does not represent a correct UTF-8 character sequence.
As stated above, name objects shall be treated as atomic within a PDF file. Ordinarily, the bytes making up the name are never treated as text to be presented to a human user or to an application external to a conforming reader. However, occasionally the need arises to treat a name object as text, such as one that represents a font name, a colorant name in a separation or DeviceN colour space, or a structure type.
In such situations, the sequence of bytes (after expansion of NUMBER SIGN sequences, if any) should be interpreted according to UTF-8, a variable-length byte-encoded representation of Unicode in which the printable ASCII characters have the same representations as in ASCII. This enables a name object to represent text virtually in any natural language, subject to the implementation limit on the length of a name.
- Object type:
CosUnicodeName - Test condition:
isValidUtf8 == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 7.3.5
The object number and generation number shall be separated by a single white-space character. The generation number and obj keyword shall be separated by a single white-space character. The object number and endobj keyword shall each be preceded by an EOL marker. The obj and endobj keywords shall each be followed by an EOL marker.
Extra spacings or missing EOL characters around indirect object/generation number or keywords 'obj' and 'endobj'.
The definition of an indirect object in a PDF file consists of its object number and generation number, followed by the value of the object itself bracketed between the keywords "obj" and "endobj". The requirements of this rule guarantee that the definition of an indirect object can be parsed unambiguously.
- Object type:
CosIndirect - Test condition:
spacingCompliesPDFA - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The value of the F key in the Inline Image dictionary shall not be LZW, LZWDecode, Crypt, a value not listed in ISO 32000-1:2008, Table 6, or an array containing any such value.
An inline image uses LZW, Crypt or one of the unknown filters.
Inline images are defined directly within the content stream in which it will be painted, rather than as separate objects. The use of LZW, Crypt and other non-standard compression methods is also not permitted for such images.
- Object type:
CosIIFilter - Test condition:
internalRepresentation == "ASCIIHexDecode" || internalRepresentation == "ASCII85Decode" || internalRepresentation == "FlateDecode" || internalRepresentation == "RunLengthDecode" || internalRepresentation == "CCITTFaxDecode" || internalRepresentation == "DCTDecode" || internalRepresentation == "AHx" || internalRepresentation == "A85" || internalRepresentation == "Fl" || internalRepresentation == "RL" || internalRepresentation == "CCF" || internalRepresentation == "DCT" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
No keys other than UR3 and DocMDP shall be present in a permissions dictionary (ISO 32000-1:2008, 12.8.4, Table 258).
The document permissions dictionary contains keys other than UR3 and DocMDP.
- Object type:
PDPerms - Test condition:
entries.split('&').filter(elem => elem != 'UR3' && elem != 'DocMDP').length == 0 || entries == '' - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 12.8.4
If DocMDP is present, then the Signature References dictionary (ISO 32000-1:2008, 12.8.1, Table 253) shall not contain the keys DigestLocation, DigestMethod, and DigestValue.
The Signature References dictionary contains one of the keys DigestLocation, DigestMethod, or DigestValue in presence of DocMDP entry in the permissions dictionary.
These restrictions are present to ensure that functionality such as obsolete versions of the "User Rights" dictionary do not appear in a document conforming to ISO 19005-2 and ISO 19005-3.
- Object type:
PDSigRef - Test condition:
permsContainDocMDP == false || entries.split('&').filter(elem => elem == 'DigestLocation' || elem == 'DigestMethod' || elem == 'DigestValue').length == 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 12.8.1
A conforming file shall not contain any integer greater than 2147483647. A conforming file shall not contain any integer less than -2147483648.
Integer value is out of range.
- Object type:
CosInteger - Test condition:
(intValue <= 2147483647) && (intValue >= -2147483648) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any real number outside the range of +/-3.403 x 10^38.
Real value is out of range.
- Object type:
CosReal - Test condition:
(realValue >= -3.403e+38) && (realValue <= 3.403e+38) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any string longer than 32767 bytes.
Maximum length of a String (32767) is exceeded.
- Object type:
CosString - Test condition:
value.length() < 32768 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any name longer than 127 bytes.
Maximum length of a Name (127) is exceeded.
- Object type:
CosName - Test condition:
internalRepresentation.length() <= 127 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any real number closer to zero than +/-1.175 x 10^(-38).
Non-zero real value is too close to 0.0.
- Object type:
CosReal - Test condition:
realValue == 0.0 || (realValue <= -1.175e-38) || (realValue >= 1.175e-38) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain more than 8388607 indirect objects.
Maximum number of indirect objects (8,388,607) in a PDF file is exceeded.
- Object type:
CosDocument - Test condition:
nrIndirects <= 8388607 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not nest q/Q pairs by more than 28 nesting levels.
Maximum depth of graphics state nesting (q and Q operators) is exceeded.
- Object type:
Op_q_gsave - Test condition:
nestingLevel <= 28 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain a DeviceN colour space with more than 32 colourants.
Maximum number of DeviceN components (32) is exceeded
- Object type:
PDDeviceN - Test condition:
nrComponents <= 32 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain a CID value greater than 65535.
Maximum value of a CID (65535) is exceeded.
- Object type:
CMapFile - Test condition:
maximalCID <= 65535 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The size of any of the page boundaries described in ISO 32000-1:2008, 14.11.2 shall not be less than 3 units in either direction, nor shall it be greater than 14 400 units in either direction.
One of the page boundaries is out of range (3-14400) in one of the directions.
- Object type:
CosBBox - Test condition:
Math.abs(top - bottom) >= 3 && Math.abs(top - bottom) <= 14400 && Math.abs(right - left) >= 3 && Math.abs(right - left) <= 14400 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Content streams shall not contain any operators not defined in ISO 32000-1 even if such operators are bracketed by the BX/EX compatibility operators.
A content stream contains an operator not defined in ISO 32000-1.
Ordinarily, when a viewer application encounters an operator in a content stream that it does not recognize, an error will occur. A pair of compatibility operators, BX and EX, modify this behavior. These operators must occur in pairs and may be nested. They bracket a compatibility section, a portion of a content stream within which unrecognized operators are to be ignored without error. This mechanism enables a PDF document to use operators defined in newer versions of PDF without sacrificing compatibility with older viewers.
However, as the use of undefined operators may still result in error for some PDF processors, their use is not permitted in PDF/A-compliant documents, even if they are bracketed by BX/EX compatibility operators.
In earlier versions of the PDF format a PostScript operator "PS" was defined. As this operator is not defined in PDF Reference its use is implicitly prohibited by PDF/A specification.
- Object type:
Op_Undefined - Test condition:
false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A content stream that references other objects, such as images and fonts that are necessary to fully render or process the stream, shall have an explicitly associated Resources dictionary as described in ISO 32000-1:2008, 7.8.3.
A content stream refers to resources not defined in an explicitly associated Resources dictionary
- Object type:
PDContentStream - Test condition:
inheritedResourceNames == '' - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 7.8.3
The profile stream that is the value of the DestOutputProfile key shall either be an output profile (Device Class = "prtr") or a monitor profile (Device Class = "mntr"). The profiles shall have a colour space of either "GRAY", "RGB", or "CMYK".
The embedded PDF/A Output Intent colour profile has invalid header
- Object type:
ICCOutputProfile - Test condition:
(deviceClass == "prtr" || deviceClass == "mntr") && (colorSpace == "RGB " || colorSpace == "CMYK" || colorSpace == "GRAY") && version < 5.0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 14.11.5
If a file's OutputIntents array contains more than one entry, as might be the case where a file is compliant with this part of ISO 19005 and at the same time with PDF/X-4 or PDF/E-1, then all entries that contain a DestOutputProfile key shall have as the value of that key the same indirect object, which shall be a valid ICC profile stream.
File's OutputIntents array contains output intent dictionaries with non-matching destination output profiles.
A PDF document may conform to several PDF standards at the same time, such as PDF/X, PDF/E or PDF/UA. Each of these standards relies on the presence of the OutputIntent color profile and has to identify such profile via a standard-specific subtype entry (S key in the OutputIntent dictionary). For example, the value of this key is "GTS_PDFA1" for the PDF/A standards, and is "GTS_PDFX" for PDF/X standards.
The requirement for all output intent dictionaries to share the same output ICC profile minimizes risks that a wrong ICC output profile is used for rendering the PDF document.
- Object type:
OutputIntents - Test condition:
sameOutputProfileIndirect == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The DestOutputProfileRef key, as defined in ISO 15930-7:2010, Annex A, shall not be present in any PDF/X OutputIntent.
The PDF/X output intent dictionary contains entry DestOutputProfileRef, which is not permitted by PDF/A-2 and PDF/A-3 specifications.
- Object type:
PDOutputIntent - Test condition:
S != 'GTS_PDFX' || containsDestOutputProfileRef == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO15930-7:2010, Annex A
The profile that forms the stream of an ICCBased colour space shall conform to ICC.1:1998-09, ICC.1:2001-12, ICC.1:2003-09 or ISO 15076-1.
The embedded ICC profile is either invalid or does not satisfy PDF 1.7 requirements.
ICC profiles can be used in PDF documents to identify the source color spaces. Similar to the requirements for the ICC output profile (see Rule 6.2.3-1), the embedded ICC input profile shall satisfy a number of additional requirements of PDF 1.7 Specification. These requirements cover the device class of the ICC profile, its connection color space and the version of the ICC standard the input profile is based on.
- Object type:
ICCInputProfile - Test condition:
(deviceClass == "prtr" || deviceClass == "mntr" || deviceClass == "scnr" || deviceClass == "spac") && (colorSpace == "RGB " || colorSpace == "CMYK" || colorSpace == "GRAY" || colorSpace == "Lab ") && version < 5.0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 8.6.5.5
Overprint mode (as set by the OPM value in an ExtGState dictionary) shall not be one (1) when an ICCBased CMYK colour space is used for stroke and overprinting for stroke is set to true, or when ICCBased CMYK colour space is used for fill and overprinting for fill is set to true, or both.
Overprint mode (OPM) is set to 1 when an ICCBased CMYK colour space is used with enabled overprinting.
This prohibition avoids unpredictable overprinting behaviour when overprint mode is 1 if implicit colour conversion is applied as described in ISO 32000-1:2008, 8.6.7.
- Object type:
PDICCBasedCMYK - Test condition:
overprintFlag == false || OPM == 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 8.6.7
DeviceRGB shall only be used if a device independent DefaultRGB colour space has been set when the DeviceRGB colour space is used, or if the file has a PDF/A OutputIntent that contains an RGB destination profile.
DeviceRGB colour space is used without RGB output intent profile
A conforming PDF/A document may use either DeviceRGB or DeviceCMYK colour spaces, but shall not use both. In an uncalibrated colour space is used in a file then that file shall contain an PDF/A OutputIntent specifying the output ICC profile with matching colour space.
When rendering colours specified in a device-dependent colour space a conforming reader shall use file's PDF/A OutputIntent dictionary as the source colour space. This guarantees unambiguous and device-independent representation of all colours used in the conforming PDF/A document.
- Object type:
PDDeviceRGB - Test condition:
gOutputCS != null && gOutputCS == "RGB " - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
DeviceCMYK shall only be used if a device independent DefaultCMYK colour space has been set or if a DeviceN-based DefaultCMYK colour space has been set when the DeviceCMYK colour space is used or the file has a PDF/A OutputIntent that contains a CMYK destination profile.
DeviceCMYK colour space is used without CMYK output intent profile
A conforming PDF/A document may use either DeviceRGB or DeviceCMYK colour spaces, but shall not use both. In an uncalibrated colour space is used in a file then that file shall contain an PDF/A OutputIntent specifying the output ICC profile with matching colour space.
When rendering colours specified in a device-dependent colour space a conforming reader shall use file's PDF/A OutputIntent dictionary as the source colour space. This guarantees unambiguous and device-independent representation of all colours used in the conforming PDF/A document.
- Object type:
PDDeviceCMYK - Test condition:
gOutputCS != null && gOutputCS == "CMYK" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
DeviceGray shall only be used if a device independent DefaultGray colour space has been set when the DeviceGray colour space is used, or if a PDF/A OutputIntent is present.
DeviceGray colour space is used without an ICC output intent profile.
- Object type:
PDDeviceGray - Test condition:
gOutputCS != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
For any spot colour used in a DeviceN or NChannel colour space, an entry in the Colorants dictionary shall be present.
A colorant of the DeviceN or NChannel color space is not defined in the Colorants dictionary
- Object type:
PDDeviceN - Test condition:
areColorantsPresent == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 8.6.6.5, Table 71
All Separation arrays within a single PDF/A-2(PDF/A-3) file (including those in Colorants dictionaries) that have the same name shall have the same tintTransform and alternateSpace. In evaluating equivalence, the PDF objects shall be compared, rather than the computational result of the use of those PDF objects. Compression and whether or not an object is direct or indirect shall be ignored.
Several occurrences of a Separation colour space with the same name are not consistent
- Object type:
PDSeparation - Test condition:
areTintAndAlternateConsistent == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
An ExtGState dictionary shall not contain the TR key.
An ExtGState dictionary contains the TR key.
In PDF, a transfer function adjusts the values of color components to compensate for nonlinear response in an output device and in the human eye. Each component of a device color space (for example, the red component of the DeviceRGB space) is intended to represent the perceived lightness or intensity of that color component in proportion to the component’s numeric value. Many devices do not actually behave this way, however; the purpose of a transfer function is to compensate for the device's actual behavior.
As this may lead in significantly different visual appearance of PDF documents on different devices, the use of transfer functions is not permitted by PDF/A.
- Object type:
PDExtGState - Test condition:
TR == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
An ExtGState dictionary shall not contain the TR2 key with a value other than Default.
An ExtGState dictionary contains the TR2 key with a value other than Default.
The TR2 key has the same meaning as TR key (see Rule 6.2.5-1) except that the value may also be the name or name Default, denoting the transfer function used by default by the output device. And this is the only case, permitted in PDF/A-compliant documents.
- Object type:
PDExtGState - Test condition:
TR2 == null || TR2 == "Default" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
An ExtGState dictionary shall not contain the HTP key.
An ExtGState dictionary contains the HTP key.
- Object type:
PDExtGState - Test condition:
containsHTP == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
All halftones in a conforming PDF/A-2(PDF/A-3) file shall have the value 1 or 5 for the HalftoneType key.
A Halftone has type other than 1 or 5
- Object type:
PDHalftone - Test condition:
HalftoneType != null && (HalftoneType == 1 || HalftoneType == 5) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Halftones in a conforming PDF/A-2(PDF/A-3) file shall not contain a HalftoneName key.
A Halftone dictionary contains the HalftoneName key
- Object type:
PDHalftone - Test condition:
HalftoneName == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The TransferFunction key in a halftone dictionary shall be used only as required by ISO 32000-1.
Custom TransferFunction in a Halftone dictionary is not permitted for primary (CMYK) colorants
- Object type:
PDHalftone - Test condition:
colorantName == 'Default' || ((colorantName == null || colorantName == 'Cyan' || colorantName == 'Magenta' || colorantName == 'Yellow' || colorantName == 'Black') ? TransferFunction == null : TransferFunction != null) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, Table 130
Where a rendering intent is specified, its value shall be one of the four values defined in ISO 32000-1:2008, Table 70: RelativeColorimetric, AbsoluteColorimetric, Perceptual or Saturation.
A rendering intent with non-standard value is used
Although CIE-based color specifications are theoretically device-independent, they are subject to practical limitations in the color reproduction capabilities of the output device. Such limitations may sometimes require compromises to be made among various properties of a color specification when rendering colors for a given device. Specifying a rendering intent allows a PDF file to set priorities regarding which of these properties to preserve and which to sacrifice.
ISO 32000-1:2008 defines four standard rendering intents, which can be specified directly in the page content stream via the "ri" operator or attached to any image as an extra property. These standard intents have been deliberately chosen to correspond closely to those defined by the International Color Consortium (ICC), an industry organization that has developed standards for device-independent color.
However, that the exact set of rendering intents supported may vary from one output device to another; a particular device may not support all possible intents, or may support additional ones beyond those listed in the table. To guarantee the predictability of PDF rendering results, non-standard rendering intents are not permitted in PDF/A-compliant documents.
- Object type:
CosRenderingIntent - Test condition:
internalRepresentation == "RelativeColorimetric" || internalRepresentation == "AbsoluteColorimetric" || internalRepresentation == "Perceptual" || internalRepresentation == "Saturation" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
An Image dictionary shall not contain the Alternates key.
Alternates key is present in the Image dictionary.
Alternate images provide a straightforward and backward-compatible way to include multiple versions of an image in a PDF file for different purposes. These variant representations of the image may differ, for example, in resolution or in color space. The primary goal is to reduce the need to maintain separate versions of a PDF document for low-resolution on-screen viewing and highresolution printing. However, this mechanism is prohibited in PDF/A-compliant documents, as it introduces risks of choosing different images for rendering.
- Object type:
PDXImage - Test condition:
containsAlternates == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
An Image dictionary shall not contain the OPI key.
OPI key is present in the Image dictionary.
The Open Prepress Interface (OPI) is a mechanism, originally developed by Aldus Corporation, for creating low-resolution placeholders, or proxies, for such high-resolution images. The proxy typically consists of a downsampled version of the full-resolution image, to be used for screen display and proofing. Before the document is printed, it passes through a filter known as an OPI server, which replaces the proxies with the original full-resolution images. Similar to Rule 6.2.8-1, this mechanism is prohibited in PDF/A-compliant documents, as it introduces risks of unpredictable PDF rendering.
- Object type:
PDXImage - Test condition:
containsOPI == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If an Image dictionary contains the Interpolate key, its value shall be false. For an inline image, the I key shall have a value of false.
The value of the Interpolate key in the Image dictionary is true
When the resolution of a source image is significantly lower than that of the output device, each source sample covers many device pixels. This can cause images to appear "jaggy" or "blocky." These visual artifacts can be reduced by applying an image interpolation algorithm during rendering. Instead of painting all pixels covered by a source sample with the same color, image interpolation attempts to produce a smooth transition between adjacent sample values.
However, the interpolation algorithm is implementation-dependent and is not specified by PDF. Image interpolation may not always be performed for some classes of images or on some output devices. Therefore, this mechanism is not permitted in PDF/A-compliant documents.
- Object type:
PDXImage - Test condition:
Interpolate == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If an Image dictionary contains the BitsPerComponent key, its value shall be 1, 2, 4, 8 or 16
The value of the BitsPerComponent key in the Image dictionary is not equal to 1, 2, 4, 8 or 16
- Object type:
PDXImage - Test condition:
BitsPerComponent == null || BitsPerComponent == 1 || BitsPerComponent == 2 || BitsPerComponent == 4 || BitsPerComponent == 8 || BitsPerComponent == 16 - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 8.9.5.1, Table 89
The number of colour channels in the JPEG2000 data shall be 1, 3 or 4.
JPEG2000 image has number of colour channels different from 1, 3 or 4.
- Object type:
JPEG2000 - Test condition:
nrColorChannels == 1 || nrColorChannels == 3 || nrColorChannels == 4 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If the number of colour space specifications in the JPEG2000 data is greater than 1, there shall be exactly one colour space specification that has the value 0x01 in the APPROX field.
The JPEG2000 image contains more than one colour specification with the best colour fidelity (value 0x01 in the APPROX field).
- Object type:
JPEG2000 - Test condition:
hasColorSpace == true || nrColorSpaceSpecs == 1 || nrColorSpacesWithApproxField == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The value of the METH entry in its 'colr' box shall be 0x01, 0x02 or 0x03. A conforming reader shall use only that colour space and shall ignore all other colour space specifications.
Invalid JPEG2000 image: the value of the METH entry in its 'colr' box is different from 0x01, 0x02 or 0x03.
- Object type:
JPEG2000 - Test condition:
hasColorSpace == true || colrMethod == 1 || colrMethod == 2 || colrMethod == 3 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
JPEG2000 enumerated colour space 19 (CIEJab) shall not be used.
JPEG2000 image uses enumerated colour space 19 (CIEJab), which is not allowed in PDF/A.
- Object type:
JPEG2000 - Test condition:
hasColorSpace == true || colrEnumCS == null || colrEnumCS != 19 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The bit-depth of the JPEG2000 data shall have a value in the range 1 to 38. All colour channels in the JPEG2000 data shall have the same bit-depth.
JPEG2000 image has different bit-depth parameters in 'bpcc' box, or bit depth is out of range
- Object type:
JPEG2000 - Test condition:
bpccBoxPresent == false && (bitDepth >= 1 && bitDepth <= 38) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A form XObject dictionary shall not contain any of the following: - the OPI key; - the Subtype2 key with a value of PS; - the PS key.
The form XObject dictionary contains a PS key, or a Subtype2 key with value PS, or an OPI key.
In earlier versions of PDF, a content stream can include PostScript language fragments. These fragments are used only when printing to a PostScript output device; they have no effect either when viewing the document on-screen or when printing to a non-PostScript device. In addition, applications that understand PDF are unlikely to be able to interpret the PostScript fragments. Hence, this capability should be used with extreme caution and only if there is no other way to achieve the same result. Inappropriate use of PostScript XObjects can cause PDF files to print incorrectly.
- Object type:
PDXForm - Test condition:
(Subtype2 == null || Subtype2 != "PS") && containsPS == false && containsOPI == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any reference XObjects.
The document contains a reference XObject (Ref key in the form XObject dictionary).
Reference XObjects enable one PDF document to import content from another. The document in which the reference occurs is called the containing document; the one whose content is being imported is the target document. The target document may reside in a file external to the containing document or may be included within it as an embedded file stream.
As this makes the initial PDF document dependent on the presence of external resources, this mechanism is not permitted in PDF/A-compliant documents.
- Object type:
PDXForm - Test condition:
containsRef == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A conforming file shall not contain any PostScript XObjects.
The document contains a PostScript XObject.
PostScript XObjects contain arbitrary executable PostScript code streams that have the potential to interfere with reliable and predictable rendering. See Rule 6.2.9-1 for more detail.
- Object type:
PDXObject - Test condition:
Subtype != "PS" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Only blend modes that are specified in ISO 32000-1:2008 shall be used for the value of the BM key in an extended graphic state dictionary.
The document uses the blend mode not defined in ISO 32000-1:2008.
- Object type:
CosBM - Test condition:
internalRepresentation == "Normal" || internalRepresentation == "Compatible" || internalRepresentation == "Multiply" || internalRepresentation == "Screen" || internalRepresentation == "Overlay" || internalRepresentation == "Darken" || internalRepresentation == "Lighten" || internalRepresentation == "ColorDodge" || internalRepresentation == "ColorBurn" || internalRepresentation == "HardLight" || internalRepresentation == "SoftLight" || internalRepresentation == "Difference" || internalRepresentation == "Exclusion" || internalRepresentation == "Hue" || internalRepresentation == "Saturation" || internalRepresentation == "Color" || internalRepresentation == "Luminosity" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 11.3.5, Tables 136-137
If the document does not contain a PDF/A OutputIntent, then all Page objects that contain transparency shall include the Group key, and the attribute dictionary that forms the value of that Group key shall include a CS entry whose value shall be used as the default blending colour space.
The page contains transparent objects with no blending colour space defined.
PDF transparency (as described in ISO 32000-1:2008, Clause 11) may be used in a PDF/A-2 or PDF/A-3 file. This requirement ensures that there is always an explicitly defined transparency blending space specified for any content which has associated transparency.
- Object type:
PDPage - Test condition:
gOutputCS != null || containsGroupCS == true || containsTransparency == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 11.3.4
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
Type - name - (Required) The type of PDF object that this dictionary describes; must be Font for a font dictionary
A Font dictionary has missing or invalid Type entry
- Object type:
PDFont - Test condition:
Type == "Font" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.6.5, Table 112
- ISO 32000-1:2008, 9.7.4.1, Table 117
- ISO 32000-1:2008, 9.7.6.1, Table 121
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
Subtype - name - (Required) The type of font; must be "Type1" for Type 1 fonts, "MMType1" for multiple master fonts, "TrueType" for TrueType fonts "Type3" for Type 3 fonts, "Type0" for Type 0 fonts and "CIDFontType0" or "CIDFontType2" for CID fonts
A Font dictionary has missing or invalid Subtype entry.
The correct value of the Subtype entry in the font dictionary is critical for the text rendering in PDF documents.
- Object type:
PDFont - Test condition:
Subtype == "Type1" || Subtype == "MMType1" || Subtype == "TrueType" || Subtype == "Type3" || Subtype == "Type0" || Subtype == "CIDFontType0" || Subtype == "CIDFontType2" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.6.2.3
- ISO 32000-1:2008, 9.6.3
- ISO 32000-1:2008, 9.6.5, Table 112
- ISO 32000-1:2008, 9.7.4.1, Table 117
- ISO 32000-1:2008, 9.7.6.1, Table 121
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
BaseFont - name - (Required) The PostScript name of the font
A BaseFont entry is missing or has invalid type
For Type 1 fonts, this is usually the value of the FontName entry in the font program. The PostScript name of the font can be used to find the font’s definition in the viewer application or its environment. It is also the name that will be used when printing to a PostScript output device.
For TrueType fonts the value of BaseFont is determined in one of two ways. It is defined as the PostScript name that is an optional entry in the "name" table of the TrueType font itself. In the absence of such an entry in the "name" table, a PostScript name is derived from the name by which the font is known in the host operating system.
- Object type:
PDFont - Test condition:
Subtype == "Type3" || fontName != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.7.4.1, Table 117
- ISO 32000-1:2008, 9.7.6.1, Table 121
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
FirstChar - integer - (Required except for the standard 14 fonts) The first character code defined in the font's Widths array
A non-standard simple font dictionary has missing or invalid FirstChar entry
The PostScript names of 14 Type 1 fonts, known as the standard fonts, are as follows:
Times−Roman Helvetica Courier Symbol Times−Bold Helvetica−Bold Courier−Bold ZapfDingbats Times−Italic Helvetica−Oblique Courier−Oblique Times−BoldItalic Helvetica−BoldOblique Courier−BoldOblique
These fonts, or their font metrics and suitable substitution fonts, are guaranteed to be available to any viewer application.
- Object type:
PDSimpleFont - Test condition:
isStandard == true || FirstChar != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.6.5, Table 112
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
LastChar - integer - (Required except for the standard 14 fonts) The last character code defined in the font's Widths array
A non-standard simple font dictionary has missing or invalid LastChar entry
See also rule 6.2.11.2-4.
- Object type:
PDSimpleFont - Test condition:
isStandard == true || LastChar != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.6.5, Table 112
All fonts and font programs used in a conforming file, regardless of rendering mode usage, shall conform to the provisions in ISO 32000-1:2008, 9.6 and 9.7, as well as to the font specifications referenced by these provisions.
Widths - array - (Required except for the standard 14 fonts; indirect reference preferred) An array of (LastChar - FirstChar + 1) widths
Font Widths array is missing or has invalid size.
See also rule 6.2.11.2-4.
- Object type:
PDSimpleFont - Test condition:
isStandard == true || (Widths_size != null && Widths_size == LastChar - FirstChar + 1) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.2.1, Table 111
- ISO 32000-1:2008, 9.6.5, Table 112
All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5. The subtype is the value of the Subtype key, if present, in the font file stream dictionary. The only valid values of this key in PDF 1.7 are Type1C - Type 1–equivalent font program represented in the Compact Font Format (CFF), CIDFontType0C - Type 0 CIDFont program represented in the Compact Font Format (CFF) and OpenType - OpenType® font program, as described in the OpenType Specification v.1.4.
Unsupported font file format of the embedded font.
- Object type:
PDFont - Test condition:
fontFileSubtype == null || fontFileSubtype == "Type1C" || fontFileSubtype == "CIDFontType0C" || fontFileSubtype == "OpenType" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.9, Table 126,
- Adobe Technical Note #5176, The Compact Font Format Specification,
- OpenType Font Specification 1.4, December 2004, Microsoft
For any given composite (Type 0) font within a conforming file, the CIDSystemInfo entry in its CIDFont dictionary and its Encoding dictionary shall have the following relationship. If the Encoding key in the Type 0 font dictionary is Identity-H or Identity-V, any values of Registry, Ordering, and Supplement may be used in the CIDSystemInfo entry of the CIDFont. Otherwise, the corresponding Registry and Ordering strings in both CIDSystemInfo dictionaries shall be identical, and the value of the Supplement key in the CIDSystemInfo dictionary of the CIDFont shall be less than or equal to the Supplement key in the CIDSystemInfo dictionary of the CMap.
CIDSystemInfo entries the CIDFont and CMap dictionaries of a Type 0 font are not compatible.
CIDFont and CMap dictionaries contain a CIDSystemInfo entry specifying the character collection assumed by the CIDFont or by each CIDFont associated with the CMap - that is, the interpretation of the CID numbers used by the CIDFont. A character collection is uniquely identified by the Registry, Ordering, and Supplement entries in the CIDSystemInfo dictionary. Character collections whose Registry and Ordering values are the same are compatible.
PDF/A-2 and PDF/A-3 standards require that the Registry and Ordering strings of the CIDSystemInfo dictionaries for that font shall be identical and the value of the Supplement key in the CIDSystemInfo dictionary of the CIDFont shall be less than or equal to the Supplement key in the CIDSystemInfo dictionary of the CMap, unless the value of the CMap dictionary UserCMap key is "Identity-H" or "Identity-V".
- Object type:
PDType0Font - Test condition:
cmapName == "Identity-H" || cmapName == "Identity-V" || (CIDFontOrdering != null && CIDFontOrdering == CMapOrdering && CIDFontRegistry != null && CIDFontRegistry == CMapRegistry && CIDFontSupplement != null && CMapSupplement != null && CIDFontSupplement <= CMapSupplement) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
ISO 32000-1:2008, 9.7.4, Table 117 requires that all embedded Type 2 CIDFonts in the CIDFont dictionary shall contain a CIDToGIDMap entry that shall be a stream mapping from CIDs to glyph indices or the name Identity, as described in ISO 32000-1:2008, 9.7.4, Table 117.
A Type 2 CIDFont dictionary has missing or invalid CIDToGIDMap entry.
For Type 2, the CIDFont program is actually a TrueType font program, which has no native notion of CIDs. In a TrueType font program, glyph descriptions are identified by glyph index values. Glyph indices are internal to the font and are not defined consistently from one font to another. Instead, a TrueType font program contains a "cmap" table that provides mappings directly from character codes to glyph indices for one or more predefined encodings.
If the TrueType font program is embedded, the Type 2 CIDFont dictionary must contain a CIDToGIDMap entry that maps CIDs to the glyph indices for the appropriate glyph descriptions in that font program.
- Object type:
PDCIDFont - Test condition:
Subtype != "CIDFontType2" || CIDToGIDMap != null || fontFile_size == 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.7.4, Table 117
All CMaps used within a PDF/A-2(PDF/A-3) file, except those listed in ISO 32000-1:2008, 9.7.5.2, Table 118, shall be embedded in that file as described in ISO 32000-1:2008, 9.7.5.
A non-standard CMap is not embedded
- Object type:
PDCMap - Test condition:
CMapName == "Identity-H" || CMapName == "Identity-V" || CMapName == "GB-EUC-H" || CMapName == "GB-EUC-V" || CMapName == "GBpc-EUC-H" || CMapName == "GBpc-EUC-V" || CMapName == "GBK-EUC-H" || CMapName == "GBK-EUC-V" || CMapName == "GBKp-EUC-H" || CMapName == "GBKp-EUC-V" || CMapName == "GBK2K-H" || CMapName == "GBK2K-V" || CMapName == "UniGB-UCS2-H" || CMapName == "UniGB-UCS2-V" || CMapName == "UniGB-UFT16-H" || CMapName == "UniGB-UFT16-V" || CMapName == "B5pc-H" || CMapName == "B5pc-V" || CMapName == "HKscs-B5-H" || CMapName == "HKscs-B5-V" || CMapName == "ETen-B5-H" || CMapName == "ETen-B5-V" || CMapName == "ETenms-B5-H" || CMapName == "ETenms-B5-V" || CMapName == "CNS-EUC-H" || CMapName == "CNS-EUC-V" || CMapName == "UniCNS-UCS2-H" || CMapName == "UniCNS-UCS2-V" || CMapName == "UniCNS-UFT16-H" || CMapName == "UniCNS-UTF16-V" || CMapName == "83pv-RKSJ-H" || CMapName == "90ms-RKSJ-H" || CMapName == "90ms-RKSJ-V" || CMapName == "90msp-RKSJ-H" || CMapName == "90msp-RKSJ-V" || CMapName == "90pv-RKSJ-H" || CMapName == "Add-RKSJ-H" || CMapName == "Add-RKSJ-V" || CMapName == "EUC-H" || CMapName == "EUC-V" || CMapName == "Ext-RKSJ-H" || CMapName == "Ext-RKSJ-V" || CMapName == "H" || CMapName == "V" || CMapName == "UniJIS-UCS2-H" || CMapName == "UniJIS-UCS2-V" || CMapName == "UniJIS-UCS2-HW-H" || CMapName == "UniJIS-UCS2-HW-V" || CMapName == "UniJIS-UTF16-H" || CMapName == "UniJIS-UTF16-V" || CMapName == "KSC-EUC-H" || CMapName == "KSC-EUC-V" || CMapName == "KSCms-UHC-H" || CMapName == "KSCms-UHC-V" || CMapName == "KSCms-UHC-HW-H" || CMapName == "KSCms-UHC-HW-V" || CMapName == "KSCpc-EUC-H" || CMapName == "UniKS-UCS2-H" || CMapName == "UniKS-UCS2-V" || CMapName == "UniKS-UTF16-H" || CMapName == "UniKS-UTF16-V" || embeddedFile_size == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.7.5.2, Table 118
For those CMaps that are embedded, the integer value of the WMode entry in the CMap dictionary shall be identical to the WMode value in the embedded CMap stream.
WMode entry in the embedded CMap and in the CMap dictionary are not identical.
A CMap also specifies the writing mode (horizontal or vertical) for any CIDFont with which the CMap is combined. This determines which metrics are to be used when glyphs are painted from that font.
In case of embedded CMap file, the writing mode is specified in two different places: in the PDF dictionary associated with the embedded CMap, and inside the embedded CMap file itself. To avoid any ambiguities, PDF/A standard requires that values of these two writing modes coincide.
- Object type:
CMapFile - Test condition:
WMode == dictWMode - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A CMap shall not reference any other CMap except those listed in ISO 32000-1:2008, 9.7.5.2, Table 118.
A CMap references another non-standard CMap
- Object type:
PDReferencedCMap - Test condition:
CMapName == "Identity-H" || CMapName == "Identity-V" || CMapName == "GB-EUC-H" || CMapName == "GB-EUC-V" || CMapName == "GBpc-EUC-H" || CMapName == "GBpc-EUC-V" || CMapName == "GBK-EUC-H" || CMapName == "GBK-EUC-V" || CMapName == "GBKp-EUC-H" || CMapName == "GBKp-EUC-V" || CMapName == "GBK2K-H" || CMapName == "GBK2K-V" || CMapName == "UniGB-UCS2-H" || CMapName == "UniGB-UCS2-V" || CMapName == "UniGB-UFT16-H" || CMapName == "UniGB-UFT16-V" || CMapName == "B5pc-H" || CMapName == "B5pc-V" || CMapName == "HKscs-B5-H" || CMapName == "HKscs-B5-V" || CMapName == "ETen-B5-H" || CMapName == "ETen-B5-V" || CMapName == "ETenms-B5-H" || CMapName == "ETenms-B5-V" || CMapName == "CNS-EUC-H" || CMapName == "CNS-EUC-V" || CMapName == "UniCNS-UCS2-H" || CMapName == "UniCNS-UCS2-V" || CMapName == "UniCNS-UFT16-H" || CMapName == "UniCNS-UTF16-V" || CMapName == "83pv-RKSJ-H" || CMapName == "90ms-RKSJ-H" || CMapName == "90ms-RKSJ-V" || CMapName == "90msp-RKSJ-H" || CMapName == "90msp-RKSJ-V" || CMapName == "90pv-RKSJ-H" || CMapName == "Add-RKSJ-H" || CMapName == "Add-RKSJ-V" || CMapName == "EUC-H" || CMapName == "EUC-V" || CMapName == "Ext-RKSJ-H" || CMapName == "Ext-RKSJ-V" || CMapName == "H" || CMapName == "V" || CMapName == "UniJIS-UCS2-H" || CMapName == "UniJIS-UCS2-V" || CMapName == "UniJIS-UCS2-HW-H" || CMapName == "UniJIS-UCS2-HW-V" || CMapName == "UniJIS-UTF16-H" || CMapName == "UniJIS-UTF16-V" || CMapName == "KSC-EUC-H" || CMapName == "KSC-EUC-V" || CMapName == "KSCms-UHC-H" || CMapName == "KSCms-UHC-V" || CMapName == "KSCms-UHC-HW-H" || CMapName == "KSCms-UHC-HW-V" || CMapName == "KSCpc-EUC-H" || CMapName == "UniKS-UCS2-H" || CMapName == "UniKS-UCS2-V" || CMapName == "UniKS-UTF16-H" || CMapName == "UniKS-UTF16-V" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.7.5.2, Table 118
The font programs for all fonts used for rendering within a conforming file shall be embedded within that file, as defined in ISO 32000-1:2008, 9.9.
The font program is not embedded
Text rendering mode 3 specifies that glyphs are not stroked, filled or used as a clipping boundary. A font referenced for use solely in this mode is therefore not rendered and is thus exempt from the embedding requirement.
- Object type:
PDFont - Test condition:
Subtype == "Type3" || Subtype == "Type0" || renderingMode == 3 || fontFile_size == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.9
Embedded fonts shall define all glyphs referenced for rendering within the conforming file. A font referenced for use solely in rendering mode 3 is therefore not rendered and is thus exempt from the embedding requirement. In all cases for TrueType fonts that are to be rendered, character codes shall be able to be mapped to glyphs according to ISO 32000-1:2008, 9.6.6.4 without the use of a non-standard mapping chosen by the conforming processor.
Not all glyphs referenced for rendering are present in the embedded font program.
All conforming PDF/A readers shall use the embedded fonts, rather than other locally resident, substituted or simulated fonts, for rendering.
The fonts used exclusively with text rendering mode 3 (invisible) are exempt from this requirement. OCR solutions often use such invisible fonts on top of the original scanned image to enable selection and copying of recognized text.
There is no exemption from the requirements of this rule for the 14 standard Type 1 fonts. See Rule 6.2.11.2-4 for the list of all standard fonts.
- Object type:
Glyph - Test condition:
renderingMode == 3 || isGlyphPresent == null || isGlyphPresent == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 9.6.6.4
If the FontDescriptor dictionary of an embedded Type 1 font contains a CharSet string, then it shall list the character names of all glyphs present in the font program, regardless of whether a glyph in the font is referenced or used by the PDF or not.
A CharSet entry in the Descriptor dictionary of a Type1 font incorrectly lists glyphs present in the font program.
- Object type:
PDType1Font - Test condition:
fontFile_size == 0 || fontName.search(/[A-Z]{6}\+/) != 0 || CharSet == null || charSetListsAllGlyphs == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If the FontDescriptor dictionary of an embedded CID font contains a CIDSet stream, then it shall identify all CIDs which are present in the font program, regardless of whether a CID in the font is referenced or used by the PDF or not.
A CIDSet entry in the Font descriptor does not correctly identify all glyphs present in the embedded font subset.
- Object type:
PDCIDFont - Test condition:
fontFile_size == 0 || fontName.search(/[A-Z]{6}\+/) != 0 || containsCIDSet == false || cidSetListsAllGlyphs == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
For every font embedded in a conforming file and used for rendering, the glyph width information in the font dictionary and in the embedded font program shall be consistent.
Glyph width information in the embedded font program is not consistent with the Widths entry of the font dictionary.
This requirement is necessary to ensure predictable font rendering, regardless of whether a given reader uses the metrics in the Widths entry or those in the font program.
- Object type:
Glyph - Test condition:
renderingMode == 3 || widthFromFontProgram == null || widthFromDictionary == null || Math.abs(widthFromFontProgram - widthFromDictionary) <= 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
For all non-symbolic TrueType fonts used for rendering, the embedded TrueType font program shall contain one or several non-symbolic cmap entries such that all necessary glyph lookups can be carried out.
The embedded font program for a non-symbolic TrueType font does not contain non-symbolic cmap entries.
- Object type:
TrueTypeFontProgram - Test condition:
isSymbolic == true || (cmap30Present == true ? nrCmaps > 1 : nrCmaps > 0) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
All non-symbolic TrueType fonts shall have either MacRomanEncoding or WinAnsiEncoding as the value for the Encoding key in the Font dictionary or as the value for the BaseEncoding key dictionary that is the value of the Encoding key in the Font dictionary. In addition, all non-symbolic TrueType fonts shall not define a Differences array unless all of the glyph names in the Differences array are listed in the Adobe Glyph List and the embedded font program contains at least the Microsoft Unicode (3,1 – Platform ID = 3, Encoding ID = 1) encoding in the 'cmap' table.
A non-symbolic TrueType font encoding does not define a correct mapping to the Adobe Glyph List
- Object type:
PDTrueTypeFont - Test condition:
isSymbolic == true || ((Encoding == "MacRomanEncoding" || Encoding == "WinAnsiEncoding") && (containsDifferences == false || differencesAreUnicodeCompliant == true)) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Symbolic TrueType fonts shall not contain an Encoding entry in the font dictionary.
A symbolic TrueType font specifies an Encoding entry in its dictionary.
A Font is called symbolic if it contains characters outside the Adobe standard Latin character set. It is marked by special flag in its font descriptor dictionary.
- Object type:
PDTrueTypeFont - Test condition:
isSymbolic == false || Encoding == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The 'cmap' table in the embedded font program for a symbolic TrueType font shall contain either exactly one encoding or it shall contain, at least, the Microsoft Symbol (3,0 - Platform ID=3, Encoding ID=0) encoding.
The embedded font program for a symbolic TrueType font contains more than one cmap subtable.
- Object type:
TrueTypeFontProgram - Test condition:
isSymbolic == false || nrCmaps == 1 || cmap30Present == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The Font dictionary of all fonts shall define the map of all used character codes to Unicode values, either via a ToUnicode entry, or other mechanisms as defined in ISO 19005-2, 6.2.11.7.2.
The glyph can not be mapped to Unicode
- Object type:
Glyph - Test condition:
toUnicode != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, U
The Unicode values specified in the ToUnicode CMap shall all be greater than zero (0), but not equal to either U+FEFF or U+FFFE.
The glyph has Unicode value 0, U+FEFF or U+FFFE, which is invalid by Unicode standard.
The font dictionary of all fonts, regardless of their rendering mode usage, shall include a ToUnicode entry whose value is a CMap stream object that maps character codes for at least all referenced glyphs to Unicode values, as described in ISO 32000-1:2008, 9.10.3, unless the font meets at least one of the following four conditions:
- fonts that use the predefined encodings MacRomanEncoding, MacExpertEncoding or WinAnsiEncoding;
- Type 1 and Type 3 fonts where the glyph names of the glyphs referenced are all contained in the Adobe Glyph List or the set of named characters in the Symbol font, as defined in ISO 32000-1:2008, Annex D;
- Type 0 fonts whose descendant CIDFont uses the Adobe-GB1, Adobe-CNS1, Adobe-Japan1 or Adobe-Korea1 character collections.
- Non-symbolic TrueType fonts.
This requirement ensures that the values in the ToUnicode CMap will be useful values and not simply placeholders.
- Object type:
Glyph - Test condition:
toUnicode == null || (toUnicode.indexOf("\u0000") == -1 && toUnicode.indexOf("\uFFFE") == -1 && toUnicode.indexOf("\uFEFF") == -1) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, U
For any character, regardless of its rendering mode, that is mapped to a code or codes in the Unicode Private Use Area (PUA), an ActualText entry as described in ISO 32000-1:2008, 14.9.4 shall be present for this character or a sequence of characters of which such a character is a part.
The character has Unicode value from Private Use Area, and no replacement text present
- Object type:
Glyph - Test condition:
unicodePUA == false || actualTextPresent == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.9.4
A PDF/A-2(PDF/A-3) compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream.
The document contains a reference to the .notdef glyph.
- Object type:
Glyph - Test condition:
name != ".notdef" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Annotation types not defined in ISO 32000-1 shall not be permitted. Additionally, the 3D, Sound, Screen and Movie types shall not be permitted.
Unknown or not permitted annotation type.
An annotation associates an object such as a note, sound, or movie with a location on a page of a PDF document, or provides a means of interacting with the user via the mouse and keyboard. PDF includes a wide variety of standard annotation types, described in detail in ISO 32000-1:2008, 12.5.6, "Annotation Types."
Support for multimedia content is outside the scope of PDF/A-2 and PDF/A-3, and, thus, annotations of type "Sound" and "Movie" are not permitted.
- Object type:
PDAnnot - Test condition:
Subtype == "Text" || Subtype == "Link" || Subtype == "FreeText" || Subtype == "Line" || Subtype == "Square" || Subtype == "Circle" || Subtype == "Polygon" || Subtype == "PolyLine" || Subtype == "Highlight" || Subtype == "Underline" || Subtype == "Squiggly" || Subtype == "StrikeOut" || Subtype == "Stamp" || Subtype == "Caret" || Subtype == "Ink" || Subtype == "Popup" || Subtype == "FileAttachment" || Subtype == "Widget" || Subtype == "PrinterMark" || Subtype == "TrapNet" || Subtype == "Watermark" || Subtype == "Redact" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- PDF 1.4 Reference, 12.5.6.1, Table 169
Except for annotation dictionaries whose Subtype value is Popup, all annotation dictionaries shall contain the F key.
A dictionary of a non-Popup annotation does not contain F key.
- Object type:
PDAnnot - Test condition:
Subtype == "Popup" || F != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If present, the F key's Print flag bit shall be set to 1 and its Hidden, Invisible, ToggleNoView, and NoView flag bits shall be set to 0.
Annotation flags are set the annotation to be hidden/invisible or non-printable.
The value of the annotation dictionary's F entry is an unsigned 32-bit integer containing flags specifying various characteristics of the annotation. Bit positions within the flag word are numbered from 1 (low-order) to 32 (high-order).
Flag "Invisible" (bit position 1), if clear, allows to display an unknown annotation using an appearance stream specified by its appearance dictionary, if any.
Flag "Hidden" (bit position 2), if set, specifies to not display or print the annotation or allow it to interact with the user, regardless of its annotation type.
Flag "Print" (bit position 3), if set, specifies to print the annotation when the page is printed.
Flag "NoView" (bit position 6), if set, specifies to not display the annotation on the screen or allow it to interact with the user.
Flag "ToggleNoView" (bit position 9), if set, inverts the interpretation of the NoView flag for certain events.
The restrictions on annotation flags prevent the use of annotations that are hidden or that are viewable but not printable.
- Object type:
PDAnnot - Test condition:
F == null || ((F & 1) == 0 && (F & 2) == 0 && (F & 4) == 4 && (F & 32) == 0 && (F & 256) == 0) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Every annotation (including those whose Subtype value is Widget, as used for form fields), except for the two cases listed below, shall have at least one appearance dictionary: annotations where the value of the Rect key consists of an array where value 1 is equal to value 3 and value 2 is equal to value 4; annotations whose Subtype value is Popup or Link.
An annotation does not contain an appearance dictionary.
- Object type:
PDAnnot - Test condition:
(width == 0 && height == 0) || Subtype == "Popup" || Subtype == "Link" || AP != null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
For all annotation dictionaries containing an AP key, the appearance dictionary that it defines as its value shall contain only the N key.
Annotation's appearance dictionary contains entries other than N
An annotation can define as many as three separate appearances. The normal appearance (N key in the appearance dictionary) is used when the annotation is not interacting with the user. This is also the appearance that is used for printing the annotation. The rollover appearance (R key) is used when the user moves the cursor into the annotation's active area without pressing the mouse button. The down appearance (R key) is used when the mouse button is pressed or held down within the annotation's active area.
In accordance with the ISO 32000-1:2008, 12.5.5, a Button form field needs to have multiple appearance states, each one associated with the specific values that the button can take.
Even if a Button form field has only one state, it is still required to have an appearance subdictionary with a single key as its default (and only) state.
- Object type:
PDAnnot - Test condition:
AP == null || AP == "N" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If an annotation dictionary's Subtype key has a value of Widget and its FT key has a value of Btn, the value of the N key shall be an appearance subdictionary.
An annotation dictionary's Subtype key has a value of Widget and its FT key has a value of Btn, but the value of the N key is different from appearance subdictionary
See also rule 6.3.3-2.
- Object type:
PDAnnot - Test condition:
AP != "N" || Subtype != "Widget" || FT != "Btn" || (N_type == "Dict" && appearance_size > 0) - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If an annotation dictionary's Subtype key has value other than Widget, or if FT key associated with Widget annotation has value other than Btn, the value of the N key shall be an appearance stream.
An annotation dictionary's Subtype key has a value other than Widget or/and its FT key different from Btn, but the value of the N key is not an appearance stream
See also rule 6.3.3-2.
- Object type:
PDAnnot - Test condition:
AP != "N" || (Subtype == "Widget" && FT == "Btn") || N_type == "Stream" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A Widget annotation dictionary shall not contain the A or AA keys.
A Widget annotation contains either A or AA entry.
Such actions may modify the values of the forms and alter the visual representation of the document.
- Object type:
PDWidgetAnnot - Test condition:
containsA == false && containsAA == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A Field dictionary shall not contain the A or AA keys.
A Form field dictionary contains the AA entry.
These additional-actions dictionaries define arbitrary JavaScript actions. The explicit prohibition of the AA entry has the implicit effect of disallowing JavaScript actions that can create external dependencies and complicate preservation efforts.
- Object type:
PDFormField - Test condition:
containsAA == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The NeedAppearances flag of the interactive form dictionary shall either not be present or shall be false.
The interactive form dictionary contains the NeedAppearances flag with value true.
Every form field shall have an appearance dictionary associated with the field's data. A conforming reader shall render the field according to the appearance dictionary without regard to the form data. Requiring an appearance dictionary ensures the reliable rendering of the form.
- Object type:
PDAcroForm - Test condition:
NeedAppearances == null || NeedAppearances == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The document's interactive form dictionary that forms the value of the AcroForm key in the document's Catalog of a PDF/A-2(PDF/A-3) file, if present, shall not contain the XFA key.
The interactive form dictionary contains the XFA key.
- Object type:
PDAcroForm - Test condition:
containsXFA == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A document's Catalog shall not contain the NeedsRendering key.
A document's Catalog contains NeedsRendering flag set to true.
- Object type:
CosDocument - Test condition:
NeedsRendering == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
When computing the digest for the file, it shall be computed over the entire file, including the signature dictionary but excluding the PDF Signature itself.
ByteRange array of the digital signature does not cover the entire file (excluding the PDF Signature itself).
As permitted by ISO 32000-1:2008, 12.8.1, a PDF/A-2 or PDF/A-3 conforming file may contain document, certifying or user rights signatures. Such signatures shall be specified in the PDF through the use of signature fields in accordance with ISO 32000-1:2008, 12.7.4.5.
This makes normative a recommendation in ISO 32000-1:2008, 12.8.1. By restricting the ByteRange entry this way, it ensures that there are no bytes in the PDF that are not covered by the digest, other than the PDF signature itself.
- Object type:
PDSignature - Test condition:
doesByteRangeCoverEntireDocument == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 19005-2:2011, Annex B
- ISO 32000-1:2008, 12.8.1
- ISO 32000-1:2008, 12.7.4.5
The PDF Signature (a DER-encoded PKCS#7 binary data object) shall be placed into the Contents entry of the signature dictionary. The PKCS#7 object shall conform to the PKCS#7 specification in RFC 2315. At minimum, it shall include the signer's X.509 signing certificate.
The DER-encoded PKCS#7 binary data object representing a PDF Signature does not include the signer's X.509 signing certificate
- Object type:
PKCSDataObject - Test condition:
signingCertificatePresent == true - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 19005-2:2011, Annex B
- RFC 2315
The PDF Signature (a DER-encoded PKCS#7 binary data object) shall be placed into the Contents entry of the signature dictionary. The PKCS#7 object shall conform to the PKCS#7 specification in RFC 2315. At minimum, there shall only be a single signer (e.g. a single "SignerInfo" structure) in the PDF Signature.
The DER-encoded PKCS#7 binary data object representing a PDF Signature has number of signer(s) different from one in the PDF Signature instead
- Object type:
PKCSDataObject - Test condition:
SignerInfoCount == 1 - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 19005-2:2011, Annex B
- RFC 2315
The Launch, Sound, Movie, ResetForm, ImportData, Hide, SetOCGState, Rendition, Trans, GoTo3DView and JavaScript actions shall not be permitted. Additionally, the deprecated set-state and no-op actions shall not be permitted.
Unknown or not permitted action type.
Support for multimedia content is outside the scope of PDF/A-2 and PDF/A-3. The ResetForm action changes the rendered appearance of a form. The ImportData action imports form data from an external file. JavaScript actions permit an arbitrary executable code that has the potential to interfere with reliable and predictable rendering.
- Object type:
PDAction - Test condition:
S == "GoTo" || S == "GoToR" || S == "GoToE" || S == "Thread" || S == "URI" || S == "Named" || S == "SubmitForm" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 12.6.4.1, Table 198
Named actions other than NextPage, PrevPage, FirstPage, and LastPage shall not be permitted.
Unknown or not permitted named action.
In response to each of the four allowed named actions, conforming interactive readers shall perform the appropriate action described in ISO 32000-1:2008 Table 211. Viewer applications may support additional, nonstandard named actions, but any document using them will not be portable.
- Object type:
PDNamedAction - Test condition:
N == "NextPage" || N == "PrevPage" || N == "FirstPage" || N == "LastPage" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 12.6.4.11, Table 211
The document's Catalog shall not include an AA entry for an additional-actions dictionary.
The document catalog dictionary contains an additional-actions dictionary (AA entry)
These additional-actions dictionaries define arbitrary JavaScript actions. The explicit prohibition of the AA entry has the implicit effect of disallowing JavaScript actions that can create external dependencies and complicate preservation efforts.
- Object type:
PDDocument - Test condition:
containsAA == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The Page dictionary shall not include an AA entry for an additional-actions dictionary.
The Page dictionary contains an additional-actions dictionary (AA entry).
- Object type:
PDPage - Test condition:
containsAA == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The Catalog dictionary of a conforming file shall contain the Metadata key whose value is a metadata stream as defined in ISO 32000-1:2008, 14.3.2.
The document catalog dictionary doesn't contain metadata key.
Metadata is essential for effective management of a file throughout its life cycle. A file depends on metadata for identification and description, as well as for describing appropriate technical and administrative matters.
Metadata, both for an entire document and for components within a document, can be stored in PDF streams called metadata streams. The contents of a metadata stream is the metadata represented in Extensible Markup Language (XML). The format of the XML representing the metadata is defined as part of a framework called the Extensible Metadata Platform (XMP).
A metadata stream can be attached to a document through the Metadata entry in the document catalog.
- Object type:
PDDocument - Test condition:
metadata_size == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- ISO 32000-1:2008, 14.3.2
The bytes attribute shall not be used in the header of an XMP packet.
The XMP Package contains bytes attribute.
Both the bytes and encoding attributes are deprecated in XMP Specification.
- Object type:
XMPPackage - Test condition:
bytes == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The encoding attribute shall not be used in the header of an XMP packet.
The XMP Package contains encoding attribute.
Both the bytes and encoding attributes are deprecated in XMP Specification.
- Object type:
XMPPackage - Test condition:
encoding == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
All metadata streams present in the PDF shall conform to the XMP Specification. All content of all XMP packets shall be well-formed, as defined by Extensible Markup Language (XML) 1.0 (Third Edition), 2.1, and the RDF/XML Syntax Specification (Revised).
A metadata stream is serialized incorrectly and can not be parsed.
- Object type:
XMPPackage - Test condition:
isSerializationValid - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- XMP Specification September 2005,
- Extensible Markup Language (XML) 1.0 (Third Edition), 04 February 2004, 2.1,
- RDF/XML Syntax Specification (Revised), 10 February 2004
All metadata streams present in the PDF shall conform to the XMP Specification. The XMP package must be encoded as UTF-8.
The XMP package uses an encoding different from UTF-8.
- Object type:
XMPPackage - Test condition:
actualEncoding == "UTF-8" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
- Additional references:
- XMP Specification September 2005, 5 - Embedding XMP Metadata in Application Files - PDF
All properties specified in XMP form shall use either the predefined schemas defined in the XMP Specification, ISO 19005-1 or this part of ISO 19005, or any extension schemas that comply with 6.6.2.3.2.
XMP property is either not predefined, or is not defined in any XMP extension schema.
- Object type:
XMPProperty - Test condition:
isPredefinedInXMP2005 == true || isDefinedInMainPackage == true || isDefinedInCurrentPackage == true - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
All properties specified in XMP form shall use either the predefined schemas defined in the XMP Specification, ISO 19005-1 or this part of ISO 19005, or any extension schemas that comply with 6.6.2.3.2.
XMP property does not correspond to defined type
- Object type:
XMPProperty - Test condition:
isValueTypeCorrect == true - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Extension schemas shall be specified using the PDF/A extension schema container schema defined in 6.6.2.3.3. All fields described in each of the tables in 6.6.2.3.3 shall be present in any extension schema container schema.
An extension schema object contains fields not defined by the specification.
An extension schema is any XMP schema that is not defined in the XMP Specification. All objects of the extension schemas and their fields are specified in ISO 19005-2:2011 (ISO 19005-3:2012), 6.6.2.3 and its technical corrigenda.
- Object type:
ExtensionSchemaObject - Test condition:
containsUndefinedFields == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The extension schema container schema uses the namespace URI "http://www.aiim.org/pdfa/ns/extension/". The required schema namespace prefix is pdfaExtension. pdfaExtension:schemas - Bag Schema - Description of extension schemas
The extension schema container has invalid type or doesn't have prefix 'pdfaExtension'.
Extension schema container stores a sequence of extension schemas defined in the XMP package.
- Object type:
ExtensionSchemasContainer - Test condition:
isValidBag == true && prefix == "pdfaExtension" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'schema' of the PDF/A Schema value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaSchema'.
Field 'schema' of the PDF/A Schema value type is not present, or doesn't have prefix 'pdfaSchema' or doesn't have type Text
- Object type:
ExtensionSchemaDefinition - Test condition:
isSchemaValidText == true && schemaPrefix == "pdfaSchema" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'namespaceURI' of the PDF/A Schema value type in the PDF/A extension schema shall be present and shall have type URI and namespace prefix 'pdfaSchema'.
Field 'namespaceURI' of the PDF/A Schema value type is not present, or doesn't have prefix 'pdfaSchema' or doesn't have type URI
- Object type:
ExtensionSchemaDefinition - Test condition:
isNamespaceURIValidURI == true && namespaceURIPrefix == "pdfaSchema" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'prefix' of the PDF/A Schema value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaSchema'.
Field 'prefix' of the PDF/A Schema value type is not present, or doesn't have prefix 'pdfaSchema' or doesn't have type Text
- Object type:
ExtensionSchemaDefinition - Test condition:
isPrefixValidText == true && prefixPrefix == "pdfaSchema" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'property' of the PDF/A Schema value type in the PDF/A extension schema shall be present and shall have type Seq Property and namespace prefix 'pdfaSchema'.
Field 'property' of the PDF/A Schema value type is not present, or doesn't have prefix 'pdfaSchema' or doesn't have type Seq Property
- Object type:
ExtensionSchemaDefinition - Test condition:
isPropertyValidSeq == true && propertyPrefix == "pdfaSchema" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'valueType' of the PDF/A Schema value type in the PDF/A extension schema shall have type Seq ValueType and namespace prefix 'pdfaSchema'.
Field 'valueType' of the PDF/A Schema value type doesn't have prefix 'pdfaSchema' or doesn't have type Seq ValueType
- Object type:
ExtensionSchemaDefinition - Test condition:
isValueTypeValidSeq == true && (valueTypePrefix == null || valueTypePrefix == "pdfaSchema") - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'name' of the PDF/A Property value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaProperty'.
Field 'name' of the PDF/A Property value type is not present, or doesn't have prefix 'pdfaProperty' or doesn't have type Text
- Object type:
ExtensionSchemaProperty - Test condition:
isNameValidText == true && namePrefix == "pdfaProperty" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'valueType' of the PDF/A Property value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaProperty'. Value of valueType property shall be defined.
Field 'valueType' of the PDF/A Property value type is not present, or doesn't have prefix 'pdfaProperty' or doesn't have type Text or value of valueType doesn't defined
- Object type:
ExtensionSchemaProperty - Test condition:
isValueTypeValidText == true && isValueTypeDefined == true && valueTypePrefix == "pdfaProperty" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'category' of the PDF/A Property value type in the PDF/A extension schema shall be present and shall have type Text, value external or internal and namespace prefix 'pdfaProperty'.
Field 'category' of the PDF/A Property value type is not present, or doesn't have prefix 'pdfaProperty' or doesn't have type Text or has value different from external or internal
- Object type:
ExtensionSchemaProperty - Test condition:
isCategoryValidText == true && (category == "external" || category == "internal") && categoryPrefix == "pdfaProperty" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'description' of the PDF/A Property value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaProperty'.
Field 'description' of the PDF/A Property value type is not present, or doesn't have prefix 'pdfaProperty' or doesn't have type Text
- Object type:
ExtensionSchemaProperty - Test condition:
isDescriptionValidText == true && descriptionPrefix == "pdfaProperty" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'type' of the PDF/A ValueType value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaType'.
Field 'type' of the PDF/A ValueType value type is not present, or doesn't have prefix 'pdfaType' or doesn't have type Text
- Object type:
ExtensionSchemaValueType - Test condition:
isTypeValidText == true && typePrefix == "pdfaType" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'namespaceURI' of the PDF/A ValueType value type in the PDF/A extension schema shall be present and shall have type URI and namespace prefix 'pdfaType'.
Field 'namespaceURI' of the PDF/A ValueType value type is not present, or doesn't have prefix 'pdfaType' or doesn't have type URI
- Object type:
ExtensionSchemaValueType - Test condition:
isNamespaceURIValidURI == true && namespaceURIPrefix == "pdfaType" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'prefix' of the PDF/A ValueType value type in the PDF/A extension schema be present and shall have type Text and namespace prefix 'pdfaType'.
Field 'prefix' of the PDF/A ValueType value type is not present, or doesn't have prefix 'pdfaType' or doesn't have type Text
- Object type:
ExtensionSchemaValueType - Test condition:
isPrefixValidText == true && prefixPrefix == "pdfaType" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'description' of the PDF/A ValueType value type in the PDF/A extension schema shall be present and shall have type Text and namespace prefix 'pdfaType'.
Field 'description' of the PDF/A ValueType value type is not present, or doesn't have prefix 'pdfaType' or doesn't have type Text
- Object type:
ExtensionSchemaValueType - Test condition:
isDescriptionValidText == true && descriptionPrefix == "pdfaType" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'field' of the PDF/A ValueType value type in the PDF/A extension schema shall have type Seq Field and namespace prefix 'pdfaType'.
Field 'field' of the PDF/A ValueType value type doesn't have prefix 'pdfaType' or doesn't have type Seq Field
- Object type:
ExtensionSchemaValueType - Test condition:
isFieldValidSeq == true && (fieldPrefix == null || fieldPrefix == "pdfaType") - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'name' of the PDF/A Field value type in the PDF/A extension schema shall have type Text and namespace prefix 'pdfaField'.
Field 'name' of the PDF/A Field value type is not present, or doesn't have prefix 'pdfaField' or doesn't have type Text
- Object type:
ExtensionSchemaField - Test condition:
isNameValidText == true && namePrefix == "pdfaField" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'valueType' of the PDF/A Field value type in the PDF/A extension schema shall have type Text and namespace prefix 'pdfaField'. Value of valueType property shall be defined.
Field 'valueType' of the PDF/A Field value type is not present, or doesn't have prefix 'pdfaField' or doesn't have type Text or value of valueType doesn't defined
- Object type:
ExtensionSchemaField - Test condition:
isValueTypeValidText == true && isValueTypeDefined == true && valueTypePrefix == "pdfaField" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Field 'description' of the PDF/A Field value type in the PDF/A extension schema shall have type Text and namespace prefix 'pdfaField'.
Field 'description' of the PDF/A Field value type is not present, or doesn't have prefix 'pdfaField' or doesn't have type Text
- Object type:
ExtensionSchemaField - Test condition:
isDescriptionValidText == true && descriptionPrefix == "pdfaField" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The PDF/A version and conformance level of a file shall be specified using the PDF/A Identification extension schema.
The document metadata stream doesn't contains PDF/A Identification Schema.
- Object type:
MainXMPPackage - Test condition:
Identification_size == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The value of "pdfaid:part" shall be the part number of ISO 19005 to which the file conforms.
The "part" property of the PDF/A Identification Schema is does not match the PDF/A profile part number.
- Object type:
PDFAIdentification - Test condition:
part == 2(for PDF/A-2);part == 3(for PDF/A-3). - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
A Level A conforming file shall specify the value of "pdfaid:conformance" as A. A Level B conforming file shall specify the value of "pdfaid:conformance" as B. A Level U conforming file shall specify the value of "pdfaid:conformance" as U.
The "conformance" property of the PDF/A Identification Schema does not confirm the PDF/A profile level.
The "conformance" property of the PDF/A Identification Schema is not equal to "A" for a PDF/A-2a(PDF/A-3a) conforming file.
The "conformance" property of the PDF/A Identification Schema is not equal to "A","B" or "U" for a PDF/A-2b(PDF/A-3b) conforming file.
The "conformance" property of the PDF/A Identification Schema is not equal to "A" or "U" for a PDF/A-2u(PDF/A-3u) conforming file.
As Level B requirements form a strict subset of Levels A and U requirements, validation for Level B conformance also accepts the "conformance" property having a value of "A" and "U".
As Level U requirements form a strict subset of Level A requirements, validation for Level U conformance also accepts the "conformance" property having a value of "A".
- Object type:
PDFAIdentification - Test condition (Level B):
conformance == "B" || conformance == "U" || conformance == "A" - Test condition (Level U):
conformance == "U" || conformance == "A" - Test condition (Level A):
conformance == "A" - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Property "part" of the PDF/A Identification Schema shall have namespace prefix "pdfaid"
Property "part" of the PDF/A Identification Schema has an invalid namespace prefix
- Object type:
PDFAIdentification - Test condition:
partPrefix == null || partPrefix == "pdfaid" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Property "conformance" of the PDF/A Identification Schema shall have namespace prefix "pdfaid"
Property "conformance" of the PDF/A Identification Schema has an invalid namespace prefix
- Object type:
PDFAIdentification - Test condition:
conformancePrefix == null || conformancePrefix == "pdfaid" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Property "amd" of the PDF/A Identification Schema shall have namespace prefix "pdfaid"
Property "amd" of the PDF/A Identification Schema has an invalid namespace prefix
- Object type:
PDFAIdentification - Test condition:
amdPrefix == null || amdPrefix == "pdfaid" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Property "corr" of the PDF/A Identification Schema shall have namespace prefix "pdfaid"
Property "corr" of the PDF/A Identification Schema has an invalid namespace prefix
- Object type:
PDFAIdentification - Test condition:
corrPrefix == null || corrPrefix == "pdfaid" - Specification: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The document catalog dictionary shall include a MarkInfo dictionary containing an entry, Marked, whose value shall be true.
MarkInfo dictionary is not present in the document catalog, or Marked entry is set to false or is not present in the MarkInfo dictionary.
This setting indicates that the file conforms to the Tagged PDF conventions.
- Object type:
CosDocument - Test condition:
Marked == true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.7.1
The logical structure of the conforming file shall be described by a structure hierarchy rooted in the StructTreeRoot entry of the document's Catalog dictionary, as described in ISO 32000-1:2008, 14.7.
StructTreeRoot entry is not present in the document catalog
The logical structure of a document is described by a hierarchy of objects called the structure hierarchy or structure tree. At the root of the hierarchy is a dictionary object called the structure tree root, located via the StructTreeRoot entry in the document catalog.
- Object type:
PDDocument - Test condition:
StructTreeRoot_size == 1 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.7
All non-standard structure types shall be mapped to the nearest functionally equivalent standard type, as defined in ISO 32000-1:2008, 14.8.4, in the role map dictionary of the structure tree root.
Non-standard structure type is not mapped to a standard type, or a circular mapping for this structure type is detected.
- Object type:
SENonStandard - Test condition:
isNotMappedToStandardType == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.8.4
A circular mapping shall not exist.
A circular mapping exists.
- Object type:
SENonStandard - Test condition:
circularMappingExist != true - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.8.4
Standard tags shall not be remapped to a non-standard type
A standard structure type is remapped to a non-standard type
- Object type:
SENonStandard - Test condition:
remappedStandardType == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.8.4
If the Lang entry is present in the document's Catalog dictionary or in a structure element dictionary or property list, its value shall be a language identifier as described in ISO 32000-1:2008, 14.9.2. A language identifier shall either be the empty text string, to indicate that the language is unknown, or a Language-Tag as defined in RFC 3066, Tags for the Identification of Languages.
Value of the Lang entry is not a Language-Tag
- Object type:
CosLang - Test condition:
unicodeValue == '' || /^[a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*$/.test(unicodeValue) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A
- Additional references:
- ISO 32000-1:2008, 14.9.2,
- RFC 3066, 2.1
The MIME type of an embedded file, or a subset of a file, shall be specified using the Subtype key of the file specification dictionary. If the MIME type is not known, the "application/octet-stream" shall be used.
The MIME type information (Subtype entry) of an embedded file is missing or invalid.
- Object type:
EmbeddedFile - Test condition:
Subtype != null && /^[-\w+\.]+\/[-\w+\.]+$/.test(Subtype) - Specifications: ISO 19005-3:2012
- Levels: A, B, U
The file specification dictionary for an embedded file shall contain the F and UF keys.
The file specification dictionary for an embedded file does not contain either F or UF key.
- Object type:
CosFileSpecification - Test condition:
containsEF == false || (F != null && UF != null) - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The file specification dictionary shall contain key AFRelationship of type Name identifying the relationship between the embedded file and the content of the document
The file specification dictionary for an embedded file does not contain the AFRelationship key or it has invalid value type
- Object type:
CosFileSpecification - Test condition:
AFRelationship != null - Specifications: ISO 19005-3:2012
- Levels: A, B, U
The additional information provided for associated files as well as the usage requirements for associated files indicate the relationship between the embedded file and the PDF document or the part of the PDF document with which it is associated.
The file specification dictionary for an embedded file is not associated with the PDF document or any of its parts.
Each file attachment in a PDF/A-3 document must be referenced from one of the following objects in the PDF document:
- Catalog dictionary, if the file is associated with the document as a whole
- Page dictionary, if the file is associated with one of the document pages
- Marked content property dictionary, if the file is associated with a specific part of page contents
- XObject dictionary, if the file is associated with an image or a form XObject
- Structure element dictionary, if the file is associated with any element in the document's logical structure
- Annotation dictionary, if the file is associated with any annotation
- Object type:
CosFileSpecification - Test condition:
isAssociatedFile == true - Specifications: ISO 19005-3:2012
- Levels: A, B, U
A file specification dictionary, as defined in ISO 32000-1:2008, 7.11.3, may contain the EF key, provided that the embedded file is compliant with either ISO 19005-1 or this part of ISO 19005.
An embedded file does not comply to either ISO 19005-1 or ISO 19005-2
- Object type:
EmbeddedFile - Test condition:
isValidPDFA12 == true - Specifications: ISO 19005-2:2011
- Levels: A, B, U
Each optional content configuration dictionary that forms the value of the D key, or that is an element in the array that forms the value of the Configs key in the OCProperties dictionary, shall contain the Name key.
Missing or empty Name entry of the optional content configuration dictionary.
- Object type:
PDOCConfig - Test condition:
Name != null && Name.length() > 0 - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
Each optional content configuration dictionary shall contain the Name key, whose value shall be unique amongst all optional content configuration dictionaries within the PDF/A-2(PDF/A-3) file.
Optional content configuration dictionary has duplicated name.
- Object type:
PDOCConfig - Test condition:
hasDuplicateName == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
If an optional content configuration dictionary contains the Order key, the array which is the value of this Order key shall contain references to all OCGs in the conforming file.
Not all optional content groups are present in the Order entry of the optional content configuration dictionary.
- Object type:
PDOCConfig - Test condition:
OCGsNotContainedInOrder == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The AS key shall not appear in any optional content configuration dictionary.
AS key is present in the optional content configuration dictionary.
- Object type:
PDOCConfig - Test condition:
AS == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
There shall be no AlternatePresentations entry in the document's name dictionary.
The document's name dictionary contains the AlternatePresentations entry.
- Object type:
PDDocument - Test condition:
containsAlternatePresentations == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
There shall be no PresSteps entry in any Page dictionary.
A Page dictionary contains the PresSteps entry.
- Object type:
PDPage - Test condition:
containsPresSteps == false - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U
The document catalog shall not contain the Requirements key.
The document catalog contains the Requirements key.
- Object type:
CosDocument - Test condition:
Requirements == null - Specifications: ISO 19005-2:2011, ISO 19005-3:2012
- Levels: A, B, U