Repository navigation
PDF20 Spec 07 Document Structure
Part of: PDF20-Spec-07-Syntax
Navigation: PDF20-Spec-07-Encryption | PDF20-Spec-Index | PDF20-Spec-07-Content-Streams
7.7
Document structure
7.7.1 General A PDF document can be regarded as a hierarchy of objects contained in the body section of a PDF file. At the root of the hierarchy is the document’s catalog dictionary (see 7.7.2, "Document catalog dictionary").
96
© ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
NOTE EXAMPLE
Most of the objects in the hierarchy are dictionaries. "Figure 5 — Structure of a PDF document" illustrates the structure of the object hierarchy. Each page of the document is represented by a page object–a dictionary that includes references to the page’s contents and other attributes, such as its thumbnail image (12.3.4, "Thumbnail images") and any annotations (12.5, "Annotations") associated with it. The individual page objects are tied together in a structure called the page tree (described in 7.7.3, "Page tree"), which in turn is specified by an indirect reference in the document catalog dictionary. Parent, child, and sibling relationships within the hierarchy are defined by dictionary entries whose values are indirect references to other dictionaries.
The data structures described in this subclause, particularly the Catalog and Page dictionaries, combine entries describing document structure with ones dealing with the detailed semantics of documents and pages. All entries are listed here, but many of their descriptions are deferred to subsequent subclauses.
7.7.2 Document catalog dictionary The root of a document’s object hierarchy is the catalog dictionary, located by means of the Root entry in the trailer of the PDF file (see 7.5.5, "File trailer"). The catalog dictionary contains references to other objects defining the document’s contents, outline, article threads, named destinations, and other attributes. In addition, it contains information about how the document shall be displayed on the screen, such as whether its outline and thumbnail page images shall be displayed automatically and whether some location other than the first page shall be shown when the document is opened. "Table 29 — Entries in the catalog dictionary" shows the entries in the catalog dictionary.
© ISO 2020 – All rights reserved
97
ISO 32000-2:2020(E)
Figure 5 — Structure of a PDF document Table 29 — Entries in the catalog dictionary
98
Key
Type
Value
Type
name
(Required) The type of PDF object that this dictionary describes; shall be Catalog for the catalog dictionary.
© ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Key
Type
Value
Version
name
(Optional; PDF 1.4) The version of the PDF specification to which the document conforms (for example, 1.4) if later than the version specified in the file’s header (see 7.5.2, "File header"). If the header specifies a later version, or if this entry is absent, the document shall conform to the version specified in the header. This entry enables a PDF processor to update the version using an incremental update; see 7.5.6, "Incremental updates". The value of this entry shall be a name object, not a number, and therefore shall be preceded by a SOLIDUS (2Fh) character (/) when written in the PDF file (for example, /1.4).
Extensions
dictionary
(Optional; ISO 32000-1) An extensions dictionary containing developer prefix identification and version numbers for developer extensions that occur in this document. 7.12, "Extensions dictionary", describes this dictionary and how it shall be used.
Pages
dictionary
(Required; shall be an indirect reference) The page tree node that shall be the root of the document’s page tree (see 7.7.3, "Page tree").
PageLabels
number tree (Optional; PDF 1.3) A number tree (see 7.9.7, "Number trees") defining the page labelling for the document. The keys in this tree shall be page indices; the corresponding values shall be page label dictionaries (see 12.4.2, "Page labels"). Each page index shall denote the first page in a labelling range to which the specified page label dictionary applies. The tree shall include a value for page index 0.
Names
dictionary
(Optional; PDF 1.2) The document’s name dictionary (see 7.7.4, "Name dictionary"). (PDF 2.0) For unencrypted wrapper documents for an encrypted payload document (see 7.6.7, "Unencrypted wrapper document") the Names dictionary is required and shall contain the EmbeddedFiles name tree.
Dests
dictionary
(Optional; PDF 1.1; shall be an indirect reference) A dictionary of names and corresponding destinations (see 12.3.2.4, "Named destinations").
ViewerPreferences dictionary
(Optional; PDF 1.2) A viewer preferences dictionary (see 12.2, "Viewer preferences") specifying the way the document shall be displayed on the screen. If this entry is absent, PDF readers shall use their own current user preference settings.
© ISO 2020 – All rights reserved
99
ISO 32000-2:2020(E)
100
Key
Type
Value
PageLayout
name
(Optional) A name object specifying the page layout shall be used when the document is opened: SinglePage Display one page at a time OneColumn Display the pages in one column TwoColumnLeft Display the pages in two columns, with oddnumbered pages on the left TwoColumnRight Display the pages in two columns, with oddnumbered pages on the right TwoPageLeft (PDF 1.5) Display the pages two at a time, with odd-numbered pages on the left TwoPageRight (PDF 1.5) Display the pages two at a time, with odd-numbered pages on the right Default value: SinglePage.
PageMode
name
(Optional) A name object specifying how the document shall be displayed when opened: UseNone Neither document outline nor thumbnail images visible UseOutlines Document outline visible UseThumbs Thumbnail images visible FullScreen Full-screen mode, with no menu bar, window controls, or any other window visible UseOC (PDF 1.5) Optional content group panel visible UseAttachments (PDF 1.6) Attachments panel visible Default value: UseNone.
Outlines
dictionary
(Optional; shall be an indirect reference) The outline dictionary that shall be the root of the document’s outline hierarchy (see 12.3.3, "Document outline").
Threads
array
(Optional; PDF 1.1; shall be an indirect reference) An array of thread dictionaries that shall represent the document’s article threads (see 12.4.3, "Articles").
OpenAction
dictionary or array
(Optional; PDF 1.1) A value specifying a destination that shall be displayed or an action that shall be performed when the document is opened. The value shall be either an array defining a destination (see 12.3.2, "Destinations") or an action dictionary representing an action (12.6.2, "Action dictionaries"). If this entry is absent, the document shall be opened to the top of the first page at the default magnification factor.
AA
dictionary
(Optional; PDF 1.2) An additional-actions dictionary defining the actions that shall be taken in response to various trigger events affecting the document as a whole (see 12.6.3, "Trigger events").
URI
dictionary
(Optional; PDF 1.1) A URI dictionary containing document-level information for URI (uniform resource identifier) actions (see 12.6.4.8, "URI actions").
AcroForm
dictionary
(Optional; PDF 1.2) The document’s interactive form (AcroForm) dictionary (see 12.7.3, "Interactive form dictionary"). © ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Key
Type
Value
Metadata
stream
(Optional; PDF 1.4; shall be an indirect reference) A metadata stream that shall contain metadata for the document (see 14.3.2, "Metadata streams").
StructTreeRoot
dictionary
(Optional; PDF 1.3) The document’s structure tree root dictionary (see 14.7.2, "Structure hierarchy").
MarkInfo
dictionary
(Optional; PDF 1.4) A mark information dictionary that shall contain information about the document’s usage of tagged PDF conventions (see 14.7, "Logical structure").
Lang
text string
(Optional; PDF 1.4) A language identifier that shall specify the natural language for all text in the document except where overridden by language specifications for structure elements or marked-content (see 14.9.2, "Natural language specification"). If this entry is absent, the language shall be considered unknown.
SpiderInfo
dictionary
(Optional; PDF 1.3) A Web Capture information dictionary that shall contain state information used by any Web Capture extension (see 14.10.2, "Web capture information dictionary").
OutputIntents
array
(Optional; PDF 1.4) An array of output intent dictionaries that shall specify the colour characteristics of output devices on which the document might be rendered (see 14.11.5, "Output intents").
PieceInfo
dictionary
(Optional; PDF 1.4) A page-piece dictionary associated with the document (see 14.5, "Page-piece dictionaries").
OCProperties
dictionary
(Optional; PDF 1.5; required if a document contains optional content) The document’s optional content properties dictionary (see 8.11.4, "Configuring optional content").
Perms
dictionary
(Optional; PDF 1.5) A permissions dictionary that shall specify user access permissions for the document. 12.8.6, "Permissions", describes this dictionary and how it shall be used.
Legal
dictionary
(Optional; PDF 1.5) A dictionary that shall contain attestations regarding the content of a PDF document, as it relates to the legality of digital signatures (see 12.8.7, "Legal content attestations").
Requirements
array
(Optional; PDF 1.7) An array of requirement dictionaries that shall represent requirements for the document. Subclause 12.11, "Document requirements", describes this dictionary and how it shall be used.
Collection
dictionary
(Optional; PDF 1.7) A collection dictionary that an interactive PDF processor shall use to enhance the presentation of file attachments stored in the PDF document. (see 12.3.5, "Collections"). (PDF 2.0) For unencrypted wrapper documents for an encrypted payload document (see 7.6.7, "Unencrypted wrapper document ") the Collection is required and shall identify the encrypted payload as the default document (as indicated by the D entry) of the collection and shall further specify that the collection View should be initially H (hidden).
© ISO 2020 – All rights reserved
101
ISO 32000-2:2020(E)
Key
Type
Value
NeedsRendering
boolean
(Optional; deprecated in PDF 2.0) A flag used to expedite the display of PDF documents containing XFA forms. It specifies whether the document shall be regenerated when the document is first opened. See Annex K, “XFA forms”. Default value: false.
DSS
dictionary
(Optional; PDF 2.0) A DSS dictionary containing document-wide security information. See 12.8.4.3, "Document Security Store (DSS)".
AF
array of (Optional; PDF 2.0) An array of one or more file specification dictionaries dictionaries (7.11.3, "File specification dictionaries") which denote the associated files for this PDF document. See 14.13, "Associated files" and 14.13.3, "Associated files linked to the PDF document’s catalog" for more details. For unencrypted wrapper documents for an encrypted payload document (see 7.6.7, "Unencrypted wrapper document") the AF key is required and shall include a reference to the file specification dictionary for the encrypted payload document.
DPartRoot
dictionary
EXAMPLE
(Optional; PDF 2.0) A DPartRoot dictionary used to describe the document parts hierarchy for this PDF document. See 14.12, "Document parts".
The following shows a sample catalog dictionary object.
1 0 obj <</Type /Catalog /Pages 2 0 R /PageMode /UseOutlines /Outlines 3 0 R
endobj
7.7.3 Page tree 7.7.3.1
General
The pages of a document are accessed through a structure known as the page tree, which defines the ordering of pages in the document. Using the tree structure, PDF readers using only limited memory, can quickly open a document containing thousands of pages. The tree contains nodes of two types — intermediate nodes, called page tree nodes, and leaf nodes, called page objects — whose form is described in the subsequent subclauses. Compliant PDF processors shall be prepared to handle any form of tree structure built of such nodes. NOTE
7.7.3.2
The simplest structure can consist of a single page tree node that references all of the document’s page objects directly. However, to optimise application performance, a PDF writer can construct trees of a particular form, known as balanced trees. Further information on this form of tree can be found in Data Structures and Algorithms, by Aho, Hopcroft, and Ullman.
Page tree nodes
"Table 30 — Required entries in a page tree node" shows the entries in a page tree node that shall always be present (Required). 102 © ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Table 30 — Required entries in a page tree node Key
Type
Value
Type
name
(Required) The type of PDF object that this dictionary describes; shall be Pages for a page tree node.
Parent
dictionary
(Required except in root node; not permitted in the root node; shall be an indirect reference) The page tree node that is the immediate parent of this one.
Kids
array
(Required) An array of indirect references to the immediate children of this node. The children shall only be page objects or other page tree nodes.
Count
integer
(Required) The number of leaf nodes (page objects) that are descendants of this node within the page tree. NOTE
Since the number of pages descendent from a Pages dictionary can be accurately determined by examining the tree itself using the Kids arrays, the Count entry is redundant.
A PDF writer shall ensure that the value of the Count key is consistent with the number of entries in the Kids array and its descendants which definitively determines the number of descendant pages.
NOTE 1
The structure of the page tree is not necessarily related to the logical structure of the document; that is, page tree nodes do not represent chapters, sections, and so forth. Other data structures are defined for this purpose; see 14.7, "Logical structure".
PDF processors shall not be required to preserve the existing structure of the page tree. EXAMPLE
The following illustrates the page tree for a document with three pages. See 7.7.3.3, "Page objects" for the contents of the individual page objects, and H.5, "Page tree example", for a more extended example showing the page tree for a longer document.
2 0 obj <</Type /Pages /Kids [4 0 R 10 0 R 24 0 R ] /Count 3
endobj 4 0 obj <</Type /Page …Additional entries describing the attributes of this page…
endobj 10 0 obj <</Type /Page …Additional entries describing the attributes of this page…
endobj 24 0 obj <</Type /Page …Additional entries describing the attributes of this page…
endobj
© ISO 2020 – All rights reserved
103
ISO 32000-2:2020(E)
In addition to the entries shown in "Table 30 — Required entries in a page tree node", a page tree node may contain further entries defining inherited attributes for the page objects that are its descendants (see 7.7.3.4, "Inheritance of page attributes"). A page tree shall not contain multiple indirect references to the same page tree node. NOTE 2
This requirement prevents multiple copies of the same node being present in the tree.
7.7.3.3
Page objects
The leaves of the page tree are page objects, each of which is a dictionary specifying the attributes of a single page of the document. "Table 31 — Entries in a page object" shows the contents of this dictionary. The table also identifies which attributes a page may inherit from its ancestor nodes in the page tree, as described under 7.7.3.4, "Inheritance of page attributes". Attributes that are not explicitly identified in the table as inheritable shall not be inherited. Table 31 — Entries in a page object Key
Type
Value
Type
name
(Required) The type of PDF object that this dictionary describes; shall be Page for a page object or Template for an invisible Template page (see 12.7.7, "Named pages").
Parent
dictionary
(Required; shall be an indirect reference) The page tree node that is the immediate parent of this page object. Objects of Type Template shall have no Parent key.
LastModified
date
(Required if PieceInfo is present; optional otherwise; PDF 1.3) The date and time (see 7.9.4, "Dates") when the page’s contents were most recently modified. If a page-piece dictionary (PieceInfo) is present, the modification date shall be used to ascertain which of the application data dictionaries that it contains correspond to the current content of the page (see 14.5, "Page-piece dictionaries").
Resources
dictionary
(Required; inheritable) A dictionary containing any resources required by the page contents (see 7.8.3, "Resource dictionaries"). If the page requires no resources, the value of this entry shall be an empty dictionary. Omitting the entry entirely indicates that the resources shall be inherited from an ancestor node in the page tree, but PDF writers should not use this method of sharing resources as described in 7.8.3, "Resource dictionaries".
MediaBox
rectangle
(Required; inheritable) A rectangle (see 7.9.5, "Rectangles"), expressed in default user space units, that shall define the boundaries of the physical medium on which the page shall be displayed or printed (see 14.11.2, "Page boundaries").
CropBox
rectangle
(Optional; Inheritable) A rectangle, expressed in default user space units, that shall define the visible region of default user space. When the page is displayed or printed, its contents shall be clipped (cropped) to this rectangle (see 14.11.2, "Page boundaries"). Default value: the value of MediaBox. NOTE 1 This clipped page output will often be placed (imposed) on the output medium in some implementation-defined manner.
104
© ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Key
Type
Value
BleedBox
rectangle
(Optional; PDF 1.3) A rectangle, expressed in default user space units, that shall define the region to which the contents of the page shall be clipped when output in a production environment (see 14.11.2, "Page boundaries"). Default value: the value of CropBox.
TrimBox
rectangle
(Optional; PDF 1.3) A rectangle, expressed in default user space units, that shall define the intended dimensions of the finished page after trimming (see 14.11.2, "Page boundaries"). Default value: the value of CropBox.
ArtBox
rectangle
(Optional; PDF 1.3) A rectangle, expressed in default user space units, that shall define the extent of the page’s meaningful content (including potential white-space) as intended by the page’s creator (see 14.11.2, "Page boundaries"). Default value: the value of CropBox.
BoxColorInfo
dictionary
(Optional; PDF 1.4) A box colour information dictionary that shall specify the colours and other visual characteristics that should be used in displaying guidelines on the screen for the various page boundaries (see 14.11.2.2, "Display of page boundaries"). If this entry is absent, the application shall use its own current default settings.
Contents
stream or array
(Optional) A content stream (see 7.8.2, "Content streams") that shall describe the contents of this page. If this entry is absent, the page shall be empty. The value shall be either a single stream or an array of streams. If the value is an array, the effect shall be as if all of the streams in the array were concatenated with at least one white-space character added between the streams’ data, in order, to form a single stream. PDF writers can create image objects and other resources as they occur, even though they interrupt the content stream. The division between streams may occur only at the boundaries between lexical tokens (see 7.2, "Lexical conventions") but shall be unrelated to the page’s logical content or organisation. Applications that consume or produce PDF files need not preserve the existing structure of the Contents array. PDF writers shall not create a Contents array containing no elements.
Rotate
integer
(Optional; inheritable) The number of degrees by which the page shall be rotated clockwise when displayed or printed. The value shall be a multiple of 90. Default value: 0.
Group
dictionary
(Optional; PDF 1.4) A group attributes dictionary that shall specify the attributes of the page’s page group for use in the transparent imaging model (see 11.4.7, "Page group" and 11.6.6, "Transparency group XObjects").
Thumb
stream
(Optional) A stream object that shall define the page’s thumbnail image (see 12.3.4, "Thumbnail images").
© ISO 2020 – All rights reserved
105
ISO 32000-2:2020(E)
Key
Type
Value
B
array
(Optional; PDF 1.1; recommended if the page contains article beads) An array that shall contain indirect references to all article beads appearing on the page (see 12.4.3, "Articles"). The beads shall be listed in the array in natural reading order. Objects of Type Template shall have no B key. NOTE 2 The information in this entry can be created or recreated from the information obtained from the Threads key in the catalog dictionary.
Dur
number
(Optional; PDF 1.1) The page’s display duration (also called its advance timing): the maximum length of time, in seconds, that the page shall be displayed during presentations before the viewer application shall automatically advance to the next page (see 12.4.4, "Presentations"). By default, the viewer shall not advance automatically.
Trans
dictionary
(Optional; PDF 1.1) A transition dictionary describing the transition effect that shall be used when displaying the page during presentations (see 12.4.4, "Presentations").
Annots
array
(Optional) An array of annotation dictionaries that shall contain indirect references to all annotations associated with the page (see 12.5, "Annotations").
AA
dictionary
(Optional; PDF 1.2) An additional-actions dictionary that shall define actions to be performed when the page is opened or closed (see 12.6.3, "Trigger events"). (PDF 1.3) additional-actions dictionaries are not inheritable.
Metadata
stream
(Optional; PDF 1.4) A metadata stream that shall contain metadata for the page (see 14.3.2, "Metadata streams").
PieceInfo
dictionary
(Optional; PDF 1.3) A page-piece dictionary associated with the page (see 14.5, "Page-piece dictionaries").
StructParents
integer
(Required if the page contains structural content items; PDF 1.3) The integer key of the page’s entry in the structural parent tree (see 14.7.5.4, "Finding structure elements from content items").
ID
byte string
(Optional; PDF 1.3; indirect reference preferred) The digital identifier of the page’s parent Web Capture content set (see 14.10.6, "Object attributes related to web capture").
PZ
number
(Optional; PDF 1.3) The page’s preferred zoom (magnification) factor: the factor by which it shall be scaled to achieve the natural display magnification (see 14.10.6, "Object attributes related to web capture").
SeparationInfo
dictionary
(Optional; PDF 1.3) A separation dictionary that shall contain information needed to generate colour separations for the page (see 14.11.4, "Separation dictionaries").
106
© ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Key
Type
Value
Tabs
name
(Optional; PDF 1.5) A name specifying the tab order that shall be used for annotations on the page (see 12.5 "Annotations"). If present, the values shall be one of R (row order), C (column order), and S (structure order). Beginning with PDF 2.0, additional values also include A (annotations array order) and W (widget order). Annotations array order refers to the order of the annotation enumerated in the Annots entry of the Page dictionary (see "Table 31 — Entries in a page object"). Widget order means using the same array ordering but making two passes, the first only picking the widget annotations and the second picking all other annotations.
TemplateInstantiated name
(Required if this page was created from a named page object; PDF 1.5) The name of the originating page object (see 12.7.7, "Named pages").
PresSteps
dictionary
(Optional; PDF 1.5) A navigation node dictionary that shall represent the first node on the page (see 12.4.4.2, "Sub-page navigation").
UserUnit
number
(Optional; PDF 1.6) A positive number that shall give the size of default user space units, in multiples of 1 ⁄ 72 inch. The range of supported values shall be implementation-dependent. Default value: 1.0 (user space unit is 1 ⁄ 72 inch).
VP
array
(Optional; PDF 1.6) An array of viewport dictionaries (see "Table 265 — Entries in a viewport dictionary") that shall specify rectangular regions of the page.
AF
array of (Optional; PDF 2.0) An array of one or more file specification dictionaries dictionaries (7.11.3, "File specification dictionaries") which denote the associated files for this page. See 14.13, "Associated files" and 14.13.8, "Associated files linked to DParts" for more details.
OutputIntents
array
(Optional; PDF 2.0) An array of output intent dictionaries that shall specify the colour characteristics of output devices on which this page might be rendered (see 14.11.5, "Output intents").
DPart
dictionary
(Required, if this page is within the range of a DPart, not permitted otherwise; PDF 2.0) An indirect reference to the DPart dictionary whose range of pages includes this page object (see 14.12.3, "Connecting the DPart tree structure to pages"). NOTE 3 The DPart key in a page object allows a PDF processor to directly retrieve the section of the document part hierarchy that applies to this page object. This also allows for ready access of DPM data in PDF processors.
© ISO 2020 – All rights reserved
107
ISO 32000-2:2020(E)
EXAMPLE
The following shows the definition of a page object with two annotations. The media box specifies that the page is to be printed on letter-size paper. In addition, the resource dictionary is specified as a direct object and shows that the page makes use of three fonts named F3, F5, and F7.
3 0 obj <</Type /Page /Parent 4 0 R /MediaBox [0 0 612 792] /Resources <</Font <</F3 7 0 R /F5 9 0 R /F7 11 0 R
/Contents 12 0 R /Annots [23 0 R 24 0 R ]
endobj
A page tree shall not contain multiple indirect references to the same page object. NOTE
7.7.3.4
This requirement prevents multiple copies of the same page being present in the tree.
Inheritance of page attributes
Some of the page attributes shown in "Table 31 — Entries in a page object" are designated as inheritable. If such an attribute is omitted from a page object, its value shall be inherited from an ancestor node in the page tree. If the attribute is a required one, a value shall be supplied in an ancestor node. If the attribute is optional and no inherited value is specified, the default value shall be used. An attribute can thus be defined once for a whole set of pages by specifying it in an intermediate page tree node and arranging the pages that share the attribute as descendants of that node. EXAMPLE
A document might specify the same media box for all of its pages by including a MediaBox entry in the root node of the page tree. If necessary, an individual page object can override this inherited value with a MediaBox entry of its own.
All values shall be inherited as-is, without merging, even for composite data types such as arrays and dictionaries. Thus (at least conceptually) the Resources dictionary for a page shall be found by searching the Page object and then each Pages object encountered by following Parent links up the pages tree from the Page towards the Catalog object. When the first Resources dictionary is found the search shall be stopped and that Resources dictionary shall be used in its entirety. In a document conforming to Linearized PDF (see Annex F, "Linearized PDF" and Annex G, "Linearized PDF access strategies") all page attributes shall be specified explicitly as entries in the page dictionaries to which they apply; they shall not be inherited from an ancestor node. "Figure 6 — Inheritance of attributes" illustrates the inheritance of attributes. In the page tree shown, pages 1, 2, and 4 are rotated clockwise by 90 degrees, page 3 by 270 degrees, page 6 by 180 degrees, and pages 5 and 7 not at all (0 degrees).
108
© ISO 2020 – All rights reserved
ISO 32000-2:2020(E)
Figure 6 — Inheritance of attributes
7.7.4 Name dictionary Some categories of objects in a PDF file can be referred to by name rather than by object reference. The correspondence between names and objects is established by the document’s name dictionary (PDF 1.2), located by means of the Names entry in the document’s catalog dictionary (see 7.7.2, "Document catalog dictionary"). Each entry in this dictionary designates the root of a name tree (see 7.9.6, "Name trees") defining names for a particular category of objects. "Table 32 — Entries in the name dictionary" shows the contents of the name dictionary. Table 32 — Entries in the name dictionary Key
Type
Value
Dests
name tree
(Optional; PDF 1.2) A name tree mapping name strings to destinations (see 12.3.2.4, "Named destinations").
AP
name tree
(Optional; PDF 1.3) A name tree mapping name strings to annotation appearance streams (see 12.5.5, "Appearance streams").
JavaScript
name tree
(Optional; PDF 1.3) A name tree mapping name strings to documentlevel ECMAScript actions (see 12.6.4.17, "ECMAScript actions").
Pages
name tree
(Optional; PDF 1.3) A name tree mapping name strings to visible pages for use in interactive forms (see 12.7.7, "Named pages").
Templates
name tree
(Optional; PDF 1.3) A name tree mapping name strings to invisible (template) pages for use in interactive forms (see 12.7.7, "Named pages").
IDS
name tree
(Optional; PDF 1.3) A name tree mapping digital identifiers to Web. Capture content sets (see 14.10.4, "Content sets").
URLS
name tree
(Optional; PDF 1.3) A name tree mapping uniform resource locators. (URLs) to Web Capture content sets (see 14.10.4, "Content sets").
© ISO 2020 – All rights reserved
109
ISO 32000-2:2020(E)
Key
Type
Value
EmbeddedFiles
name tree
(Optional; PDF 1.4) A name tree mapping name strings to file specifications for embedded file streams (see 7.11.4, "Embedded file streams"). All File Specification dictionaries referenced from this name tree shall contain an EF key whose value is a dictionary which contains either an F or UF key whose value is an embedded file stream. (PDF 2.0) For unencrypted wrapper documents for an encrypted payload document (see 7.6.7, "Unencrypted wrapper document") the name strings provided in this tree shall not contain or be derived from the encrypted payload document’s actual file name. This is to avoid potential disclosure of sensitive information in the original filename. The name string should match the value of F or UF in the referenced File Specification dictionary.
AlternatePresentations name tree Renditions
Navigation: PDF20-Spec-07-Encryption | PDF20-Spec-Index | PDF20-Spec-07-Content-Streams