14. Document interchange
14.5 Page-piece dictionaries
Change the paragraph above Table 350 as follows:
As "Table 350 - Entries in a page-piece dictionary" shows, a page-piece dictionary may contain any number of entries,
the name of a distinct PDF processor, or of a well-known data type recognised by a family of PDF processors.
The value associated with each key shall be a data dictionary containing the private data that shall be used by the PDF processor.
The Private entry may have a value of any data type, but typically it is a dictionary containing all of the private
data needed by the PDF processor other than the actual content of the document, page, or form.
Change Table 350 as follows:
|any valid second-class name||dictionary||A data dictionary (see "Table 351 - Entries in a data dictionary").|
Insert new NOTE below Table 350 as follows:
14.6 Marked content
Change NOTE 3 as follows:
NOTE 3 The tag operand of marked-content operators have no relationship to Tagged PDF (see 14.8 "Tagged PDF") and thus is not
14.7 Logical structure
14.7.2 Structure hierarchy
Change Table 355 as follows:
|R||integer||(Optional) The current revision number of this structure element (see 18.104.22.168, "Attribute revision numbers"). The value shall be a non-negative integer. Default value: 0.|
14.7.3 Structure types
Change the third paragraph as follows:
The RoleMap dictionary shall be comprised of a set of keys representing structure element types
rolemapped to other structure element types. The corresponding value for each of these keys shall be a single name identifying the target structure element type.
14.8 Tagged PDF
14.8.4 Standard structure types
22.214.171.124 Grouping level structure types
Change Table 365 as follows:
Encloses a grouping of structure elements without consideration for their hierarchy.
A structure element with the type of Part shall inherit the containment requirements and limitations of its parent element. Where the parent element is itself a structure element of type Part, then the inheritance shall recurse to the first parent element whose type is not Part.
126.96.36.199 Inline level structure types
188.8.131.52.2 General inline level structure types
Change Table 368 as follows:
(PDF 2.0) Encloses content for the purpose of strong importance, seriousness or urgency for its contents.
EXAMPLE 3 In this example the Strong element is used to denote the content
Insert a new clause heading below NOTE 1 and modify text as follows:
Tagged PDF link elements (standard structure type Link) use PDF's logical structure facilities to establish the association between content items and link annotations, providing functionality comparable to HTML hypertext links. The following items may be children of a link element:
- One or more content items or other ILSEs (except other links)
if A, Dest and PA keys of all of them have identical values
- Object references (see 184.108.40.206, "PDF objects as content items") to one link
annotationassociated with the content
2 An SD entry in the GoTo or GoToR action in a Link annotation facilitates linking directly to a target structure element as opposed to just targeting an area on a page.
3 Ruby and warichu elements
EDITOR NOTE: Clause is renumbered - existing text is unchanged.
220.127.116.11.3 Table structure types
Change Table 371 as follows:
|TR||Internal to a Table structure||A row of table header cells (TH) or table data cells (TD) in a table.|
18.104.22.168.4 Caption structure types
Change Table 372 as follows:
|Caption||Grouping or Block||
A structure element is understood to be "captioned" when a Caption structure element exists as an immediate child of that structure element. The Caption shall be the first or the last structure element inside its parent structure element. The number of captions cannot exceed 1.
While captions are often used with figures or formulas, they may be associated with any type of content.
NOTE In principle, captions can appear in a nested fashion. For example, several smaller images belonging to a group of images can each be accompanied by a caption, and the group of these images as a whole is accompanied by a caption as well.
14.8.5 Standard structure attributes
22.214.171.124 Layout attributes
126.96.36.199.2 General layout attributes
Change Table 378 as follows:
(Optional; not inheritable) The positioning of the element with respect to the enclosing reference area and other content . The value shall be one of the following:
Default value: Block for BLSEs, Inline for ILSEs.
(Optional; inheritable) Indicates the directions of layout progression inside Block Level Structure Elements (BLSEs) (inline progression) and regarding the sequence of BLSEs (block progression) . WritingMode may be used as an attribute for any structure element. The value shall be one of the following:
188.8.131.52.4 Layout Attributes for ILSEs
Change Table 380 as follows:
14.8.6 Standard structure namespaces
184.108.40.206 Namespaces for standard structure types and attributes
Modify the paragraph above the current NOTE as follows:
To facilitate conversion of documents created against versions of the PDF standard earlier than PDF 2.0, the
default standard structure namespace shall be "http://iso.org/pdf/ssn".
When a namespace is not explicitly specified for a given structure element or attribute, it shall be assumed to be within this default standard structure namespace.
Add a new NOTE 1 above the current NOTE as follows:
EDITOR NOTE: the current note is renumbered as NOTE 2.
Insert a new NOTE 3 after the last paragraph as follows:
The term standard structure namespaces refers to either of the two namespaces defined above.
220.127.116.11 Role maps and namespaces
Modify the 2nd bullet in the bulleted list as follows:
In a tagged PDF, all structure elements shall be in at least one of the standard structure namespaces or in a namespace identified in 18.104.22.168, “Other namespaces”. An element shall be considered to be in one of these namespaces if:
- they directly identify one of these namespaces through their NS entry;
- they are in the default standard structure namespace ;
Insert a new EXAMPLE 1 at the end of the subclause as follows:
Insert a new EXAMPLE 2 at the end of the subclause as follows:
22.214.171.124 Other namespaces
Replace the paragraph below NOTE 1 as follows:
NOTE 1 MathML is the only domain-specific namespace defined in PDF 2.0.
When including mathematics structured as MathML 3.0, the math structure element type as defined in MathML 3.0 shall be used, and shall have its namespace explicitly defined (see 126.96.36.199, "Namespace dictionary").
14.10 Web capture
14.10.5 Source information
188.8.131.52 Command dictionaries
Change Table 393 as follows:
(Optional) A set of flags specifying various characteristics of the command (see
14.12 Document parts
14.12.4 Data structures
184.108.40.206 Document part metadata
Change the last paragraph as follows:
The values of keys present in the DPM dictionary, or of any dictionary or array object present in the DPM dictionary, shall only be of type text string, date string, array, dictionary, boolean, integer or real as defined in 7.3, "Objects". Other PDF value types shall not be used.
14.13 Associated files
14.13.5 Associated files linked to graphics objects
Change the paragraph below NOTE 3 as follows:
The property list associated with the marked-content shall specify an array of file specification dictionaries to which
the content is associated. The named resource in the
(see 14.6.2, "Property lists") shall specify an array of file specification dictionaries to which the content is associated.
The relationship that the associated files have to the PDF content is supplied by the AFRelationship key in each file specification dictionary.
Last modified: 1 July 2022