BS ISO 21812-1:2019
$167.15
Graphic technology. Print product metadata for PDF files – Architecture and core requirements for metadata
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 36 |
The document part metadata in a PDF file that conforms to this document can be used to communicate the intended appearance of print products and their components. Examples of intended use are: direct interpretation within a production process, creation of job tickets such as XJDF, or populating records in an MIS. This document builds on the DPart syntax as specified in ISO 16612-2 (PDF/VT) and ISO 32000-2 (PDF 2.0) which is designed for encoding metadata related to pages or groups of pages in PDF files.
The document part metadata provided in this document applies to individual document parts, whereas XMP metadata typically applies to the scope of the entire document. XMP can apply to the scope of an individual page or part of a page but this usage is very uncommon. Thus, XMP is not applicable for the case where metadata is required for sets of pages such as multiple recipients or binding information. For example, XMP is used within PDF/X for file conformance identification and is also used for additional file level information such as author.
This document defines standardized metadata to:
-
provide product intent specifications such as paper media selection and binding information;
-
identify the type of product that the content pages are intended to represent (e.g. a brochure, letter or postcard);
-
identify the intended recipient of each of the content pages for variable document printing applications.
This document defines a base conformance level that includes the syntax of the metadata framework and the semantics of a core set of metadata.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 7 | Foreword |
| 8 | Introduction |
| 9 | 1 Scope 2 Normative references |
| 10 | 3 Terms and definitions 4 Notation 4.1 Keywords 4.2 Cardinality 4.3 Values of lists |
| 11 | 4.4 XPath Notation 5 Conformance 6 Technical requirements 6.1 Encoding metadata keys |
| 12 | 6.2 Encoding metadata values 6.2.1 Mapping of the encoding of XJDF Intent 6.2.2 Encoding of XML |
| 13 | 6.3 Document part (DPart) hierarchy 6.4 Defining metadata within a DPart 6.5 Registered second class name prefixes |
| 14 | 7 CIP4 Common metadata hierarchy 7.1 Background 7.2 CIP4_Root hierarchy |
| 15 | 7.3 CIP4_Metadata level 7.4 Recipient level |
| 16 | 7.5 Intent level 7.5.1 Background 7.5.2 Intent referencing |
| 18 | 7.6 Supported XJDF Intents 7.6.1 Background 7.6.2 Scope of Intents 7.6.3 CIP4_Intent/CIP4_AssemblingIntent |
| 20 | 7.6.4 CIP4_Intent/CIP4_BindingIntent |
| 22 | 7.6.5 CIP4_Intent/CIP4_ColorIntent 7.6.6 CIP4_Intent/CIP4_FoldingIntent |
| 25 | 7.6.7 CIP4_Intent/CIP4_HoleMakingIntent 7.6.8 CIP4_Intent/CIP4_LayoutIntent |
| 26 | 7.6.9 CIP4_Intent/CIP4_MediaIntent |
| 27 | 7.6.10 CIP4_Intent/CIP4_ProductionIntent |
| 28 | 7.7 Restrictions on mapping XJDF Intent types 7.8 CIP4_IntentSummary level |
| 29 | 7.9 Production level 7.9.1 CIP4_Production |
| 30 | 7.10 Common metadata structures 7.10.1 General 7.10.2 Contact information |
| 31 | 7.10.3 CIP4_Contact/CIP4_Person 7.10.4 CIP4_Contact/CIP4_Company |
| 32 | 7.10.5 CIP4_Contact/CIP4_Address 7.10.6 CIP4_Contact/CIP4_ComChannel |
| 33 | 8 PDF metadata encoding example 8.1 Introduction 8.2 Example metadata for a single recipient |
| 35 | Bibliography |
