(informative) Example PDF files

H.2 Minimal PDF file
H.7 Updating example
- H.7.5 Stage 4: Add three annotations and update metadata
H.8 Structure elements examples
- H.8.2 Table of Contents
- H.8.3 Hierarchical lists

Issue #xxxx

Annex H. (informative) Example PDF files

EDITOR NOTE: as a result of Errata #415, all occurrences of incorrect PDF content stream operator ~~/BDC~~ need to replaced by BDC (PDF content operators do not have leading SLASH) throughout Annex H.

H.2 Minimal PDF file

Change the example as follows:

...
            <xmpMM:DocumentID>… unique GUID of document …</xmpMM:DocumentID>
            <xmpMM:InstanceID>… GUID changed for each save …</xmpMM:InstanceID>
...

H.7 Updating example

H.7.5 Stage 4: Add three annotations and update metadata

Change the example as follows:

...
6 0 obj                                         %Metadata streams
      <</Type /Metadata
          /Subtype /XML
          /Length … number of bytes in updated metadata …
      >>
stream
%In this Metadata, "preserved" items are left unaltered, and not updated to reflect possibly
%different software or a different author. Updating software needs to be able to parse the XMP
%in any valid format and preserve all content which is not to be updated, even that with
%unfamiliar tags. In this example some reordering of tags has taken place. Note further that
%after incremental update there can be multiple XMP packets
<?xpacket begin="… UTF-8 value of U+FEFF (efbbbf) …" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about="" xmlns:pdf="http://ns.adobe.com/pdf/1.3/">
<pdf:Producer>… name of software which generated the PDF (preserved) …</pdf:Producer>
</rdf:Description>
<rdf:Description rdf:about="" xmlns:dc="http://purl.org/dc/elements/1.1/">
<dc:format>application/pdf</dc:format>
<dc:title><rdf:Alt>
<rdf:li xml:lang="x-default">… document title (preserved) …</rdf:li>
</rdf:Alt></dc:title>
<dc:creator><rdf:Seq>
<rdf:li>… document author’s personal name (preserved) …</rdf:li>
</rdf:Seq></dc:creator>
</rdf:Description>
<rdf:Description rdf:about="" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/">
<xmpMM:DocumentID>… unique GUID of document (preserved) …</xmpMM:DocumentID>
<xmpMM:InstanceID>… GUID changed for each save (updated) …</xmpMM:InstanceID>
</rdf:Description>
<rdf:Description rdf:about="" xmlns:xmp="http://ns.adobe.com/xap/1.0/">
<xmp:CreatorTool>… name of tool used to create the document (preserved) …</xmp:CreatorTool>
<xmp:CreateDate>… timestamp, like 2012-12-25T12:34:56Z (preserved) …</xmp:CreateDate>
<xmp:ModifyDate>… timestamp, like 2012-12-27T14:36:06Z (updated) …</xmp:ModifyDate>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
… white-space padding to permit in-place updating of metadata …
… Note that applications which fully understand PDF updating do not usually update in-place …
<?xpacket end="w"?>
...
endstream
endobj
...

H.8 Structure elements examples

H.8.2 Table of Contents

Change the first paragraph as follows:

The structure element’s structure type entry (S) may have values that establish hierarchical relationships between entries in a table of contents. TheTOCI value specifies an individual member of a table of contents. The TOC value specifies a list made up of other table of contents items that are individual members of the table of contents and/or lists of table of contents items. (The trailing character in TOCI is an ~~upper case~~ uppercase "i".)

Insert a new NOTE after the first paragraph as follows:

NOTE the following example uses Reference, TOC and TOCI structure elements which are part of the standard structure namespace for PDF 1.7 and are entirely valid for use in PDF 2.0 under the default standard structure namespace (see 14.8.6, "Standard structure namespaces").

...

Correct Figure H.5 as follows (page numbers are all vertically aligned):

TABLE OF CONTENTS

1. Chapter One.............3

1.21 Section A.............4

1.32 Section B.............5

2. Chapter Two.............6

3. Chapter ~~Two~~Three.........7

3.1 Section A............8

...

Replace Figure H.6 with the following corrected version:

Corrected Figure H.6 — Association between content and marked-content identifiers — Figure H.6 — Association between content and marked-content identifiers

...

Replace Figure H.7 with the following corrected version:

Corrected Figure H.7 — Hierarchy of structure elements and relationship with marked-content — Figure H.7 — Hierarchy of structure elements and relationship with marked-content

...

Correct the last EXAMPLE as follows:

...
400 0 obj
    <</Type /StructElem
       /S /TOC
       /K [201 0 R 211 0 R 301 0 R 214 0 R 215 0 R 302 0 R]
       /P 400 0 R
    >>
endobj

H.8.3 Hierarchical lists

Change the first paragraph as follows:

The structure element’s structure type entry (S) may have values that establish hierarchical relationships between entries in a list. The LI value specifies an individual list entry. The L value specifies a list made up of individual list entries and/or lists of list entries. The trailing character in LI is an ~~upper case~~ uppercase "i".

...

Replace Figure H.9 with the following corrected version:

Corrected Figure H.9 — Hierarchy of structure elements and relationship with marked-content — Figure H.9 — Hierarchy of structure elements and relationship with marked-content

...

Last modified: 26 May 2024